Product Lead, Ambience Healthcare

• 5+ years of product management experience with direct ownership of platforms, shared systems, or cross-product experience layers
• Prior experience as a software engineer with strong system design fundamentals
• Experience scaling platforms through growth — complex migrations, platform-wide changes, and cross-team coordination
• Track record of building internal tooling that created real leverage for go-to-market, finance, or operational teams
• Technical fluency in APIs, licensing systems, design systems, and workflow orchestration
• Comfort working with Data/Analytics — defining requirements, ensuring instrumentation, and using data to inform decisions
• Strong communicator who can align engineers, clinicians, executives, and partner teams
• Based in SF, available to be in the office 3x/week

Desirable

• As our Platform Product Lead, you'll own the core platform — the shared foundation that every Ambience product is built on
• We serve thousands of clinicians and nurses across leading health systems like Mayo Clinic and Cleveland Clinic, with a product surface that spans documentation, visit prep, and coding across ambulatory, emergency, and inpatient care
• The platform has to be reliable and coherent across all of that — multiple products, multiple care settings, multiple EMR environments — while continuing to evolve quickly
• Done well, this platform scales from thousands of clinicians to hundreds of thousands, across more health systems, more care settings, and more product capabilities, without the foundation becoming the constraint
• This is a Staff / Senior Staff-level IC role that reports directly to the Head of Product
• You'll work closely with engineering, design, data, and internal partner teams
• Scale reliability and performance: Lead migrations and architectural improvements that support significant user growth, reduce fragility, and cut unnecessary internal dependencies
• Drive platform quality: Identify and systematically address the platform-level issues that generate the most support burden and impact clinician experience
• Maintain shared infrastructure: Evolve Ambience's design language and shared system components so new product lines can integrate without one-off work
• Own foundational tooling: Build and maintain capabilities like feature flagging that help the broader product org ship more predictably
• Growth Infrastructure — Onboarding, Activation & Internal Tooling
• Own onboarding and activation: Own the infrastructure that shapes a clinician's first experience with Ambience — account provisioning, licensing, cross-product preferences, and dashboards — moving from manual configuration to self-service experiences that get clinicians to value faster
• Build internal partner tooling: Deliver tools that let internal teams operate independently at scale:
• Care Transformation: Access controls, reporting, and configuration management
• Finance: Licensing and billing integrations
• GTM: Demo environments and tooling
• Instrument platform health: Partner with Data and Analytics to build onboarding telemetry, funnel tracking, and operational reporting