Sr Product Owner, Portal Modernization, Attach & EBill

This Sr Product Owner role leads product ownership for Portal Modernization and EBill customer-facing experiences, with a focus on electronic billing workflows. The position blends Product Owner responsibilities with Technical Product Owner capabilities to convert business needs into UI/UX requirements and detailed, field-level and interface specifications across engineering teams.

Location and Work Model

• Danville, CA (hybrid)

Compensation

• USD 115,000 - 130,000 per year

Key Responsibilities

• Own the backlog and requirements for a defined product area spanning multiple engineering teams, prioritizing the highest-value capabilities in the right sequence.
• Elicit and analyze business requirements from product leadership, customers, operations, and compliance stakeholders, then translate them into epics, user stories, and workflows using Jira and Confluence.
• Decompose complex initiatives into structured, prioritized backlogs aligned to engineering execution across front-end, back-end, and integration teams.
• Define clear acceptance criteria (including Given/When/Then) and ensure requirements are complete, testable, and outcome driven.
• Continuously refine and reprioritize backlog items based on shifting priorities, dependencies, and technical constraints.
• Ensure readiness for sprint planning and ongoing development by attaching the necessary specifications and design artifacts to each story.
• Translate business requirements into UI/UX requirements, including user journeys, screen flows, page layouts, navigation, and role-based access behaviors.
• Partner with stakeholders on wireframes and prototypes (such as Figma), reviewing designs against business rules and confirming feasibility and completeness prior to development.
• Define field-level specifications for each screen, including field names, labels, data types and lengths, required or optional rules, default values, validation rules, dependencies, plus error and help messages.
• Define interface specifications for front-end and back-end development, including API endpoints, request and response payloads, data contracts, status and error codes, and pagination or search behavior, in collaboration with architects and engineering leads (for example, using OpenAPI/Swagger).
• Create and maintain data mappings that trace each data element across the UI, APIs, back-end services, databases, and EDI segments and loops (including X12 837, 835, 275, 277).
• Document business rules, state transitions, and process flows using diagrams such as swimlanes, sequence diagrams, and state models.
• Support QA by clarifying expected behavior, reviewing test scenarios, and validating delivery matches the defined specifications.
• Use AI assistants and agents (such as Claude) to build and validate product artifacts, including reusable AI skills, templates, and prompts for consistent generation of user stories, acceptance criteria, field specs, and API contracts, with review for accuracy prior to engineering handoff.
• Own the backlog for modernizing legacy portal capabilities, including user onboarding, account and enrollment management, bill submission, attachment upload, bill or claim status inquiry, and payment and remittance visibility.
• Define requirements for EBill workflows supporting electronic submission of medical bills and supporting documentation to payers and claims administrators, including acknowledgments, rejections, and status tracking.
• Partner with EDI, payment, and integration teams to ensure portal and EBill experiences accurately reflect transaction status, payment status, remittance details, and reconciliation data.
• Plan phased migration from legacy portal functionality, including feature parity analysis, user transition, and retirement of legacy components.
• Incorporate state e-billing rules, jurisdictional requirements, and HIPAA considerations into requirements and acceptance criteria.
• Use customer feedback, support trends, and usage analytics to identify pain points and prioritize improvements.
• Partner closely with engineering daily to clarify requirements, validate solutions, and remove blockers.
• Act as the primary point of contact for scope, requirement, and prioritization decisions for the product area.
• Participate in technical design discussions and evaluate trade-offs to align implementation approaches with product intent and platform architecture.
• Support engineering teams in delivering scalable, high-quality solutions across portal user interfaces, APIs, services, and EDI or integration workflows.
• Maintain an outcome focus, rather than operating as a Scrum Master or delivery coordination role.
• Represent the product area in sprint planning, backlog refinement, sprint reviews, and cross-functional discussions.
• Communicate priorities, trade-offs, and delivery expectations to stakeholders at all levels.
• Collaborate with product leadership, architecture, and UX to shape the roadmap and support cohesive platform evolution and a consistent user experience.
• Work with customer support, implementation, and operations teams to understand user and trading partner issues and feed them into backlog planning.
• Mentor other Product Owners and Business Analysts, helping establish standards and templates for user stories, field specifications, and interface documentation.
• Escalate strategic questions while driving day-to-day execution decisions independently.
• Provide visibility into progress, risks, and dependencies.

Required Qualifications

• 8+ years of experience as a Product Owner, Technical Product Owner, or Business/Systems Analyst in an agile, engineering-driven environment, including at least 2 years in a technical product ownership role.
• Proven ability to translate business requirements into UI/UX requirements, screen flows, and detailed field-level specifications.
• Experience defining or reviewing API and interface specifications (including REST, JSON, OpenAPI/Swagger) and data contracts with front-end and back-end developers.
• Solid understanding of data modeling and relational data concepts; ability to write basic SQL queries to analyze data is a plus.
• Experience working with UX designers and wireframing or prototyping tools such as Figma and Balsamiq (or similar).
• Demonstrated experience owning backlogs for customer-facing web portals, SaaS applications, or platform modernization initiatives.
• Fluency with Jira and Confluence, plus diagramming tools such as Lucidchart, Visio, or Miro.
• Ability to prioritize effectively, make trade-offs, and maintain a clear point of view under pressure.
• Strong communication and collaboration skills, including explaining technical concepts to business stakeholders and business context to engineers.
• Working knowledge of EDI, including one or more of the following: X12 837 (claims/bills), X12 835 (remittance advice), X12 275 (attachments), X12 276/277 (claim status), and X12 999/TA1 acknowledgments; reading implementation guides and mapping EDI segments and loops to application data models; trading partner onboarding, enrollment, and testing; EDI validation, error handling, rejections, and exception workflows.
• Working knowledge of payment processing concepts including ACH/EFT, virtual card, and check payments; payment lifecycle tracking and status management; electronic remittance (ERA/835) and payment-to-remittance reconciliation; compliance, risk, and financial control considerations (for example, NACHA rules and PCI).

Technologies

• Jira, Confluence
• Figma, Balsamiq
• Lucidchart, Visio, Miro
• OpenAPI/Swagger, OpenAPI
• REST, JSON
• SQL
• X12 837, X12 835, X12 275, X12 276, X12 277, X12 999, TA1
• Claude
• ACH/EFT, ERA/835

Nice to Have

• Experience in workers' compensation, auto/P&C medical billing, or healthcare revenue cycle management.
• Familiarity with state workers' compensation e-billing mandates and IAIABC standards.
• Experience migrating legacy web applications to modern front-end frameworks (for example React or Angular) and services-based architectures.
• Familiarity with API testing tools such as Postman and reviewing JSON/XML payloads.
• Background working on API-first products, distributed systems, or cloud-based architectures.
• Understanding of HIPAA, accessibility standards (WCAG), and regulated data environments, including role-based access for multi-organization portals.
• Certified Scrum Product Owner (CSPO), SAFe POPM, or equivalent certification.
• Experience building AI-assisted workflows for the product team, including AI skills for story writing, spec review, or test scenario generation, and helping other Product Owners adopt them effectively.

What You’ll Love at Office Ally

Office Ally focuses on work that has direct impact on healthcare providers and their ability to deliver exceptional care.