Forward Deployed Engineer

About OpenLoop

OpenLoop 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.

About the Role

As a Senior Forward Deployed Engineer you own a client deployment end to end. You embed with the client's engineering team, build their integration against our Partner API, and carry it through go-live and the weeks after it. You write production code in two places, the client's system and ours, and every deployment you run leaves behind something reusable: a recipe the next engineer starts from, a check that locks a claim in our docs, a gap filed with the evidence to back it.

What You'll Do

• Build for clients, in their codebase, against our API. Embed with a client's engineering team and stand up their integration on OpenLoop'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 with AI in the loop. Ship the backend and frontend work that lets a client build on us with AI in the loop: SDK contributions and reference implementations, machine-readable docs a client can hand to their own coding agent, and agentic workflows on our API with human review by design, evaluations before launch and monitoring after.

• Run deployments on the agent roster. Use and improve the agents that run our deployments: the tenant readiness gate, 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, and you are that human before anything reaches a client.

• Feed the platform. Turn what your client needed into what every client gets: additive recipes and checks on the shared cookbook, a client manifest you keep current, and the evidence that moves a recurring workaround into the platform roadmap. The measure is how much less of us the next client needs.

• Turn ambiguity into a plan. Take a client ask that is vague or over-promised and produce a scoped, sequenced plan, with a clear statement of what we are not doing and what the API does not do yet.

• Never undo prior work. Checks lock the claims we publish; manifests tell you who depends on what; edits are additive or explicitly superseding with a compatibility window. A change that would break a live client stops and becomes a proposal, not a merge.

• Be straight with the client. Say what we cannot do and when a date is at risk early, in writing, with an alternative attached.

Who You Are

• 6+ years of software engineering experience, including time delivering directly for external customers or partners, in their environments, not only internal roadmap work.

• End-to-end ownership of at least one complex, customer-facing technical delivery: you can name the deployment you ran, what went wrong, and what you did about it after launch.

• Strong integration engineering depth: API design and consumption, auth, webhooks versus polling, idempotency, rate limits, pagination, schema drift, reconciliation, and comfort across the stack from APIs to data to cloud infrastructure.

• You build with AI agents every day and can show how you verify what they produce and when you stop trusting them.

• Experience handling sensitive data with a security-first mindset, treating compliance constraints as design inputs rather than follow-ups.

• Clear communication with technical and non-technical audiences, including delivering unwelcome news to a customer early and keeping the relationship.

• Judgment about scope: you can point to things you descoped or resequenced, and explain why.

• Preferred

• Experience in healthcare or another regulated domain where a mistake has consequences beyond a rollback.

• Practical experience shipping LLM-based or agentic systems to production, including how you measured quality.

• Experience contributing to developer platforms: SDKs, CLIs, API conventions, documentation that is tested rather than written.

• Familiarity with EHR, scheduling, pharmacy or payments integrations; FHIR is a plus.

• Bachelor's degree in Computer Science, Engineering or a related technical field, or equivalent practical experience.

How You Work

OpenLoop's values are prescriptive, and this role tests all of them:

Disciplined Intensity: effective under real deadline pressure, and you build systems instead of becoming the only person who can fix things.

Do No Harm: patient safety and data integrity come first, and you know when to slow down to do it right.

Step In, Stay In: your ownership travels to the outcome, not to the handoff.

Purposeful Speed: you ship fast without leaving behind something only you can maintain.

Clarity Over Comfort: you say the thing, explain the why, and invite disagreement.

Core collaboration hours are CST 8am to 5pm, with client-facing work occasionally requiring flexibility outside them. Remote within the United States; periodic travel to clients and to team working sessions.

Our Benefits

In addition, for salaried positions you would also be eligible for:

• Medical, Dental, and Vision plans

• Flexible Spending/Health Savings Accounts

• Flexible PTO

• 401(k) + Company Match

• Life Insurance, Pet insurance, and more

Our Company

We have a relatively flat organizational structure here at OpenLoop. Everyone is encouraged to bring ideas to the table and make things happen. This fits in well with our core values of Autonomy, Competence and Belonging, as we want everyone to feel empowered and supported to do their best work.

Sound like a good fit? We’d love to meet you.