What is a Forward Deployed Engineer (FDE)?
- Authors
- Name
- Amit Shekhar
- Published on
A Forward Deployed Engineer (FDE) is an engineer who sits with a customer, builds the AI software the customer needs, delivers it inside the customer's own systems, and stays until it works in production.
In this blog, we will learn about the Forward Deployed Engineer role. We will also see where this role came from, what a Forward Deployed Engineer owns from the first meeting to the working system, what a day in the role looks like, how it differs from a Solutions Engineer, and who this role suits.
We will cover the following:
- What is a Forward Deployed Engineer?
- Where did the role come from?
- What does a Forward Deployed Engineer own?
- A day in the role
- Forward Deployed Engineer vs Solutions Engineer
- Who suits this role?
I am Amit Shekhar, Founder @ Outcome School, I have taught and mentored many developers, and their efforts landed them high-paying tech jobs, helped many tech companies in solving their unique problems, and created many open-source libraries being used by top companies. I am passionate about sharing knowledge through open-source, blogs, and videos.
I teach AI and Machine Learning at Outcome School.
Let's get started.
What is a Forward Deployed Engineer?
A Forward Deployed Engineer is an engineer who is embedded with a customer and who scopes, builds, and ships production AI software inside the customer's environment, from the integrations to the AI agent itself, and stays until it works.
In simple words, the company sends its engineer to the customer, instead of sending the customer's problem to the engineer.
Let's understand the term Forward Deployed.
In most software companies, engineers sit at the home office and build one product for everyone. The customers are far away. Someone from sales or support talks to them, writes a ticket, and the engineer reads the ticket.
A Forward Deployed Engineer is deployed forward, which means the engineer moves out of the home office and sits with the customer. The engineer sees the customer's data, the customer's systems, and the customer's problems directly. There is no ticket in between.
So, the one-line summary of the role is: half engineer, half consultant, full owner.
- Half engineer, because the FDE builds software that runs in production.
- Half consultant, because the FDE sits with the customer, understands the business, and decides what to build.
- Full owner, because the FDE is responsible for the result, not just for the code.
Where did the role come from?
Palantir created the Forward Deployed Engineer role. Palantir sells software to large organizations such as governments and big companies. Every customer has different data, different systems, and different rules, and the product could not fit into each customer by itself. So, Palantir started sending engineers to sit with the customer and make the product work there. They called these engineers Forward Deployed Engineers.
Now, the same role is common at AI companies. The reason is the same. An AI model or an AI agent looks powerful in a demo, but a customer does not buy a demo. A customer buys a working system that reads their documents, connects to their tools, follows their rules, and gives correct answers in their environment. The work of fitting the AI into the customer's systems is large, and someone must own it. Here comes the Forward Deployed Engineer into the picture.
A quick note for you
No matter which tech domain you work in, get familiar with these topics:
- LLM
- RAG
- MCP
- Agent
- Fine-tuning
- Quantization
We put it all together in one video:
AI Engineering Explained: LLM, RAG, MCP, Agent, Fine-Tuning, and Quantization
No need to stop reading - bookmark it and watch later when you get time. Future you will thank you.
Now, let's get back to the topic.
What does a Forward Deployed Engineer own?
A Forward Deployed Engineer owns the complete path from "the customer has a problem" to "the customer has a working AI system". Let's see each part of that path.
Scoping with the customer
The FDE starts by sitting with the customer and finding the real problem. The customer says, "We want AI for our support team." That is a wish, not a problem that can be built. The FDE asks questions until it becomes something specific, like "The support team spends hours finding the right answer in old tickets, and we want an agent that finds it in seconds."
The FDE also decides what is in and what is out for the first version. The FDE keeps the first version small so that it ships quickly and the customer can give feedback on a working system.
Integrations and connectors
Every customer has their own systems, such as a ticketing tool, a document store, a database, and an internal API. The AI agent is useless until it can read from and write to these systems. The FDE builds the connectors that link the agent to the customer's data.
This is where a coding agent such as Claude Code does most of the typing. The FDE describes the connector clearly, with the source system, the fields needed, the authentication, and the error cases. Then, the FDE directs the coding agent to write it, reviews the code, and tests it against real customer data.
The agent or AI feature itself
Once the data flows, the FDE builds the AI part. This includes the prompts, the retrieval of the right documents, the tools the agent can call, the guardrails that stop it from doing something wrong, and the evaluation that proves it gives correct answers. Again, the FDE builds this with a coding agent and spends most of the time on judgment: is the answer correct, is it safe, and does it fit how the customer works.
Shipping inside the customer's environment
The software does not run on the FDE's laptop. It runs inside the customer's cloud, behind the customer's security rules, with the customer's access controls. The FDE makes it run there, which often means dealing with permissions, networks, and deployment steps that are different for every customer.
Staying until it works
This is the part that makes the role different from most engineering roles. The FDE does not hand over the code and leave. The FDE watches the system in production, collects the cases where it fails, fixes them, and keeps going until the customer's team uses it every day and trusts it.
Want to become a Forward Deployed Engineer?
These are the skills this role needs, and we teach them in our AI and Machine Learning Program at Outcome School:
- RAG
- AI Agent
- Model Context Protocol (MCP)
- Evaluation of LLMs and Agents
- Model Deployment and Serving
- AI Security
We take you from the fundamentals to building real AI systems, step by step.
A day in the role
The best way to learn this is by taking an example.
Let's say an FDE named Priya is embedded with a hospital chain. The hospital wants an AI agent that helps its billing team answer questions about insurance claims. The claims live in an old billing system, the rules live in PDF documents, and the team works inside a ticketing tool.
Priya starts the morning in a meeting with the billing team lead. She shows the first version of the agent and asks the team to try five real questions. Three answers are correct. Two are wrong, because the agent could not find the latest rule document. Priya notes both failures.
Back at her desk, she opens the coding agent and describes the problem: the retrieval step must prefer the newest version of a rule document when two versions exist. The coding agent proposes a change to the retrieval code and writes a test for it. Priya reads the change, checks that it matches how the hospital versions its documents, runs the test, and then runs the two failed questions again. Both are correct now.
After lunch, the hospital's IT team tells her that the agent must not send any claim data outside the hospital's private network. Priya directs the coding agent to send the model call to a model server that runs inside the hospital's own cloud, reviews the configuration, and verifies with the IT team that no traffic leaves the network.
In the evening, she writes a note to the billing team lead: what was fixed, what is next, and what she needs from them, which is twenty more real questions to test against. Then she updates the plan for the week.
Here, we can notice that the coding agent did the building. Priya did the directing, the verifying, and the deciding. This is how most days in this role go.
Stay updated: Subscribe to our newsletter to get our latest AI and Machine Learning blogs straight to your inbox.
Forward Deployed Engineer vs Solutions Engineer
Now, let's see how this role differs from the nearest role, the Solutions Engineer. A Solutions Engineer works before the sale. The Solutions Engineer explains the product, builds demos, answers technical questions, and helps the sales team close the deal. Once the customer signs, the Solutions Engineer moves to the next possible customer. A Forward Deployed Engineer works after the sale. The FDE builds the production system inside the customer's environment and owns it until it works. The Solutions Engineer shows that it can work, and the Forward Deployed Engineer makes it work.
Who suits this role?
The Forward Deployed Engineer role suits a person who:
- Likes building systems with a coding agent and is good at reviewing and verifying what the agent produces.
- Enjoys talking to customers and can turn a vague wish into a clear, small, buildable scope.
- Is comfortable with messy systems, old databases, strict permissions, and data that is never clean.
- Takes ownership of the result and does not feel done until the customer's team uses the system every day.
- Is fine with travel or long calls and with being the only engineer in the room.
The role does not suit a person who prefers to work on one deep technical problem for months, who dislikes meetings, or who wants a fixed product with a fixed plan. An FDE's plan changes every week because the customer's needs change every week.
Now we must have understood what a Forward Deployed Engineer is, where the role came from, what an FDE owns, what a day in the role looks like, how it differs from a Solutions Engineer, and who this role suits.
Frequently Asked Questions
Does a Forward Deployed Engineer write all the code by hand?
No. A coding agent such as Claude Code does most of the typing. The Forward Deployed Engineer describes what to build, directs the coding agent to write it, reviews the code, and tests it against real customer data. Most of the time goes into judgment: is the answer correct, is it safe, and does it fit how the customer works.
Does a Forward Deployed Engineer leave after delivering the code?
No. A Forward Deployed Engineer does not hand over the code and leave. The engineer watches the system in production, collects the cases where it fails, and fixes them. The work goes on until the customer's team uses the system every day and trusts it.
Why does a Forward Deployed Engineer keep the first version small?
A Forward Deployed Engineer keeps the first version small so that it ships quickly and the customer can give feedback on a working system. The engineer first turns a vague wish from the customer into a specific problem, and then decides what is in and what is out for the first version.
Where does the software built by a Forward Deployed Engineer run?
It runs inside the customer's environment, not on the engineer's laptop. The software runs in the customer's cloud, behind the customer's security rules, with the customer's access controls. Making it run there often means dealing with permissions, networks, and deployment steps that are different for every customer.
That's it for now.
Thanks
Amit Shekhar
Founder @ Outcome School
You can connect with me on:
Follow Outcome School on:
