Clover Health - Staff Product Manager

• Product strategy. Set the vision and roadmap for the longitudinal record. Find the highest-value problems across the products and programs that depend on it, and make the trade-offs among completeness, accuracy, timeliness, and investment. • Product strategy. • A trusted record. Define how care events and their dates, settings, providers, and facilities are represented consistently, and how medications, conditions, labs, and procedures connect to those events and to the patient's history over time. Set clinically grounded rules for combining sources that each describe part of the same care, so every fact can be traced to the evidence behind it. • A trusted record. • A unified record of acute events. One record of each hospitalization, ED and post-discharge care management built from multiple sources such as: ADT notifications, prior authorization and admission notices, facility claims, medical records (especially discharge documentation), and where the patient went at discharge. Anyone working with the patient sees the whole stay, from admission through discharge to the next setting of care. • A unified record of acute events. • Data for every use case. The record serves providers at the point of care and the programs that depend on complete care history: quality measurement (HEDIS), risk adjustment and RADV audits, payment integrity, and revenue operations. Providers, quality analysts, and operational teams all work from the same care history. • Data for every use case. • How every source becomes part of the record. You own patient matching, deduplication, normalization, and clinical terminology mapping, which turn raw data from each source into a trusted part of the patient's record. Every new source runs through them, so improvements are built once and reused across products. • How every source becomes part of the record. • Adoption. A canonical field counts only when clinicians use it. You own the path from definition to adoption: requirements, a migration plan per use case, and retiring fragmented, duplicate versions of the same data. • Adoption. • What success looks like • The record gets more complete, accurate, and timely, and you can show it with numbers. • Products and programs adopt the shared record and retire their own versions of it. • New customers and markets reach a usable patient record with less time and less one-off work. • You can show what those gains changed downstream: more complete evidence for quality and risk adjustment, earlier visibility into admissions and care transitions, and fewer inconsistencies across products. • You run a clear decision process with clinical and engineering partners, and definitions are documented, adopted, and applied consistently. • You should get in touch if • You have 8+ years of product management experience, including owning a data platform, data model, or shared data product used by multiple teams. • You have set product strategy for a platform with many internal consumers and made the trade-offs that came with it. • You have deep working knowledge of healthcare data and the clinical utility: institutional and professional claims, clinical documents such as C-CDA, FHIR resources, ADT feeds, and lab data. You know what part of a patient's care each covers and where the gaps are. • You have defined canonical or master data (patient, provider, facility, encounter, clinical concepts) and gotten other teams to adopt it. • You work in the data yourself: reviewing charts, investigating discrepancies, running analyses, and testing a definition against real records before it ships. You use AI to accelerate that work and know how to validate its output. • You have led cross-functional projects through influence, setting direction and driving delivery across engineering, clinical, and operations teams you don't directly manage. • You can point to a time a data improvement you owned contributed to a business result, such as a clinical outcome otherwise missed, avoided patient abrasion through duplication of care, physician time savings not chasing portals, or similar impact.