The conversation in AI has shifted. In 2023, everyone was asking "Can we use AI?" In 2025, the question became "Why isn't our AI working?" In 2026, the question is simpler: "Who is going to build this?"
The answer, increasingly, is a Forward Deployed Engineer.
What Is a Forward Deployed Engineer?
The term comes from Palantir, which pioneered the model: instead of building a product and hoping customers figure out how to use it, you send an engineer to the customer. They work inside the client organization, own the technical integration end-to-end, and don't leave until the system is in production.
The key word is embedded. Not a consultant who writes a deck and flies home. Not a solutions engineer who does a demo and hands you a doc. An engineer who sits in your Slack, attends your standups, and writes code in your repo.
OpenAI saw the same pattern and launched the OpenAI Deployment Company in May 2026 — a standalone entity whose entire job is to embed engineers at Fortune 500 companies. Anthropic partnered with Deloitte in a $1.5 billion joint venture structured around the same model. The signal is clear.
Why the Model Works
1. The deployment gap is an engineering problem
Most AI pilots fail not because the model isn't good enough, but because nobody knows how to connect the model to the systems that need it. Data is in the wrong format. APIs are undocumented. Security reviews take months. Edge cases nobody anticipated start showing up on day two.
These are engineering problems. They require engineers — not strategists, not project managers, not another workshop.
An FDE brings the engineering capacity to solve them. They don't wait for a ticket. They find the problem, fix the problem, and ship.
2. Context is worth more than capability
The dirty secret of enterprise AI is that the model is the easy part. The hard part is understanding the customer's data, their workflows, their constraints, and their definition of "good enough."
A generic offshore team, no matter how technically capable, starts every engagement with a deficit of context. An FDE, embedded in the organization, builds that context daily. They know why the data is messy. They know which stakeholder will kill the project if the latency is above 2 seconds. They know the system that generates the training data has a bug that's been there for 18 months.
Context like that is worth more than raw engineering hours.
3. Accountability collapses distance
When something breaks in production at 2am, the question is always: who owns this? In a traditional services engagement, the answer is murky — the client team owns it but doesn't understand it; the vendor team understands it but doesn't own it.
The FDE model collapses that distance. The FDE is on your on-call rotation. They built the system. They know the runbooks. The accountability is clear.
What a Good FDE Function Looks Like
Not all FDE engagements are created equal. Here's what separates the ones that ship from the ones that stall.
Senior engineers only. FDE work requires judgment, not just execution. You're often making architectural decisions under uncertainty, negotiating with skeptical stakeholders, and working without complete information. Junior engineers can't do this independently.
Fixed scope, not time-and-materials. Open-ended engagements drift. The best FDE engagements start with a scoping exercise that produces a concrete definition of done: what system, what performance, what deadline. Scope can change — but changes should be explicit, not drift.
Eval-first. Every system an FDE builds should ship with an automated evaluation suite. If you can't measure whether the system is working, you can't trust it in production, and you can't detect when it stops working. This is non-negotiable.
Knowledge transfer as a deliverable. The goal of an FDE engagement is to make the FDE unnecessary. Runbooks, architecture docs, training sessions, annotated code — all of it should be included in the engagement scope. FDEs who create dependency aren't doing their job.
The Market in 2026
FDE job postings grew 800% between January and September 2025. Mid-level FDEs are clearing $300K–$450K total comp. OpenAI has 30+ open FDE roles. Palantir has 50+. There are 224 open FDE roles across 39 AI companies as of this writing.
The supply of qualified FDEs is nowhere near the demand. Which is why the agency model exists: you get access to an FDE without competing with OpenAI's recruiting machine or paying for a full-time hire before you know if the model fits.
For most companies, an FDE engagement is the fastest path from "we have AI ambitions" to "we have an AI system in production."
If you're trying to ship AI and struggling to find the engineering capacity to do it, talk to us. We scope every engagement in 2 days.