Back to jobs

Forward Deployed Engineer

United States - Remote · Toronto, Canada · Des Moines, Iowa, United States

Live, first seen by us 47 days ago
Pay
Pay not listed
Work setting
Remote — work setting source
Location type: Remote
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Product & Tech › Engineering - Product & Services — team source
Department: Product & Tech › Engineering - Product & Services
From the employer’s posting

What you’ll work on

Full posting

Forward Deployed Engineering is how we build that platform with real clients instead of guessing.

You will write production code in two places, the client's system and ours.

  • You will write production code in two places, the client's system and ours.

  • Build for clients, in their codebase, against our API.

  • Own the outcome through go-live and the weeks after it.

From the employer’s posting
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 OpenLoop'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.
You will write production code in two places, the client's system and ours. You will take an ask that is vague or over-promised and turn it into a scope you can defend. You will tell a client, and our own sales team, when something should not be committed to. And you will leave every deployment better instrumented than you found it, so the next client needs less of us than the last one did.
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 OpenLoop'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. You will write production code in two places, the client's system and ours. You will take an ask that is vague or over-promised and turn it into a scope you can defend. You will tell a client, and our own sales team, when something should not be committed to. And you will leave every deployment better instrumented than you found it, so the next client needs less of us than the last one did. We are hiring for this role at the Senior, Staff and Senior Staff levels. Apply once; we will calibrate level during the process based on the scope you have carried, not on years alone. The section below describes what changes as scope grows.
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, for clients and for us. Ship the 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 such as intake, routing, support and refill journeys, with human review by design, evaluations before launch and monitoring after.

Before you apply

Sponsorship
Visa sponsorship not confirmed — sponsorship source
Will you now or in the future require visa sponsorship? This includes initiating, continuing or transferring your visa to OpenLoop, now or at any time in the future.
From the employer’s application form

What you’ll bring

All qualifications

Core experience

  • 5 to 15+ years of software engineering experience, including significant time delivering directly for external customers or partners, in their environments, not only internal roadmap work.
  • Experience in healthcare or another regulated domain where a mistake has consequences beyond a rollback.
  • Experience handling sensitive data with a security-first mindset, treating compliance constraints as design inputs rather than follow-ups.
  • Practical experience shipping LLM-based or agentic systems to production, including how you measured quality and what you did when the model was confidently wrong.
  • Excellent communication with technical and non-technical audiences, including delivering unwelcome news to a customer early and keeping the relationship.
  • Experience building developer platforms: SDKs, CLIs, API conventions, documentation that is tested rather than written.

Preferred experience

  • Familiarity with EHR, scheduling, pharmacy or payments integrations; FHIR is a plus.
Qualification wording
5 to 15+ years of software engineering experience, including significant time delivering directly for external customers or partners, in their environments, not only internal roadmap work. We are filling roles across this range; depth of ownership matters more to us than the number.
Experience in healthcare or another regulated domain where a mistake has consequences beyond a rollback.
Experience handling sensitive data with a security-first mindset, treating compliance constraints as design inputs rather than follow-ups.
Practical experience shipping LLM-based or agentic systems to production, including how you measured quality and what you did when the model was confidently wrong.
Excellent communication with technical and non-technical audiences, including delivering unwelcome news to a customer early and keeping the relationship.
Experience building 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.
Education & alternatives
- Experience working alongside sales or solutions teams in pre-sales technical conversations without becoming a blocker. - Bachelor's degree in Computer Science, Engineering or a related technical field, or equivalent practical experience. How You Work

Benefits in the posting

Full benefits wording
  • 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

From the employer’s posting.

About OpenLoop Health

Jon Lensing, and COO, Christian Williams, with the vision to bring care anywhere.

In the employer’s words · Read in context · Company website ↗

Apply at OpenLoop Health

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 5, 202647 days ago
Recorded sightings
55
Last seen by us
Nov 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 47

Up longer than most. Similar jobs usually come down between day 3 and day 42.

At OpenLoop Health, jobs usually come down by about day 42.

From 633 similar postings that came down, and 5 of OpenLoop Health’s. Coming down is not always a hire.

OpenLoop Health is hiring

5 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring has slowed
  • Takes jobs down at a usual pace
Hiring record

See how this role fits your experience

Add your resume to compare the role’s scope, tools and requirements with your experience.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

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

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

You will write production code in two places, the client's system and ours. You will take an ask that is vague or over-promised and turn it into a scope you can defend. You will tell a client, and our own sales team, when something should not be committed to. And you will leave every deployment better instrumented than you found it, so the next client needs less of us than the last one did.

We are hiring for this role at the Senior, Staff and Senior Staff levels. Apply once; we will calibrate level during the process based on the scope you have carried, not on years alone. The section below describes what changes as scope grows.

 

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, for clients and for us. Ship the 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 such as intake, routing, support and refill journeys, with human review by design, evaluations before launch and monitoring after.

  • Run deployments on the agent roster, and make it better. Use and extend 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 accountable for knowing when the agent is wrong.

  • Turn one client's need into every client's capability. Contribute additive recipes and checks to the shared cookbook, keep client manifests current, and bring the evidence that moves a recurring workaround into the platform roadmap instead of into another workaround. The measure is how much less of us the next client needs.

  • Turn ambiguity into a plan. Take a client ask that is vague, over-promised or self-contradictory and produce a phased, defensible scope, 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.

  • Hold the line, internally and externally. Be the credible technical voice with client engineering and with our own go-to-market team: what we cannot do, what we should not do, and what will not fit the timeline are three different answers, and all three are better delivered early.

  • Raise the bar around you. Share what a deployment taught you, review other people's integration designs, and help write the playbook for a team that is being built now.

Who You Are

  • 5 to 15+ years of software engineering experience, including significant time delivering directly for external customers or partners, in their environments, not only internal roadmap work. We are filling roles across this range; depth of ownership matters more to us than the number.

  • End-to-end ownership of complex, customer-facing technical delivery: you can name the deployments 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, when you stop trusting them, and how you evaluate an LLM-based system before it reaches a customer.

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

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

  • Demonstrated judgment about scope: you can point to things you descoped, sequenced or declined, and explain why.

  • Evidence of leverage beyond your own delivery: SDKs, tooling, checks, reference implementations or practices you built that made other people's work faster. The scale of that leverage is part of how we calibrate level.

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 and what you did when the model was confidently wrong.

  • Experience building 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.

  • Experience working alongside sales or solutions teams in pre-sales technical conversations without becoming a blocker.

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

Demand for Forward Deployed Engineer roles

New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.

Weekly new Forward Deployed Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 51, the most 267, and the latest week had 217.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Forward Deployed Engineer, by the work the posting describes.

Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.

Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.

An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Des Moines, Iowa, United States

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
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.