Implementation Engineer

Heidi•New York, NY

About The Position

Heidi is seeking a dedicated Implementation Engineer to ensure the stability and scalability of their accounts. This role involves building account health infrastructure to shift from reactive fixes to proactive engineering. The Implementation Engineer will collaborate with Go-To-Market teams and report to the NA Manager of Solutions. The position requires assessing technical feasibility of customer requests, scoping and building integrations (APIs, HL7 and FHIR interfaces, webhooks, data exports, agentic workflows), and owning the process from enterprise handover through acceptance criteria, customer sign-off, documentation for reuse, and transition to hypercare or BAU support.

Requirements

  • 3+ years of experience building integrations in healthcare or enterprise SaaS.
  • Hands-on experience with HL7v2 and FHIR.
  • Proficiency with REST APIs and authentication methods (OAuth, SAML/OIDC).
  • Production code experience in Python or TypeScript.
  • Experience with EHRs such as Epic, Oracle Health, or athenahealth.
  • A track record of transforming one-off builds into reusable components.
  • The ability to communicate feasibility and alternative solutions to sales leads, such as stating "not as scoped, but here's what we can do."

Responsibilities

  • Build integrations between Heidi and customer systems, including EHRs, identity providers, data warehouses, scheduling tools, and internal tools, utilizing HL7v2, FHIR, REST APIs, SFTP, and webhooks.
  • Set up agents and agentic workflows that connect to customer data and align with their clinical and operational workflows.
  • Own technical testing, support customer User Acceptance Testing (UAT), and manage technical go-live.
  • Monitor integrations post-go-live and iterate with the customer's integration team.
  • Design each build as a configurable component, separating customer-specific logic and configuration from code.
  • Maintain the team's shared library of connectors, integration patterns, and runbooks.
  • Document each build to enable other engineers to deploy, support, or extend it.
  • Identify recurring customer requests and propose them to the Technical Program Manager (TPM) for productization.
  • Act as the technical lead for customer IT, security, and integration teams.
  • Provide technical input and evidence to Compliance for security questionnaires, privacy reviews, and IT assurance.
  • Plan work around customer governance gates, including clinical safety sign-off, privacy approval, and change-control windows.
  • Review the signed Statement of Work (SOW), discovery notes, architecture, acceptance criteria, and risk log before commencing build.
  • Return a handover if blocking risks, unclear scope, or unsupported commitments prevent a credible plan.
  • Route material scope changes through the Customer Success Manager (CSM), Solutions Engineer (SE), and Account Executive (AE) before committing work or dates.
  • Join presales discovery for integration-heavy deals, assessing customer systems, APIs, and data constraints to determine feasibility.
  • Size work, including effort, dependencies, risks, and assumptions, to inform the SOW.
  • Classify requests as reuse of existing integrations, configuration, custom build, core product change, or roadmap item.
  • Push back on commitments that cannot be supported by a credible plan.
  • Write technical designs that Field Development Engineers (FDEs), product teams, and customer IT can execute without rework.

Benefits

  • Sustainable performance and mental health support.
  • Flexibility in setting your schedule.
  • Focus on outcomes over inputs, not process theatre.
  • Opportunity to do defining work.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service