About the Role We are seeking a Senior Product Owner with strong technical depth to lead product ownership for Portal Modernization and EBill - the customer-facing portals and electronic billing workflows that connect providers, billing services, payers, and claims administrators across healthcare and property & casualty markets. This role combines core Product Owner responsibilities with Technical Product Owner skills: you will understand business requirements, translate them into UI/UX requirements, and define the field-level and interface specifications that front-end and back-end developers build from.
You will own the backlog and requirements for a defined product area spanning multiple engineering teams, ensuring they are consistently building the highest-value capabilities in the right order. This is a hands-on, delivery-oriented role focused on clarity, prioritization, and execution. As a senior member of the product delivery team, you will also contribute to roadmap planning and help raise the bar for requirements quality across the engineering organization.
As part of a broader platform transformation, you will help modernize legacy portal experiences into scalable, API-driven, user-centric applications and evolve our EBill platform for electronic bill submission, attachments, acknowledgments, and status tracking. You will work at the intersection of business workflows, user experience, EDI transactions, and payment processing, ensuring that bills, remittances, and payments flow accurately and transparently between trading partners.
Success in this role will be measured by the quality, predictability, and efficiency of product delivery, including:
- Backlog readiness and quality (clear, well-defined, and consistently prioritized work available for engineering execution).
- Specification completeness (UI field definitions, validation rules, and interface contracts finalized before development begins, with minimal mid-sprint clarification).
- Sprint predictability (high alignment between planned vs. completed sprint commitments).
- Delivery quality (reduced/eliminate rework, fewer requirement-related defects, and clear acceptance criteria adherence).
- Time-to-clarity for engineering (speed and effectiveness in resolving scope and requirement questions).
- Customer adoption and experience (improved portal usability, increased self-service adoption, and successful migration of users off legacy portal functionality).
- Transaction integrity (accurate, compliant EBill processing and fewer EDI rejections or payment exceptions caused by requirement gaps).
- Improved engineering focus (reduced reliance on engineering leadership for product ownership decisions, enabling focus on technical/architectural work).
This role is critical to the success of our Portal Modernization and EBill initiatives and our broader platform modernization efforts. You will directly influence how customers submit bills, track their status, and view payments and remittances through our portals. By ensuring clarity, focus, and execution discipline, you enable faster delivery, higher-quality outcomes, and a more resilient, future-ready platform.
This is a hybrid role based in Concord, CA. Employees are expected to work from the office at least two days per week.
What You'll Do Backlog & Requirements Ownership - Elicit and analyze business requirements from product leadership, customers, operations, and compliance stakeholders, and 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 (e.g., Given/When/Then) and ensure requirements are complete, testable, and outcome driven.
- Continuously refine and reprioritize backlog items based on evolving priorities, dependencies, and technical constraints.
- Ensure readiness of work for sprint planning and ongoing development, including specifications and design artifacts attached to each story.
UI/UX Requirements & Technical Specifications - Translate business requirements into UI/UX requirements, including user journeys, screen flows, page layouts, navigation, and role-based access behavior.
- Partner with stakeholders on wireframes and prototypes (e.g., Figma), review designs against business rules, and ensure designs are feasible and complete before development.
- Define field-level specifications for each screen, including field names, labels, data types, lengths and formats, required/optional rules, default values, validation rules, dependencies between fields, and error and help messages.
- Define interface specifications for front-end and back-end developers, including API endpoints, request and response payloads, data contracts, status and error codes, and pagination/search behavior, in collaboration with architects and engineering leads (e.g., using OpenAPI/Swagger).
- Create and maintain data mappings that trace each data element from the UI through APIs and back-end services to databases and EDI segments/loops (e.g., 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 that delivered functionality matches specifications.
- Use AI assistants and agents (e.g., Claude) to build and validate product artifacts. This includes creating reusable AI skills, templates, and prompts that generate user stories, acceptance criteria, field specs, and API contracts in a consistent format. It also includes checking requirements against business rules, EDI implementation guides, and existing specs, and reviewing AI-generated output for accuracy before sharing with engineering.
Portal Modernization & EBill - Own the backlog for modernizing legacy portal capabilities, including user onboarding, account and enrollment management, bill submission, attachment upload, bill/claim status inquiry, and payment and remittance visibility.
- Define requirements for EBill workflows that support 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 of existing screens and fields, 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.
Engineering Partnership - Partner closely with engineering on a daily basis to clarify requirements, validate solutions, and unblock execution.
- Act as the primary point of contact for all scope, requirement, and prioritization decisions for your product area.
- Participate in technical design discussions and evaluate trade-offs, aligning 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/integration workflows.
- Maintain a strong focus on outcomes, not just output (this is not a Scrum Master or delivery coordination role).
Stakeholder Alignment & Leadership - Represent your product area in sprint planning, backlog refinement, sprint reviews, and cross-functional discussions.
- Clearly communicate priorities, trade-offs, and delivery expectations to stakeholders at all levels.
- Collaborate with product leadership, architecture, and UX to shape the roadmap and ensure 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 the backlog.
- Mentor other Product Owners and Business Analysts, and help establish standards and templates for user stories, field specifications, and interface documentation.
- Escalate strategic questions while independently driving day-to-day execution decisions.
- Provide visibility into progress, risks, and dependencies.
What You'll Need - 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 (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/prototyping tools such as Figma, Balsamiq, or similar.
- Demonstrated experience owning backlogs for customer-facing web portals, SaaS applications, or platform modernization initiatives.
- Fluency with Jira and Confluence for backlog management and documentation, and with 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, with the ability to explain technical concepts to business stakeholders and business context to engineers.
- Working knowledge of EDI, including one or more of the following:
- X12 healthcare transactions such as 837 (claims/bills), 835 (remittance advice), 275 (attachments), 276/277 (claim status), and 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 (e.g., NACHA rules, PCI).
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 (e.g., React, Angular) and services-based architectures.
- Familiarity with API testing tools such as Postman, and with 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, such as AI skills for story writing, spec review, or test scenario generation, and helping other Product Owners adopt them effectively.
