SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Doctolib is seeking a Product Manager to own the end-to-end patient data collection programme across the Patient Profile team. Your mission is to make the patient health record complete, accurate, and current enough to power downstream features like health recommendations, care plans, and assistant experiences.
A patient record is built from four channels: patient self-entry, data shared during consultation preparation, data retrieved from health professionals' systems, and third-party integrations (Apple Health, Google Health Connect, national health record services). You will own the outcome across all four channels, working through cross-functional partnerships since three channels are owned by other teams. This is a highly leveraged position requiring influence without direct authority.
Key Responsibilities:
- Own the end-to-end patient data collection programme and be accountable for results across all four channels
- Define what a "useful record" means for downstream teams, make it measurable, and instrument dashboards rather than inherit them
- Partner with channel-owning teams to set inter-team contracts, agree on contribution models, and arbitrate collection priorities
- Own record quality and freshness (not volume), alongside health data storage consent, patient account, and online identity
- Ship the data-serving layers: patient feature store, patient context service, and Patient Health Record feature
- Lead the Patient Profile team's roadmap and delivery from PHR and trackers through to feature store and context service
You will work within a hard regulatory perimeter involving health data, GDPR, and consent-by-design principles.
Requirements:
- Owned a coverage, completeness, or data quality metric as primary objective; can articulate the baseline, outcome, and timeline
- Experience working at millions-of-records scale
- Moved metrics through teams that did not report to you, setting interfaces, contracts, and SLAs with partner teams
- Shipped under hard regulatory or consent constraints (health, finance, or identity) with privacy and consent by design
- Real technical depth: owned a data platform component as a product, feature store, context/profile service, or identity layer
- Fluent in English
Nice-to-have:
- Experienced a data quality problem surface only at a downstream consumer and changed working practices as a result
- Built a completeness or quality definition and driven organizational adoption
- Worked on interoperability, health data standards, or identity and account models
