What a Forward Deployed Engineer Does
The role, how it differs from nearby jobs, and the loop every customer project follows.
A forward deployed engineer works next to one customer and builds an AI solution for their real problem. They also stay until it runs and the result is real. The work follows a loop: find the problem, agree success, build a first version, connect it, roll it out and learn.
- FDE
- An engineer who builds and runs a solution inside one customer's world.
- Sponsor
- The person who pays for the project and wants the result.
- Loop
- The repeating cycle of discover, scope, prototype, integrate, roll out and learn.
A forward deployed engineer, or FDE, works next to a customer and builds the AI solution that fits their real problem. The job started at data companies such as Palantir. Today many AI companies and large firms hire for it. This lesson explains what the job is, how it differs from nearby jobs, and how a typical project runs.
The job in one sentence
An FDE takes a messy business problem and turns it into a working solution inside the customer's world. They write code. They also talk to the people who have the problem. They stay until the solution runs and the customer gets a result.
Think of a hospital that wants AI to sort incoming referral letters. The FDE sits with the staff who read those letters. They learn how the work really happens. They build a first version on real letters. They connect it to the hospital's systems. Then they train the staff and check that it saves time.
How it differs from nearby jobs
- A software engineer builds a product for many customers. An FDE builds for one customer at a time, then shares what they learn.
- A consultant gives advice and a plan. An FDE also builds and runs the thing.
- A solutions engineer helps before the sale with demos and answers. An FDE works after the sale until the result is real.
- A support engineer fixes problems in a product. An FDE shapes a new solution from a blank page.
These jobs overlap. Titles change from company to company. So read the job description, not just the title.
The loop an FDE runs
Most projects follow the same loop. Each turn of the loop is short, often a week. The customer sees something real each time.
- Discover: find the real problem and who feels it.
- Scope: agree on what success looks like, in numbers.
- Prototype: build a first version on the customer's own data.
- Integrate: connect it to their systems with the least access it needs.
- Roll out: train people, watch it run, and hand it over.
- Learn: tell your own team what you found, so the product improves.
Skills you need
An FDE needs three kinds of skill. First, technical depth: APIs, data, prompts, search and agents. Second, people skill: listening, explaining, and saying no politely. Third, business sense: knowing which number the customer's boss cares about.
You do not need to be great at all three on day one. Most people start strong in one and grow the others on the job.
What good looks like
A good FDE makes the customer more capable. After the project, the customer can run the solution without you. They trust you and ask for more. Your own team also learns from the project, because you wrote down what worked.
WEEK ONE CHECKLIST [ ] Meet the sponsor: who pays, and what result do they want? [ ] Meet the users: who does this work today, and how? [ ] Watch the work once, in person or on a call [ ] Ask for 20 real examples (with permission and privacy rules) [ ] Write the problem in two sentences and read it back to them [ ] List the systems, owners and rules you will need to touch [ ] Agree the next meeting and what you will show
- ✓An FDE builds and runs an AI solution inside one customer's world, and stays until the result is real.
- ✓The work runs as a loop: discover, scope, prototype, integrate, roll out and learn.
- ✓Technical depth, people skill and business sense all matter. Start from your strongest and grow the rest.
- ✓Success means the customer can run it without you, and your own team learns from the project.
Describe a project you could run
- Pick a real team you know, such as a support desk or a sales team. Write the problem in two sentences.
- Name the sponsor, the users and one system the solution would touch.
- Write one number that would show success, such as hours saved a week.
- List the first three questions you would ask in week one.
Q1How is an FDE different from a consultant?show answer
A consultant mostly advises and plans. An FDE also builds the solution, connects it to the customer's systems and stays until it runs.
Q2Name the steps in the FDE loop.show answer
Discover, scope, prototype, integrate, roll out and learn. Each turn is short, and the customer sees something real each time.
Q3What is the most common FDE mistake?show answer
Building something clever that nobody asked for. Always start from the customer's real problem and a success number.