Forward Deployed Engineer

Open Loop was co-founded by CEO, Dr. Jon Lensing, and COO, Christian Williams, with the vision to bring care anywhere. Our telehealth support solutions are thoughtfully designed to streamline and simplify go-to-market care delivery for companies offering meaningful virtual support to patients across an expansive array of specialties, in all 50 states.

Open Loop is the clinical and operational infrastructure that digital-health brands, clinics and employers use to run virtual care across all 50 states. Our clients put their brand on the front end; everything behind it runs on us: clinicians, intake, scheduling, charting, pharmacy and fulfillment, payments and licensing. Clients reach that infrastructure through one client platform, from a no-code storefront to a full Partner API, and our job is to make it effortless for them to adopt.

Forward Deployed Engineering is how we build that platform with real clients instead of guessing. An FDE embeds with a client, works in the client’s own codebase, and builds their integration against Open Loop's production API. Whatever the client needs that the platform cannot do yet is filed as a platform gap and built once, centrally, so every client inherits it.

The work product of an FDE is not the client's integration; it is the reusable asset that client forced into existence: a recipe others start from, an executable check behind every claim in our docs, a client manifest that makes the impact of any platform change computable, and the SDKs, agents and tooling that make the next deployment faster than the last.

As a Staff Forward Deployed Engineer you take the deployments nobody else can, and you set the pattern the rest of the team runs. You are the technical architect of a pod: you own the client manifest, decide what is bespoke and what generalizes, are the one voice to our platform teams on API behaviour, and build the AI-native tooling that lets one engineer carry two clients.

You write production code in two places, the client's system and ours, and you tell our own sales team when a commitment should not be made.

• Build for clients, in their codebase, against our API. Embed with a client's engineering team and stand up their integration on Open Loop's Partner API: their app, their data, their identity, their legacy systems. Own the outcome through go-live and the weeks after it. Never wire around the platform: where the API falls short, file the gap with the endpoint it stands in for, and leave a dated, time-boxed workaround at most.

• Build AI SDKs and agentic solutions for clients. Design and ship the backend and frontend systems that let a client build on us with AI in the loop: SDKs and reference implementations, a CLI and machine-readable docs a client can hand to their own coding agent, and agentic workflows on our API (intake, routing, support and refill journeys) with human review by design, evaluations before launch and monitoring after.

• Architect and own the AI-assisted way FDE works. Own the agent roster that runs our deployments: the tenant readiness gate, the conformance checks against a live tenant, seeding checkers, docs-freshness and superseding drafts, gap filing, client communication drafts. Every agent output is a draft a human approves; you decide where the human sits and how you know the agent is right.

• Build the systems that improve Open Loop's API for everyone. Turn what one client needed into what every client gets: additive recipes and checks on the shared cookbook, client manifests and impact analysis, API conventions for how domain teams expose capabilities to clients, and the evidence that moves a recurring workaround into the platform roadmap. The measure is how much less of…