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 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 our San Francisco office.
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, 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, 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?
The Way We Work
Build to Last
We design for safety and reliability so clinicians, patients, and our teams can trust what we build every day.
Own Your Practice
Ideas rise on merit, not title, and everyone shares responsibility for the standards we set together.
Move Fast, Stay Steady
We move quickly but never at the cost of trust. Progress only matters if people can depend on what we make.
Make Others Better
Honest feedback, steady support, and shared growth keep our teams improving together.
Why you will flourish with us
- Flexible hybrid working environment, with 3 days in the office.
- A generous personal development budget of $500 per annum
- Learn from some of the best engineers and creatives, joining a diverse team
- Become an owner, with shares (equity) in the company, if Heidi wins, we all win
- The rare chance to create a global impact as you immerse yourself in one of Australia’s leading healthtech startups
- If you have an impact quickly, the opportunity to fast track your startup career!
Heidi is dedicated to creating an equitable, inclusive, and supportive work environment that brings people together from diverse backgrounds, experiences, and perspectives. Our strength is in our differences. We're proud to be an equal opportunity employer and welcome all applicants as we're committed to promoting a culture of opportunity for all.
#J-18808-Ljbffr