Heidi

Healthcare

TechnicalProductManager-Integrations

London, United Kingdom FULL TIME Remote Friendly
Market Sentiment
HIGH DEMAND

Neural analysis suggests this role is
optimal for Mid candidates.

The Brief

“Technical Product Manager - Integrations at Heidi. Skills: product strategy and roadmap for integrations, integration framework ownership, Integration Marketplace ownership, EMR and non-EMR connector management, healthcare interoperability, build-vs-configure trade-offs, AI tool usage, LLM concept and system fluency. Own product strategy and roadmap for Heidi’s integrations surface — the framework, the marketplace, and the individual EMR and non-EMR connectors — setting clear goals and being hel”

What You'll Achieve.

setting clear goals and being held accountable to achieving them; Set the standard for integration quality and reliability — error handling, write-back confirmations, latency, recovery from upstream failures — and be accountable to it; Shipped the migration of an existing integration (e. g. Athena) onto the new framework and unblocked sectional notes write-back and mobile parity as a downstream consequence; Written the Integration Marketplace PRD that aligned Scribe, Comms and Evidence integrations into a single surface, with success metrics that commercial actually believes

Industry & Context.

Healthcare
Problems you'll solve

Translate messy EMR realities ... into product specs engineering can build against; Diagnosed why outbound write-back was failing for a specific Veradigm customer, traced it through the logs to a feature flag mismatch, and shipped the fix without waiting for a release train; Made a build-vs-configure call on an NHS letter-flow request — proved demographic extraction from a couple of ADT messages before committing to a full integration engine connection — and brought the regional team along for the ride

What They're Looking For.

Must Have

4+ years in product, integrations or technical roles, Real fluency with healthcare interoperability: SMART on FHIR, HL7 v2 (ADT, ORM, ORU), FHIR resources, OAuth flows for clinical apps, Experience shipping platform or framework products where what you build for one customer becomes a configurable module for the next, Comfort making build-vs-configure trade-offs daily, and the judgment to know when a shortcut today costs three deployments tomorrow, The ability to hold a coherent roadmap under pressure from multiple regional teams with competing priorities, Diagnostic data fluency: you can read integration logs and distinguish a model problem from a framework problem from a customer-specific configuration issue, You build with AI tools (Cursor, Claude Code, whatever ships faster) and can show what you’ve made with them, Fluency with core LLM concepts and systems (prompting, fine-tuning, embeddings, retrieval, evaluation) and the judgment to translate these into reliable, user-facing products

Nice to Have

A romantic streak about software and a belief that great design transforms someone’s day, opinions, weakly held: you’ll shift the room when you’re right

What You'll Do.

Own product strategy and roadmap for Heidi’s integrations surface — the framework

and the individual EMR and non-EMR connectors — setting clear goals and being held accountable to achieving them

Decide which integrations to build

and which to deprecate

balancing customer demand

regional pull and engineering cost

Serve as the central integration layer for Heidi’s product lines — when Scribe

Comms or Evidence needs to connect to an external system

the path runs through you

Own the Integration Marketplace as a single experience across Scribe

Comms and Evidence — including discoverability

multi-player setup and the closed loop on integration requests from growth

Drive the migration to the new integration framework so every connector benefits from shared infrastructure: sectional notes write-back

analytics instrumentation

Translate messy EMR realities — HL7 ADT messages

Athena shell accounts

Cerner addendum behaviour

MEDITECH Expanse approval pathways

Best Practice workflows — into product specs engineering can build against

Set the standard for integration quality and reliability — error handling

write-back confirmations

recovery from upstream failures — and be accountable to it

Be the connective tissue between US

UK and APAC regional teams: absorbing their competing priorities and translating them into a coherent platform roadmap rather than a queue of one-offs

Work directly with EHR partners

integration engines and platform teams to stay ahead of API changes and certification requirements

Connect field signal back to the framework: when the same gap shows up across three accounts or three regions

consolidate it into a platform fix instead of three bespoke ones

Expand integrations beyond EMRs — document stores (SharePoint

clinical and drug references

secure messaging — wherever clinicians already work.

How You'll Work.

Team & Collaboration

Be the connective tissue between US, UK and APAC regional teams: absorbing their competing priorities and translating them into a coherent platform roadmap rather than a queue of one-offs; Work directly with EHR partners, integration engines and platform teams to stay ahead of API changes and certification requirements; Connect field signal back to the framework: when the same gap shows up across three accounts or three regions, consolidate it into a platform fix instead of three bespoke ones

Process & Methodology

Own product strategy and roadmap, setting clear goals and being held accountable to achieving them, Decide which integrations to build, which to deepen, and which to deprecate, Drive the migration to the new integration framework, Made a build-vs-configure call on an NHS letter-flow request — proved demographic extraction from a couple of ADT messages before committing to a full integration engine connection — and brought the regional team along for the ride, Said “no” to a one-off customer integration request and turned it into a framework capability that unblocked three other deals across two regions

Full Job Description

WHO WE ARE   Healthcare needs a better rhythm: one that keeps care continuous and deeply human. Heidi is building an AI Care Partner that works alongside clinicians to make that possible. We’re a team of doctors, engineers, designers, researchers, and creatives building tools that help clinicians stay focused on what matters most: their patients. In just 18 months, Heidi has given back more than 18 million hours to healthcare professionals — supporting 73 million patient visits in 116 countries. Today, more than two million patient visits each week are powered by Heidi worldwide. Backed by nearly $100 million in funding, we’re growing in the US, UK, Canada, and Europe, partnering with leading health systems including the NHS, Beth Israel Lahey Health, and Monash Health.   THE ROLE Heidi operates across US, UK, Australia and beyond — and integrations are the connective tissue that makes it work everywhere. This PM role is a central platform function: the common layer through which every Heidi product (Scribe, Comms, Evidence) interfaces with the external systems clinicians already live in.   EMRs. Scheduling systems. Document stores. Clinical references. Secure messaging. Wherever clinicians already work, Heidi should plug in without making them think.   The integration stack is real and in motion: SMART on FHIR launches inside the chart, structured write-back into Epic, Cerner, Athena, MEDITECH Expanse, Veradigm, Best Practice. HL7 ADT feeds for patient demographics. Pre-charting from appointment data. The Integration Marketplace — surfacing Scribe, Comms and Evidence integrations in one place — is being rebuilt now, and you’ll own where it goes next.   You’ll own the integration framework, the customer-facing marketplace, and the roadmap that decides which connector ships next and how deep it goes. A small dedicated engineering squad sits alongside you. A new integration framework is rolling out. The marketplace is being unified across product lines. You’re picking

Free ATS check

Applying for this Technical Product Manager - Integrations role?

Most applicants get filtered before a human reads their resume. See if yours makes the cut.

How to Apply on Ashby

  • Ashby is a fast modern ATS — most applications take under 3 minutes.
  • The resume parser is strong; verify parsed experience dates and job titles.
  • Custom screening questions are often scored algorithmically — answer completely.
  • Location field affects geo-based screening; use your actual metro area.

ANONYMOUS · UNFILTERED

What do employees actually say about Heidi?

Real rants from real employees. Read before you apply.

Read Company Rants →