3+ years of experience in building integrations within healthcare or enterprise SaaS environments.
Hands-on experience with HL7v2 and FHIR, as well as REST APIs and authentication methods (OAuth, SAML/OIDC).
Proficiency in production coding using Python or TypeScript.
Familiarity with EHR systems like Epic, Oracle Health, or athenahealth.
Demonstrated ability to transform one-off builds into reusable components.
Strong communication skills to effectively manage customer expectations and technical feasibility.
Responsibilities
Join presales discovery to assess customer systems and provide feasibility assessments.
Estimate work effort, dependencies, and risks for integration projects.
Classify integration requests and determine the appropriate approach for each.
Build integrations between Heidi and various customer systems, including EHRs and data warehouses.
Design integrations as configurable components for future reuse and maintain documentation.
Act as the technical lead for customer IT and security teams during integration processes.
Review project scope and manage changes to ensure credible planning.
Benefits
Opportunity to work on innovative healthcare integration projects.
Collaborative environment with cross-functional teams.
Potential for professional growth in a rapidly evolving field.
Access to a shared library of integration patterns and resources.
Engagement with leading healthcare technology and systems.
Full Job Description
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.
You keep boundaries clean. You own customer-specific integrations. You send core product changes to engineering through the TPM as precise requirements, and you route live defects to Support Engineering with your diagnosis attached.
People trust your translation. Customer IT and security teams treat you as a peer. The TPM hears from you which integration patterns deserve to become product.
What you'll do
Scoping and feasibility
Join presales discovery on integration-heavy deals. Assess the customer's systems, APIs and data constraints, then give a clear answer on feasibility.
Size the work: effort, dependencies, risks and the assumptions behind them. Your estimates feed the SOW.
Classify each request as reuse of an existing integration, configuration, custom build, core product change or roadmap item.
Push back on commitments you can't back with a credible plan.
Write technical designs that FDEs, product and customer IT can all act on without rework.
Custom integration build
Build integrations between Heidi and customer systems: EHRs, identity providers, data warehouses, scheduling and internal tools. Expect HL7v2, FHIR, REST APIs, SFTP and webhooks.
Set up agents and agentic workflows that connect to customer data and fit their clinical and operational workflows.
Own technical testing, support customer UAT and run technical go-live.
After go-live, monitor the integration and iterate with the customer's integration team.
Building for reuse
Design each build as a configurable component. Parameterize customer-specific logic and keep configuration separate from code.
Maintain the team's shared library of connectors, integration patterns and runbooks.
Document each build so another engineer can deploy, support or extend it without you.
Spot repeat asks across customers and bring them to the TPM as candidates for productization.
Technical partnership
Act as the technical lead with customer IT, security and integration teams.
Give Compliance the technical input and evidence they need for security questionnaires, privacy reviews and IT assurance. Compliance owns those processes, and Security, Privacy and Clinical Safety keep approval authority.
Plan work around customer governance gates: clinical safety sign-off, privacy approval and change-control windows.
Handover and scope control
Review the signed SOW, discovery notes, architecture, acceptance criteria and risk log before build begins.
Return a handover if a blocking risk, unclear scope or unsupported commitment prevents a credible plan.
Route material scope changes through the CSM, SE and AE before you commit work or dates.
What you'll bring
3+ years building integrations in healthcare or enterprise SaaS
Hands-on HL7v2 and FHIR experience, plus REST APIs and auth (OAuth, SAML/OIDC)
Production code in Python or TypeScript
Experience with EHRs such as Epic, Oracle Health or athenahealth
A track record of turning one-off builds into reusable components
The confidence to tell a sales lead "not as scoped, but here's what we can do"
