Implementation Engineer
Posted 8 Oct 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 3+ yrs
- Management level
- Individual contributor
- Employment
- On-Site
- Contract
- Full-time
No salary listed for this role.
We’re Heidi.
We're building the future of healthcare by giving every clinician the earth's finest AI Care Partner. Our platform has absorbed the administrative chaos of 175 million patient visits and supported 67 million clinical hours. Today, we support 2.8 million patient sessions a week across 190+ countries, in 110 languages and over 200 specialties.
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 capacity for care 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.
We’ve grown annual recurring revenue from $1 million to $50 million in two years.
To go further, we’ve secured US$340 million: a $100 million Series C led by Blackbird, with Phoenix Court, Point72 Private Investments and Headline, alongside a $240 million growth investment led by General Catalyst’s Customer Value Fund.
If you want to join us in doing work worth shipping, jump in.
The role
Heidi is investing in a dedicated Implementations Engineer to own the stability and scale of our accounts and to build the account health infrastructure that lets us move from reactive fixes to proactive engineering.
You'll work closely with our GTM teams and report to the NA Manager of Solutions.
Customers ask for things Heidi doesn't do out of the box. One wants a write-back into an EHR we haven't connected yet. Another wants a data feed into a quality dashboard. You decide if the ask is technically feasible, you scope it and you build it as a pattern the team can deploy again. Your ownership starts at enterprise handover. It ends once the integration passes acceptance criteria, the customer signs off, you've documented the build for reuse and the account moves into hypercare or BAU support.
Success in this role looks like:
-
You build it yourself. You write, configure, test and ship integrations: APIs, HL7 and FHIR interfaces, webhooks, data exports, agentic workflows.
-
Your work compounds. The integration you build for one health system becomes a documented, configurable component the next account can deploy in days.
-
You make the feasibility call. Sales and presales bring you customer asks. You tell them what's possible, how much effort it takes and what risk it carries before anyone commits to a date.