Platform Product Manager

About the role

Senior PM for Data Platform, owning the data product layer that the rest of Nelly builds on top of. Your primary customers are internal: the Billing Agent team, AI Scribe, Treatment Plan Agent, Risk & Financing, and the engineers across Nelly who depend on reliable, well-defined data to ship.

What you'll do

• Own the canonical data model. Define what "patient history," "odontogram," "treatment plan," and "appointment" mean as products - their schema, grain, contracts, and SLAs. Resolve cross-team conflicts and drive decisions to clear, documented answers.
• Treat internal teams as your customers. Work directly with the Billing Agent, AI Scribe, and Treatment Plan Agent teams to understand their data needs, communicate what Core Data provides and when, and make it easy for them to build on top of your models rather than around them.
• Ship governance as a feature. Own data lineage, access controls, freshness SLAs, definitions, and GDPR compliance as first-class deliverables - not afterthoughts.
• Shape the roadmap. Maintain a clear view of which data domains to invest in and why, tied directly to Nelly's business outcomes - revenue, automation quality, operational efficiency, and regulatory risk.
• Build the platform layer. Define the pipeline infrastructure, orchestration patterns, and shared building blocks Core Data needs to own so teams stop reinventing them per use case.
• Unlock AI and ML. Partner closely with AI and ML teams to understand what they need from a data platform - evaluation datasets, versioned assets, as-of semantics, change tracking.

What you'll need

• Experience with internal data product. Not a dashboard or a BI report, rather something other engineering teams built on top of. You understand what it means to treat a data entity as a product with real consumers, contracts, and SLAs.
• Strong cross-functional PM experience: You can define requirements, align stakeholders with competing needs, write crisp specs, and drive decisions to closure - without engineering authority and without waiting for someone to hand you the problem statement.
• Thinking in canonical models and contracts. You're comfortable reasoning about grain, schema, ownership, and lineage at the right level of abstraction. You don't need to write pipelines, but you need to understand them well enough to make smart trade-offs with engineers.
• Ability to connect platform work to business outcomes. You know how to measure whether a data platform is working - adoption, data quality, SLA adherence, time-to-integration.
• High agency. You take ownership in ambiguous spaces. You don't wait for the problem to be fully defined before forming a point of view. You surface blockers early and drive alignment rather than consensus.

What they offer

• BVG ticket or Swapfiets membership
• Urban Sports membership
• Top-of-the-line equipment
• Flexible hours and hybrid setup in Berlin-Mitte
• Up to 4 weeks of workation
• Dog-friendly office with snacks and drinks