Product Owner

Key Responsibilities

• Support the delivery of capabilities for transaction routing and centralized data repository platforms.

• Own assigned features, enhancements, defects, and technical improvements from discovery through release.

• Analyze transaction flows, data mappings, business rules, integration dependencies, and workflow requirements.

• Collaborate with engineering and architecture teams to define requirements for data ingestion, normalization, access, routing, and transaction processing.

• Write detailed product requirements, user stories, acceptance criteria, business rules, and workflow documentation.

• Refine and prioritize backlog items across new capabilities, production issues, data quality improvements, technical debt, and stakeholder requests.

• Investigate production support tickets and data issues using available documentation, logs, payloads, data samples, and system information.

• Provide engineering teams with clear context and actionable findings before escalating defects or issues.

• Collaborate with internal stakeholders to understand downstream product needs, operational issues, and platform challenges.

• Coordinate questions, dependencies, and delivery activities across U.S.-based stakeholders and distributed development teams.

• Support User Acceptance Testing (UAT), release readiness, defect triage, stakeholder communication, and post-release validation.

• Identify opportunities to improve data quality, transaction success rates, documentation, operational workflows, and system performance.

• Create and maintain clear product, process, data-flow, and integration documentation.

Required Qualifications

• 4+ years of experience in Product Management, Product Ownership, Business Analysis, or a related technical delivery role.

• Demonstrated experience supporting healthcare, health technology, revenue cycle, insurance, benefits, eligibility, enrollment, claims, or related data workflows.

• Experience working directly with software engineering teams in an Agile delivery environment.

• Strong experience writing detailed requirements, user stories, acceptance criteria, business rules, or technical documentation.

• Experience analyzing system integrations, APIs, data flows, batch processes, or structured data.

• Experience investigating defects, production issues, data discrepancies, transaction failures, or integration problems.

• Ability to translate complex business and data requirements into clear, actionable deliverables.

• Experience working with distributed or offshore development teams.

• Strong written and verbal English communication skills.

• Strong documentation skills and attention to detail.

• Ability to work independently with limited day-to-day direction.

• Ability to ask effective questions, research issues, and follow through on assigned responsibilities.

• Availability for regular overlap with U.S. Eastern Time business hours.

Preferred Qualifications

• Experience with transaction-based systems, data pipelines, event processing, APIs, or batch data flows.

• Familiarity with structured data formats such as XML, JSON, EDI, or similar formats.

• Familiarity with healthcare data standards such as X12, HL7, or FHIR.

• Experience with eligibility, demographic, enrollment, claims, remittance, or coverage data workflows.

• Experience working with clearinghouses, vendors, payers, or other external data partners.

• Experience supporting internal platforms, shared services, data repositories, or systems of record.

• Experience analyzing logs, payloads, data discrepancies, transaction failures, or system defects.

• Experience with data quality, data governance, matching logic, data normalization, or data reconciliation.

• Experience using tools such as Jira, Confluence, Azure DevOps, SQL, Postman, Splunk, or similar platforms.

• Experience working with U.S.-based product, engineering, and operational stakeholders.

Contract Expectations

• This is an execution-focused contract role.

• The contractor is expected to contribute quickly within an established product and engineering structure.

• The contractor should be able to independently produce requirements, investigate issues, and support delivery after an initial onboarding period.

• The contractor must be available for recurring meetings and collaboration during agreed U.S. Eastern Time hours.

• The agency must identify the specific candidate who will perform the work.

• Any proposed replacement resource must be approved before assignment.

• The contractor must comply with established security, confidentiality, data-handling, and documentation requirements.

Success Criteria

Within the First 30 Days

• Understand major platform workflows, stakeholders, backlog structure, delivery processes, and available documentation.

Within the First 60–90 Days

• Independently produce clear requirements, investigate issues, support backlog refinement, and coordinate effectively with engineering and business stakeholders.

Expected Outcomes

• Produce requirements that require minimal clarification or rework.

• Improve backlog readiness and delivery predictability.

• Analyze healthcare workflows, data mappings, business rules, and dependencies.

• Investigate issues before escalating them to engineering.

• Provide clear and actionable defect or production-support analysis.

• Document data flows, process behavior, system dependencies, and open questions.

• Support timely defect resolution, UAT, and release activities.

• Balance stakeholder requests with platform stability, data quality, and delivery capacity.

• Communicate effectively across U.S.-based product stakeholders and distributed development teams.

• Build trusted working relationships with product, engineering, architecture, and operations teams.

Candidate Submission Requirements

For each candidate, the agency must provide:

• Resume and summary of relevant healthcare platform experience.

• Specific examples of healthcare integrations or data workflows supported.

• Examples of requirements, user stories, or acceptance criteria personally written.

• An example of investigating a production defect, data issue, or transaction failure.

• Experience with XML, JSON, EDI, X12, APIs, or transaction systems.

• Experience working with U.S.-based stakeholders.

• Confirmation of required U.S. Eastern Time overlap.

• Availability and proposed contract duration.

• Hourly rate and commercial terms.

• Confirmation that the submitted candidate—not an unnamed substitute—will perform the work.