Technical Program Manager, Integrations

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 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. IF WE'D WORKED TOGETHER THE LAST 6 WEEKS, YOU'D HAVE: - 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 - Spent half-days with three customer accounts watching clinicians actually use the EMR alongside Heidi — Cerner clinician mapping, Athena multi-department provider setup, MEDITECH Expanse review-ambient flow — and come back with discrete tickets that changed the next sprint - 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 - Written the Integration Marketplace PRD that aligned Scribe, Comms and Evidence integrations into a single surface, with success metrics that commercial actually believes - 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 WHAT YOU'LL NEED - 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 IF YOU ANSWER 'NO' TO THESE QUESTIONS, THIS MAY NOT BE THE JOB FOR YOU: - Are you an execution powerhouse? - Have you shipped something this week? - Are you good at games? - Did you have a weird teenage hobby? - Are you able to execute without a legion of data analysts, product marketers, and research coordinators at your beck and call? - Does the prospect of making health systems a lot nicer make you feel fuzzy inside? HOW WE SHOW UP - Build for the next decade, not next quarter. Our targets are outrageous on purpose. The world's health doesn't have the luxury of incrementalism. - Lead, don't wait. We treat tomorrow's problems today. Sometimes we build what's needed before it's wanted, and we're fine with that. - Follow the evidence. Trust the patient. We pursue truth relentlessly. But when the subjective and objective disagree, we treat the patient, not the numbers. Ego is a comorbidity we can't afford. - Own the outcome. Everyone here carries the company. Raise problems with solutions, solve them end-to-end, and never be a bystander. - Ship, measure, go again. A button today, a workflow tomorrow. More iterations beat better planning. We're precise at pace, not reckless. - Live in clinicians' reality. Not the ideal workflow, the twenty-patients-before-lunch actual one. We build for exhausted humans, and we'd better be decent ones while we do it. WHY HEIDI? You’ll join a team focused on real-world impact over imaginary valuations and glossy PR. We live and breathe the challenges of modern health systems, and are laser-focused on exacting the change we’d like to see. We’re medicos, engineers, builders, and designers who’ve felt the moral and practical toll of what non-care feels like. True A-players progress extremely fast here. The nature of the scale-up game is demanding, but we value sustainable performance and mental health. You're trusted to perform, and you set your schedule. We operate on outcomes > inputs, not process theatre. We all take the bins out, metaphorically and literally. Building what we’re building isn’t always easy. But we didn’t choose easy, we chose to build something that actually matters. We hold ourselves to a higher standard because healthcare demands it. If you join Heidi, you recognise that the deeper question isn’t whether AI can solve the global healthcare crisis, but whose hands will shape it. The work is hard, but you will trust and admire the people you work beside, and rest easy knowing you’re doing the defining work of your career. WE TAKE CARE OF YOU We offer a $1,000 annual learning and development budget, a $150/month health and wellness allowance, a $500 home office budget, 26 weeks paid primary parental leave and 18 weeks paid secondary parental leave, fertility support up to $10,000, four weeks of work from anywhere per year, and serious equity.