Technical Program Manager, Integrations - Health Systems

Alt; Singapore; On-site; SGD 150,000 - 190,000; Full time

Job summary

Heidi is seeking a Product Manager for integrations who will own the platform framework, marketplace, and connectors to EMR systems across US, UK, Australia, Asia Pacific and beyond.

You will balance customer requests with engineering cost, guide which integrations to build next, and partner with regional teams to deliver scalable, reliable connectors.

Qualifications

• Experience defining product strategy and roadmaps for platform integrations.
• Ability to balance customer need, regional demand and engineering cost.
• Experience coordinating across multiple product lines and external partners.

Responsibilities

• Own product strategy and roadmap for Heidi’s integrations surface.
• Decide which integrations to build, deepen, or deprecate.
• Serve as central integration layer across product lines.
• Own the Integration Marketplace across Scribe and Evidence

Skills

Product strategy

Roadmap planning

Cross-functional leadership

API integrations

EMR integrations

Stakeholder management

Integration architecture

Tools

FHIR

SMART on FHIR

HL7

Job description

We’re Heidi

We're building the future of healthcare by giving every clinician the earth's finest AI Care Partner. In just 18 months, our clinical AI products have absorbed the administrative chaos of 73 million patient visits. Today, we support over 2.5 million patient sessions a week across 190+ countries.

Healthcare systems are failing us; clinicians spend more time on documentation than on patients, and the human connection that makes medicine worth practicing is eroding. Our mission is simple: double the world’s healthcare capacity and strengthen the human connection at its heart.

We found product-market fit with a freemium medical scribe that clinicians love. Now, we're expanding. Every task a clinician hands to Heidi is a patient who feels more attended to, a health system unclogged, and a clinician who gets to be a clinician again.

If you don’t choose easy and you want to build something way bigger than yourself then, choose the challenge, choose Heidi.

The Role

Heidi operates across US, UK, Australia, Asia Pacific 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 up a running operation with strong opinions about where it goes.

Half your time is building the platform - the framework, the standards, the shared infrastructure every connector benefits from. The other half is customer‑facing enablement: working directly with accounts, regional teams and commercial to get integrations live and keep them healthy. The hard part is that every customer feels bespoke, three regional teams are always pulling in different directions, and real EMR behaviour rarely matches the spec. You’ll need to hold the line between configuring for one account and building for the platform.

You need to understand how a real EMR write‑back actually works - encounter IDs, appointment IDs, patient context, addendum vs edit, side‑by‑side comparison, sectional mapping, the lookup tables that break in v1.0.2 of the desktop app. You need to know when a customer request is a one‑account fix and when it’s a framework change that touches every EMR. You need to be the person engineering trusts to call the build‑vs‑configure trade‑off, and the person commercial trusts when they’re scoping integration requirements into a contract.

This role is based in Asia Pacific, ideally located in Singapore.

What you'll do

• 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 held accountable to achieving them

• Decide which integrations to build, which to deepen, 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 or Evidence needs to connect to an external system, the path runs through you

• Own the Integration Marketplace as a single experience across Scribe and Evidence — including discover