Back to jobs

Senior Engineering Manager, Forward Deployed Engineering

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

Live, first seen by us 16 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 our platform with real clients instead of guessing.

As Senior Engineering Manager, you own this team and you’re measured on two things: clients going live with a clean handoff, and a team that gets better at it every quarter.

  • Own client outcomes across the portfolio.

  • Lead pods through their architects.

  • Own the seam with platform teams.

From the employer’s posting
Forward Deployed Engineering is how we build our platform with real clients instead of guessing. An FDE embeds with a client, works in their codebase, and builds their integration against OpenLoop’s production API. Anything the platform can’t do yet is filed as a gap and built once, centrally, so every client inherits it. The real work product isn’t the integration. It’s the reusable asset that client forced into existence.
As Senior Engineering Manager, you own this team and you’re measured on two things: clients going live with a clean handoff, and a team that gets better at it every quarter. The team is already delivering and growing fast. Your job is to turn strong individuals into a function, and to scale it without lowering the bar.
What You'll Do Own client outcomes across the portfolio. Every client in build has a named owner and a go-live date. Spot a troubled deployment before the client does, and report it with the date, impact and trade-off. Allocate capacity. Assign new clients on the day they arrive, with an owner and a clear statement of what they displace. When client, migration and platform work compete, you make the call.
Allocate capacity. Assign new clients on the day they arrive, with an owner and a clear statement of what they displace. When client, migration and platform work compete, you make the call. Lead pods through their architects. Each pod has an FDE acting as technical architect. Give them clear ownership, real decision rights, and a habit of escalating early. Migrate existing clients onto the Partner API. Move them in cohorts with implementation, platform engineering and the client’s team. Respect change calendars, and measure each move by its first production patient.
Migrate existing clients onto the Partner API. Move them in cohorts with implementation, platform engineering and the client’s team. Respect change calendars, and measure each move by its first production patient. Own the seam with platform teams. Each gap names the capability it stands in for. Decide who builds it, and escalate stalled reviews with a date. Give every go-live an exit. Clients leave hypercare on a set date, documented and signed off, so the team doesn’t become the support desk.

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

  • 8+ years in software engineering, including 3+ years managing engineers: hiring, performance, leveling and promotions, and growing a team.
Qualification wording
8+ years in software engineering, including 3+ years managing engineers: hiring, performance, leveling and promotions, and growing a team.

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
Nov 5, 202616 days ago
Recorded sightings
17
Last seen by us
Nov 21, 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 16

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 our platform with real clients instead of guessing. An FDE embeds with a client, works in their codebase, and builds their integration against OpenLoop’s production API. Anything the platform can’t do yet is filed as a gap and built once, centrally, so every client inherits it. The real work product isn’t the integration. It’s the reusable asset that client forced into existence.

As Senior Engineering Manager, you own this team and you’re measured on two things: clients going live with a clean handoff, and a team that gets better at it every quarter. The team is already delivering and growing fast. Your job is to turn strong individuals into a function, and to scale it without lowering the bar.

This is a player-coach role, coaching first. You stay technical through review, not by owning a client yourself. You read integration designs, adjudicate platform gaps, and stay credible with both client engineering leaders and our platform engineers. If you want to stop reviewing code entirely, or to write code instead of managing people, this isn’t the role.

You’ll report into Engineering and work daily with platform, implementation, customer success and sales.

What You'll Do

  • Own client outcomes across the portfolio. Every client in build has a named owner and a go-live date. Spot a troubled deployment before the client does, and report it with the date, impact and trade-off.

  • Allocate capacity. Assign new clients on the day they arrive, with an owner and a clear statement of what they displace. When client, migration and platform work compete, you make the call.

  • Lead pods through their architects. Each pod has an FDE acting as technical architect. Give them clear ownership, real decision rights, and a habit of escalating early.

  • Migrate existing clients onto the Partner API. Move them in cohorts with implementation, platform engineering and the client’s team. Respect change calendars, and measure each move by its first production patient.

  • Own the seam with platform teams. Each gap names the capability it stands in for. Decide who builds it, and escalate stalled reviews with a date.

  • Give every go-live an exit. Clients leave hypercare on a set date, documented and signed off, so the team doesn’t become the support desk.

  • Hire and develop. You’re the hiring manager for FDEs and Deployment Strategists at every level. Coach toward scope, run hard conversations on time, defend leveling decisions, and run reviews with no surprises.

  • Own the agent roster. The team runs deployments on agents (readiness, conformance, seeding, docs, gap filing, client comms), and a human approves every output. You own adoption, measurement and where the human sits.

  • Protect the discipline. Never wire around the platform. Make changes additive or explicitly superseding. Anything that would break a live client becomes a proposal, not a merge, even under deadline pressure.

  • Partner with go-to-market. Be in the room before commitments are made. Distinguish “can’t,” “shouldn’t” and “won’t fit the timeline,” and turn the prioritized client list into a dated plan.

  • Write the playbook. Turn how your best engineers deploy into how the team deploys, so each new deployment needs less of you.

 

Who You Are

  • 8+ years in software engineering, including 3+ years managing engineers: hiring, performance, leveling and promotions, and growing a team.

  • You’ve led teams delivering in customers’ environments, and you can talk through deployments that went badly and what you changed.

  • You’ve run a migration or re-platforming program with customers who could say no, and you’ve allocated a team against more demand than supply.

  • You’re still technical: deep in integrations (APIs, auth, webhooks vs. polling, idempotency, schema drift, reconciliation) and able to change a design with one question.

  • You build with AI agents and have a view on human-in-the-loop design, evaluation, and handling confident errors.

  • You’re security-first with sensitive data and treat compliance as a design input.

  • You’ve told customers or sales “no” or “not in that timeline” and kept the relationship, and you can name things you descoped and why.

  • You’ve had impact beyond your own team through tooling, practices or platform changes.

Preferred

  • Healthcare or other regulated-domain experience; EHR, scheduling, pharmacy or payments integrations (FHIR a plus).

  • You’ve managed managers, led teams through organizational change, or scaled an FDE, solutions engineering or professional services function.

  • Developer platform experience (SDKs, CLIs, API conventions, tested docs).

  • Comfortable in pre-sales technical conversations.

  • BS in CS or Engineering, or equivalent experience.

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

Working pattern and location restrictions need checking in the full posting.

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.