Forward Deployed Engineer in 2026: Skills, Role and Why Always-On Agents Need FDEs
What a Forward Deployed Engineer does in 2026, the FDE skill stack, why always-on agents like Dots and Grok Bot need FDEs, and how to train your team.
Anyone can now rent an agent that works around the clock. Nobody can rent the judgement about which process to hand it, whose identity it uses, what it may do without asking, and how you would prove it works. That judgement, applied inside a customer's real constraints, is the job of a Forward Deployed Engineer.
TL;DR
A Forward Deployed Engineer (FDE) is a software engineer who works directly with a customer or business unit to take an AI system from problem to production in their environment. In 2026, always-on agents such as OpenAI Dots, Meta Muse, xAI Grok Bot and Google Gemini Spark made the model and the agent runtime easy to get. What is still hard is everything around them: which process to automate, which identity the agent uses, what it may do without asking, how to prove it works, and how people adopt it. That is FDE work, and it is why the role matters more as agents get easier to buy. Our FDE roadmap plans about 18 weeks for an experienced engineer to build the skills; that is our plan, not a guarantee.
What does a Forward Deployed Engineer do?
An FDE owns an outcome, not a ticket. A typical engagement:
Step 1: Discovery
Sit with the people who do the work today and find where AI changes the numbers
Step 2: Solution architecture
Design within data residency, identity provider, compliance, latency and budget
Step 3: Prototype fast
Show a working slice on real data within days
Step 4: Integrate
Connect to their systems, usually through MCP tool servers and their identity provider
Step 5: Evaluate
Build an evaluation from their historical cases and agree the bar for launch
Step 6: Productionise and hand over
Monitoring, runbooks, training, and a system their team can operate
The difference from a solutions engineer is that an FDE writes and ships production code. The difference from a consultant is that an FDE is accountable for it working after launch.
Forward Deployed Engineer
- Writes and ships production code in the customer's environment
- Accountable for it working after launch
Solutions engineer
- Mostly works before a sale and demonstrates the product
Consultant
- Advises and delivers recommendations
- Not usually accountable for the system working after launch
Why always-on agents make FDEs more valuable
When an agent only answered questions, deployment was mostly retrieval and prompt work. An agent that acts around the clock raises the stakes of every deployment decision:
- Identity: whose credentials does it use? (Answer: its own. See agent identity.)
- Approvals: what can it do alone, and who signs off on the rest? (See approval design.)
- Isolation: does the product separate agents from each other? xAI's documentation, for example, says all Grok Bots on one account share a VM.
- Evidence: can you prove, with logs and evals, what the agent did and that it is getting better?
- Change management: will the team trust it enough to stop doing the work by hand?
Vendors ship the runtime. FDEs decide how it meets reality.
The 2026 FDE skill stack
| Layer | Skills |
|---|---|
| Engineering | Production software, APIs, data pipelines, cloud, security basics |
| AI engineering | Structured outputs, RAG, tool calling, agent loops, MCP |
| Agent deployment (new) | Non-human identity, least privilege, approval tiers, computer use, audit logging |
| Evaluation | Outcome and trajectory evals from customer data, regression testing on model changes |
| Customer | Discovery interviews, scoping, writing for executives, running pilots, handling "no" |
The middle row is new in 2026 and is now part of our FDE roadmap as two stages: Agent Deployment & Identity and Operating & Evaluating Agents.
A day in the life, 2026 edition
Morning: review overnight logs from a specialist procurement agent in pilot, find two cases where it asked for approval it did not need, and move that action down a tier in the policy. Midday: discovery session with a claims team about a document-intake agent. Afternoon: extend the evaluation set with ten new edge cases from the claims team, then rerun it against a cheaper model the vendor just released. End of day: a one-page update to the sponsor with approval rates, accuracy and cost per task.
How to become an FDE
- If you are a software engineer: follow the AI Engineer, then Agentic AI, then FDE roadmaps, and practise in the FDE simulator.
- If you are already an AI engineer: focus on discovery, solution architecture and the agent deployment stages.
- Build a portfolio of one end-to-end deployment: problem statement, architecture, eval results and what changed for the users.
How enterprises can train their own FDEs
Hiring FDEs is slow and expensive. Training your strongest engineers works if it is structured. Our 18-week cohort plan:
| Weeks | Focus | Checkpoint |
|---|---|---|
| 1–4 | AI engineering foundations | Ship an LLM feature with RAG and a basic eval |
| 5–8 | Agents, tools and MCP | Build a tool-using agent with guardrails |
| 9–12 | Forward deployment | Run discovery and deliver a POC |
| 13–14 | Simulated engagements | Pass the FDE simulator scenarios |
| 15–18 | Capstone on a real internal use case | One use case in production with evals and an owner |
Details and operating models are on the FDE playbook page.
Weeks 1 to 4
AI engineering foundations: ship an LLM feature with RAG and a basic eval
Weeks 5 to 8
Agents, tools and MCP: build a tool-using agent with guardrails
Weeks 9 to 12
Forward deployment: run discovery and deliver a proof of concept
Weeks 13 to 14
Simulated engagements: pass the FDE simulator scenarios
Weeks 15 to 18
Capstone: one real internal use case in production with evals and an owner
Frequently asked questions
What is a Forward Deployed Engineer? A software engineer who works directly with a customer or business unit to take an AI system from problem to production in their environment, owning discovery, architecture, prototyping, integration, evaluation and handover.
What skills does a Forward Deployed Engineer need in 2026? Production software engineering, AI engineering (RAG, tool calling, agents, MCP), agent deployment skills (identity, least privilege, approval design, audit logging), evaluation, and strong customer communication.
Why do always-on AI agents make FDE work more important? Because the agent runtime is now a product, while deciding what an agent may do, under which identity, with what approvals and how to prove it works still has to be done for each organisation. That is FDE work.
How long does it take to become a Forward Deployed Engineer? Our FDE roadmap plans about 18 weeks of focused study and practice for an experienced software engineer, and longer if you are new to production software. It is a plan, not a guarantee of any outcome.
What does an FDE do in a typical week? Reviews logs from agents in pilot and adjusts approval tiers, runs discovery sessions with the people who do the work, extends the evaluation set with real edge cases, and reports approval rates, accuracy and cost per task to the sponsor.
How do I build an FDE portfolio? Document one end-to-end deployment: the problem statement, the architecture, the evaluation results and what changed for the users.
Can a company train its own FDEs? Yes, if the programme is structured. The 18-week cohort plan above moves strong engineers from foundations through agents, forward deployment and simulated engagements to a capstone on a real internal use case.
Is FDE the same as solutions engineer? No. Solutions engineers mostly work before a sale and demonstrate the product. FDEs build and ship production systems in the customer's environment and are accountable for them after launch.
Related
Sources
- OpenAI launches Dots (TechCrunch)
- Introducing Muse (Meta)
- Grok Bot: xAI's AI teammates get their own computer (Digital Applied)
- The Personal Agent Landscape, September 2026
Forward deployed engineering
Your next step
Reading is the start. Turn it into skill: read the chapter, practise on something real, check the numbers, then follow a path.
More on Always-on agents
- Build an AI Business Case with a Skill That Won't Invent NumbersA free AI skill that builds a funding-ready business case with options, an assumptions register and best, base and worst cases, and refuses to make up numbers.
- Practise Forward Deployed Engineer Interviews with an AI Coach SkillA free AI skill that runs timed FDE drills, client role-plays and deployment-design rounds and scores you against a rubric. Includes a real coaching session.
- How to Build the Business Case for an AI ProjectHow to build a credible AI business case: costs, value, adoption ramp and best, base and worst cases, with a clearly illustrative worked example.
Discuss this article
Got a question, a counter-example or a correction? Bring it to the community.
Prefer a feed reader? Follow by RSS.