The Embedded
We work from inside
The first two weeks are spent measuring how work really moves, not how it is documented. That is how we can promise an outcome.
The plain-language guide
What is a forward-deployed engineer?
A forward-deployed engineer (FDE) is a software engineer who works inside your organization, in your systems and your workflows, to build and ship working software rather than hand you a recommendation. The role was named at Palantir and is now how OpenAI, Anthropic, and most serious AI companies get their technology working inside customers. The defining trait is accountability for a result running in production.
~800%
rise in FDE job postings, Jan to Sep 2025
Paraform, 2026
$238K
average full-time FDE compensation
Published 2026 comp data
148
companies actively hiring FDEs
FDE Pulse, April 2026
20h
a month back, minimum, on a Passel engagement
Our written commitment
Market figures are from the sources listed at the end of this page. The 20-hour figure is The Passel Group's contractual commitment.
What an FDE does
The engineer comes to the work, not the other way round.
Most software fails at the last mile: it works in the demo, then meets a real operation with its own systems, habits, and exceptions. A forward-deployed engineer owns that last mile. They learn how the work actually moves, decide what to build, build it inside the tools people already use, and stay until it is running and measured.
In practice an FDE engagement has four parts: embed (understand the real process, not the documented one), map (identify what repeats and what it costs), build (integrations, automations, and AI-assisted steps inside existing systems), and prove (measure the result against the baseline and hand it over).
The term "forward-deployed" is borrowed from the military: units deployed forward operate at the front line rather than at headquarters. The engineering version means the same thing. The engineer works where the problem is.
FDE vs consultant vs solutions engineer vs agency
Four ways to get outside help. Only one ships code in your systems.
They are often confused with each other. The differences are in what you receive, how it is priced, and who is accountable when it doesn't work.
| You get | Forward-deployed engineer | Management consultant | Solutions engineer | Dev agency |
|---|---|---|---|---|
| Deliverable | A working system, in production, in your tools | A report, roadmap, or deck | A demo or proof of concept for a vendor's product | A new application, usually separate from your existing tools |
| Where they work | Inside your operation and your systems | Outside, interviewing your team | Inside the vendor, pre-sale | Outside, against a specification |
| Priced on | An outcome, written down before the build | Time or a project fee, regardless of whether it ships | Free, funded by the software sale | Hours or a fixed scope |
| Technology stance | Neutral: your outcome chooses the tools | Neutral, but does not build | Tied to one vendor's product | Usually a preferred stack |
| Accountable for it working? | Yes, until it is measured and handed over | No, accountability ends at the recommendation | No, accountability ends at the sale | To the spec, not the business result |
| Best when | The problem is known and you need it built and running | You need strategy before committing budget | You are evaluating a specific product | You want a new product or app built from scratch |
When to hire one
Signs your operation needs a forward-deployed engineer.
Not every business needs one. These are the patterns where an FDE pays for itself quickly.
01
Your people are the integration layer
Staff spend part of every day copying information between systems that don't talk: a practice management system and payer portals, a case management tool and a document system, a ledger and a tax suite.
02
You've bought software that didn't remove the work
Each tool solved its own step and stopped at its own edge. The manual work moved rather than disappeared.
03
You want a result, not a roadmap
You already know the problem. A strategy document would tell you what you know. What you need is working automation and someone accountable for it.
04
Your data is regulated
Healthcare, legal, and financial records need engineering that treats privacy and compliance as design constraints from day one, not a sign-off at the end.
What it costs
Hire one, or engage one.
Hiring a full-time FDE is expensive and competitive. Demand rose roughly 800% through 2025, and published 2026 compensation data puts the average around $238,000 a year, before the overhead of recruiting, managing, and keeping an engineer busy once the first projects are done. For most businesses with fewer than a few hundred staff, that does not add up.
Engaging one is the practical route. The Passel Group runs a flat-fee workflow audit: two weeks with the Passel Observer, a lightweight workflow-telemetry agent, on every workstation, then a Gap Report of every repeated task and what it costs. The build is scoped per workflow from that report, with the outcome written down. If we haven't found and automated at least 20 hours a month, we keep working at no additional cost.
How The Passel Group does it
Forward-deployed engineers for medical billing, legal, clinical, and accounting operations.
We specialise in operations where the busywork is measurable and the data can't be gotten wrong. For each industry we've mapped the workflows we automate, the tools we plug into, and the hours they typically give back.
Medical billing companies
Eligibility, claim status, denials and appeals, ERA posting, AR, client reporting.
Law firms
Intake, conflict checks, engagement letters, drafting from precedent, pre-bill review.
Clinics & practices
Scheduling, intake, prior authorizations, fax routing, inbox triage, charge capture.
Accounting & CPA firms
Document chasing, extraction, bank feed rules, month-end close, tax prep support.
Verified
HIPAA program, continuously verified
Independently verified through Live Compliance. A Business Associate Agreement before any PHI moves. The same discipline for legal and financial data.
Guaranteed
Written outcome, or we keep working
You reach the outcome we agreed to in writing, or we keep working at no additional cost until you do. Same team, same standard, no new invoice.
Questions
Forward-deployed engineers, answered plainly.
What is a forward-deployed engineer? +
A software engineer who works inside a client's organization, in its own systems and workflows, to build and ship working software. The term comes from Palantir and is now used by OpenAI, Anthropic, and many AI companies. The defining trait is accountability for a running result, not a recommendation.
What does a forward-deployed engineer actually do? +
Learns how work actually moves inside the operation, identifies where software can remove repeated manual work, builds integrations, automations, and AI-assisted steps inside the tools the client already uses, and stays until the result is running in production and measured.
How is an FDE different from a consultant? +
A consultant's deliverable is a recommendation: a report, a roadmap, a deck. An FDE's deliverable is a working system in production. Consultants are typically priced on time; FDE engagements are priced against an outcome. If you need advice before committing, hire a consultant. If the problem is known and you need it built, hire an FDE.
How is an FDE different from a solutions engineer? +
Solutions engineers work pre-sale for a software vendor: demos, proofs of concept, technical answers during the sales cycle. Forward-deployed engineers work post-sale or independently, writing production code inside the customer's environment to make the outcome real.
How much does a forward-deployed engineer cost? +
Full-time, published 2026 data puts average compensation around $238,000 a year, and most mid-sized businesses cannot keep one busy. An engagement is usually the better model: The Passel Group charges one flat fee for the two-week audit, then scopes the build per workflow with a written commitment of at least 20 hours a month saved. We give the fee on the first call.
When should a business hire one? +
When staff spend a measurable share of the day moving information between systems that don't talk to each other, when software purchases haven't removed the manual work, and when you want a working result rather than a strategy document.
Do forward-deployed engineers work on-site? +
"Deployed" refers to working inside your systems and workflows, not necessarily your building. Our engineers observe the work through the Passel Observer and build inside your tools; time on-site is agreed per engagement.
Is an FDE the same as an AI implementation partner? +
Close, with one difference. An implementation partner usually implements a specific vendor's product. A forward-deployed engineer is technology-neutral: your outcome chooses the tools, which may be automation, integration, or AI, and often all three.
Sources Wikipedia: Forward Deployed Engineer · Paraform: FDE vs solutions engineer vs customer engineer (2026) · FDE Pulse: companies hiring FDEs · TSIA: What is forward deployed engineering?
Next step
Find out what your team could stop doing by hand.
One call, then two weeks with the Observer on every desk. We don't stop until at least 20 hours a month are back.
info@thepasselgroup.com