About The Position

Become a part of our caring community The Lead Data Product Owner supports the lifecycle of Humana Pharmacy Solutions (PBM) and Domani joint venture data products, ensuring data assets are trusted, governed, discoverable, and reusable across analytics, operational workflows, digital experiences, and emerging AI-enabled self-service. This role translates PBM and Domani needs into high-quality user stories and a well-managed backlog, enabling engineering teams to deliver reliable, productized data—particularly as data is modernized and migrated to Databricks. The role partners closely with a Data Product Manager (DPM) who owns product strategy and outcomes. The Lead Data Product Owner is primarily execution-focused, responsible for story definition, backlog management, delivery alignment, and ensuring existing governance and stewardship models are consistently applied and aligned with enterprise data policy within an Agile SAFe environment. Key Responsibilities 1) Own the PBM & Domani Data Product Backlog (New + Legacy) Partner with the Data Product Manager to translate PBM and Domani strategy into a prioritized, story-driven backlog. Maintain an inventory of PBM and Domani data products (e.g., claims adjudication, benefits/formulary, utilization management, pricing/rebates, network, eligibility). Identify high-value legacy datasets—especially those critical to Domani—that require clarification, remediation, or protection during modernization. Ensure backlog prioritization drives measurable outcomes such as improved adoption, reduced defects, and faster time-to-insight. 2) User Story Leadership (Primary Execution Responsibility) Write clear, testable user stories that reflect PBM and Domani consumer needs (analytics, operational, reporting, digital). Decompose complex cross-entity requirements into incremental stories (e.g., curated datasets, Domani-specific views, governed extracts). Define acceptance criteria that reinforce: Correct business semantics Data quality expectations Documentation completeness Readiness for consumption 3) Productize Data During Modernization / Migration to Databricks Ensure PBM and Domani data modernization efforts result in managed data products, not unmanaged technical artifacts. Partner with engineering and architecture to ensure migrated datasets meet established standards for: Business definitions and semantics Lineage and dependency visibility Versioning and change management Reconciliation and validation for cutover (especially financial and utilization data impacting Domani) 4) Sustain and Operationalize Existing Data Governance & Stewardship (Reframed to reflect maturity, not net-new design) Apply and reinforce existing governance and stewardship models across PBM and Domani data products rather than creating new frameworks. Ensure datasets consistently align with enterprise data policy, standards, and decision rights. Partner with data governance, stewardship, and domain leaders to: Maintain clear ownership and accountability for PBM and Domani datasets Ensure required metadata, glossary alignment, and documentation remain current Identify gaps where governance standards are not consistently applied and convert them into backlog items Support ongoing data quality management by: Translate existing CDEs and quality rules into relevant delivery stories Track recurring defects and ensure fixes are prioritized and durable Ensure dataset lifecycle practices (retention, deprecation, evolution) are followed in alignment with corporate policy and joint venture agreements. 5) Enable Self-Service Analytics & AI Readiness Through Consistency Improve usability and trust by ensuring PBM and Domani data products consistently meet established standards for: Definitions and naming conventions Documentation and examples Secure access and entitlement patterns Ensure data products are reusable across teams while respecting Domani-specific governance, contractual, and regulatory constraints. 6) Support Operational & Digital Experiences with Data Contracts Partner with operational, digital, and Domani stakeholders to ensure data products support real-world needs. Define and maintain data contracts that clarify: Availability and freshness expectations Schema evolution and change notification PBM vs. Domani consumer responsibilities 7) Deliver Through SAFe Agile with Backlog Discipline Operate within SAFe with a story-first mindset: Participate in PI planning, refinement, and ART ceremonies Ensure backlog readiness and dependency clarity Coordinate across engineering, analytics, platform, security/compliance, and JV partners Track delivery and health metrics such as adoption, quality incidents, freshness Service level agreements, and consumer satisfaction. Use your skills to make an impact

Requirements

  • Bachelor's degree (or equivalent experience)
  • 6–10+ years in data product ownership, analytics delivery, or related roles
  • Comfortable performing SQL-based data exploration/validation
  • Experience working within established governance frameworks and aligning delivery to enterprise standards

Nice To Haves

  • Ability to write high-quality user stories and acceptance criteria for data products
  • Experience supporting joint ventures or multi-entity data ecosystems
  • Databricks / lakehouse modernization experience
  • PBM, pharmacy, claims, or regulated healthcare experience
  • Familiarity with DAMA-aligned concepts applied pragmatically
  • Proven ability to operationalize governance through delivery, not process creation

Responsibilities

  • Own the PBM & Domani Data Product Backlog (New + Legacy) Partner with the Data Product Manager to translate PBM and Domani strategy into a prioritized, story-driven backlog.
  • Maintain an inventory of PBM and Domani data products (e.g., claims adjudication, benefits/formulary, utilization management, pricing/rebates, network, eligibility).
  • Identify high-value legacy datasets—especially those critical to Domani—that require clarification, remediation, or protection during modernization.
  • Ensure backlog prioritization drives measurable outcomes such as improved adoption, reduced defects, and faster time-to-insight.
  • Write clear, testable user stories that reflect PBM and Domani consumer needs (analytics, operational, reporting, digital).
  • Decompose complex cross-entity requirements into incremental stories (e.g., curated datasets, Domani-specific views, governed extracts).
  • Define acceptance criteria that reinforce: Correct business semantics Data quality expectations Documentation completeness Readiness for consumption
  • Ensure PBM and Domani data modernization efforts result in managed data products, not unmanaged technical artifacts.
  • Partner with engineering and architecture to ensure migrated datasets meet established standards for: Business definitions and semantics Lineage and dependency visibility Versioning and change management Reconciliation and validation for cutover (especially financial and utilization data impacting Domani)
  • Apply and reinforce existing governance and stewardship models across PBM and Domani data products rather than creating new frameworks.
  • Ensure datasets consistently align with enterprise data policy, standards, and decision rights.
  • Partner with data governance, stewardship, and domain leaders to: Maintain clear ownership and accountability for PBM and Domani datasets Ensure required metadata, glossary alignment, and documentation remain current Identify gaps where governance standards are not consistently applied and convert them into backlog items
  • Support ongoing data quality management by: Translate existing CDEs and quality rules into relevant delivery stories Track recurring defects and ensure fixes are prioritized and durable Ensure dataset lifecycle practices (retention, deprecation, evolution) are followed in alignment with corporate policy and joint venture agreements.
  • Improve usability and trust by ensuring PBM and Domani data products consistently meet established standards for: Definitions and naming conventions Documentation and examples Secure access and entitlement patterns
  • Ensure data products are reusable across teams while respecting Domani-specific governance, contractual, and regulatory constraints.
  • Partner with operational, digital, and Domani stakeholders to ensure data products support real-world needs.
  • Define and maintain data contracts that clarify: Availability and freshness expectations Schema evolution and change notification PBM vs. Domani consumer responsibilities
  • Operate within SAFe with a story-first mindset: Participate in PI planning, refinement, and ART ceremonies Ensure backlog readiness and dependency clarity Coordinate across engineering, analytics, platform, security/compliance, and JV partners Track delivery and health metrics such as adoption, quality incidents, freshness Service level agreements, and consumer satisfaction.

Benefits

  • Humana provides medical, dental and vision benefits, 401(k) retirement savings plan, time off (including paid time off, company and personal holidays, volunteer time off, paid parental and caregiver leave), short-term and long-term disability, life insurance and many other opportunities.
© 2024 Teal Labs, Inc
Privacy PolicyTerms of Service