Forward-Deployed Integrations Engineer

Reports to: Chief Technology Officer
Location: Burlington, VT (hybrid) or remote (no formal travel required)

OhMD is an AI patient communication platform trusted by thousands of healthcare organizations. Our product suite includes two-way patient texting, an AI voice and text assistant that handles inbound patient calls with a human always in the loop, and integrations with the leading ambulatory EHRs, including athenahealth, eClinical

Works, DrChrono, Elation, and Healthie.

Practices using OhMD reduce inbound call volume by 50% or more, which is the difference between a front desk that is drowning and one that can actually take care of patients.

Every healthcare organization operates on a unique technology stack.

One EHR exposes a clean FHIR endpoint. Another has a vendor-specific API with its own authentication and rate limits. A third has no supported API at all for the scheduling, patient, or clinical data our product needs. Even practices on the same EHR configure it differently, enforce different security requirements, and run entirely different front‑desk workflows.

OhMD still has to work.

Our products need accurate patient context, appointment data, and workflow state to resolve conversations safely. Our AI voice and text assistant cannot book, confirm, or reschedule an appointment it cannot see. Those integrations have to be reliable enough to support real patient interactions, secure enough to handle protected health information, and understandable enough that our customers trust what is happening.

Which brings us to the hard part, and to you.

This role owns the path between a practice's real‑world workflow and a working production integration. You'll sit with customers, understand how their systems actually operate, choose the right integration approach, build it, test it, launch it, and stay with it until it works cleanly.

Today that footprint spans more than a dozen EHRs. Our deepest integrations are athenahealth, eClinical

Works, DrChrono, Elation, and Healthie, and they run across three codebases: a .NET service that handles patient sync and chart write‑back, an Elixir platform that handles scheduling and reminders, and a Type Script and Playwright service for systems that don't offer a usable API. You won't need to be expert in all three on day one, but you will need to be comfortable reading and shipping in each.

This is not a role where you write a specification and hand it to someone else. You'll be the engineer in the customer conversation and the customer‑facing owner in the code.

Weeks 1–4: Live in the product. Learn how OhMD connects to EHRs today, shadow customer discovery sessions and go‑lives, and understand how patient, scheduling, and workflow data move through the platform. Get familiar with our integrations across EHRs.

Weeks 5–8: Own your first integration with support. Scope the customer’s requirements, select the right technical path, build or configure the integration, validate the data, and support the customer through testing. Ship something that runs against a real production workflow.

Weeks 9–12: Lead an integration workstream independently. Own technical discovery, implementation, validation, launch, and early production support. Bring us a point of view on what should become a reusable connector, what belongs in shared infrastructure, and where our current approach will break at scale.

You’ll work directly with healthcare organizations, EHR vendors, internal implementation teams, and engineering partners to understand what a customer needs and how their systems behave.

You’ll translate operational workflows into concrete…