Payer Product Manager, Payer Data Platform

Senior Product Manager, Payer Data Platform Job Summary

The work of building that data asset — ingestion, transformation, enrichment, and attestation — is done by dedicated product and engineering teams. This role exists to bring the value of that work to life for the health plan. The Senior PM, Payer Data Platform owns Connect Admin for payers: the administrative interface through which health plans understand, manage, and act on their golden record.

This is where the entire data management investment becomes visible. A health plan shouldn’t have to trust that the platform is working — they should be able to see exactly what’s in their data, where it came from, what’s been enriched and how, where the gaps and risks are, and what actions are available to them. This PM makes that experience real.

This role works in close partnership with the product managers responsible for data ingestion and enrichment, data attestation and validation, analytics infrastructure, bulk APIs, and the Enterprise MCP. Those teams own the underlying technology. This PM is their primary internal customer for the payer-facing surface — defining what health plans need to see and do, and partnering across the product organization to make sure the right data flows through to support it.

• Own the product roadmap for Connect Admin as a payer‑specific data management interface — the primary surface through which health plan data stewards, network operations teams, and compliance staff interact with their golden record.
• Design the golden record review experience: enabling payers to view the authoritative record for any clinician, care location, or value‑add program in their network, including the full relationship map — organizational hierarchies, network affiliations, care team structures, supplemental benefits, and program eligibility.
• Build the data provenance layer: health plans should be able to see exactly what data has been augmented or enriched, which source it came from, when it was last updated, and what confidence level the system has assigned. Transparency is what makes the golden record trustworthy.
• Design approval workflows for enriched and AI‑generated content: payers configure which fields Kyruus can augment automatically and which require human review before flowing through to the member‑facing directory. For example, a plan may auto‑approve photo sourcing but require review of AI‑generated bios before they publish.
• Surface clinicians suspected of attesting to incorrect or inconsistent data — presenting those cases with supporting evidence as an actionable work queue for the plan’s network operations or attestation team, not a static report.

• Own the analytics surface within Connect Admin. Health plans should be able to answer questions they currently cannot:
  What percentage of my network has a photo? A scheduling link? Embedded real‑time availability? A consumer rating? What is my estimated ghost network exposure by specialty and region? Where is my data quality trending over time?
• Surface enrichment opportunity intelligence: show payers what Rev Spring data or third‑party integrations are available that they are not currently using, what those capabilities would add to their directory, and what it would take to activate them — whether that is a premium add‑on, an integration approval, or a data‑sharing agreement with a third party. Turn invisible data gaps into informed decisions.
• Build compliance and audit reporting within the Connect Admin surface: attestation cycle performance, primary source monitoring flags, directory accuracy trending, and documentation that supports CMS audits and No Surprises Act compliance.
• Partner closely with the analytics team, who own the underlying data infrastructure, to ensure the model supports the reporting surface this role defines. Serve as the primary product voice for what payers need to see — not just what is technically available.

• Serve as the primary internal customer and named partner for the product managers who own bulk APIs, the Enterprise MCP, and…