Technical Program Manager, Integrations - Health Systems

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.

Responsibilities

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 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, error handling, analytics instrumentation, multi-tenancy; Translate messy EMR realities — HL7 ADT messages, FHIR resources, 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, latency, 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, GDrive, OneDrive), clinical and drug references, scheduling systems, secure messaging — wherever clinicians already work

Requirements

BA/BS in a technical or analytical field (Computer Science, Engineering, Information Systems, Analytics, Mathematics, Physics, Applied Sciences or related); 4+ years in product, integrations or technical roles — we care more about what you’ve shipped than years on the clock; Real fluency with healthcare interoperability: SMART on FHIR, HL7 v2 (ADT, ORM, ORU), FHIR resources, OAuth flows for clinical apps. This is a requirement, not a nice-to-have; 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; A romantic streak about software and a belief that great design transforms someone’s day; 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; Strong opinions, weakly held: you’ll shift the room when you’re right

Benefits

$1,000 annual learning and development budget; $150/month health and wellness allowance; $500 home office budget; 26 weeks paid primary parental leave; 18 weeks paid secondary parental leave; fertility support up to $10,000; four weeks of work from anywhere per year; serious equity