What is a forward deployed engineer?
The role explained
What is a forward deployed engineer? It is a software engineer who works inside a customer's organisation to get a product into real use. They build what that one customer needs, such as integrations, data pipelines and AI applications.
- No deposit to get started
- Every requirement read by us
- A best-fit shortlist, not a pile of CVs
- One agreement, one invoice
What is a forward deployed engineer, in short
A forward deployed engineer, or FDE, works directly inside a customer's organisation. Instead of building one feature for many customers, they build what one customer needs to succeed.
Wikipedia describes the role as "a customer-facing software engineer who works for a company that makes a product and helps implement that product within a client company". The key words are software engineer. This is a building role. It is not sales, and it is not advice.
You will also see the title forward deployed software engineer. Palantir uses that title, and OpenAI uses both titles for different posts. The work is the same.
If you need one, you can hire one through us. You tell us what you need, and we send people who fit.
What "forward deployed" means
The phrase comes from military language. A forward deployed unit is based near the action instead of at headquarters. A forward deployed engineer works out with the customer, not back at the office.
Where the role came from
Palantir made the forward deployed engineer a standard job. The Pragmatic Engineer, which interviewed Palantir engineers, reports that the role was known inside Palantir as "Delta". Accounts differ on the exact year, but not on who started it.
Palantir explains the split this way. A product engineer, a "Dev", builds one capability for many customers. A "Delta" makes many capabilities work for one customer.
It was not a side team. The Pragmatic Engineer reports that for some years Palantir had more forward deployed engineers than other software engineers. Palantir's own job post says it pioneered the role by embedding engineers directly with its customers.
Tell us the role and the hours. We send you a shortlist of people who fit.
- No deposit to get started
- Every requirement read by us
- A best-fit shortlist, not a pile of CVs
- One agreement, one invoice
What a forward deployed engineer does, step by step
The shape of the work is much the same at every employer.
- 01
Discovery
Sit with the customer's team. Learn the workflow, the data, the systems and who decides what. OpenAI's post puts discovery first in the list of things its forward deployed engineers own.
- 02
Scoping
Turn a vague goal into a plan that can ship. Agree what success looks like.
- 03
Build
Write production code inside the customer's environment. At Anthropic that means building MCP servers, sub-agents and agent skills on Claude.
- 04
Roll out
Get real users on it, fix what breaks and check whether it helps. OpenAI says it measures success through production adoption and workflow impact.
- 05
Feed back
Turn what worked into reusable tools, and tell the product team what customers need. This step makes the role valuable to the employer, not only to the customer.
A typical week
A Palantir engineer quoted by The Pragmatic Engineer said most weeks include time at the customer's site. The rest goes on meetings, technical work and reviewing code back at the office.
Travel is part of the job. Palantir, OpenAI and Anthropic each say so in their job posts.
How the role differs at Palantir, OpenAI and Anthropic
Palantir is the original. It splits the work into separate tracks: forward deployed software engineers, who build, and deployment strategists, who work closely with customers. It also hires straight from university.
OpenAI's team is much newer. The Pragmatic Engineer reports that it was pitched and is led by Colin Jarvis, who joined OpenAI as a solutions architect. OpenAI posts forward deployed engineer roles in many cities, plus roles for healthcare, legal, financial services and government work.
Anthropic's forward deployed engineers sit in its Applied AI team and embed directly with its most strategic customers. Its London post describes the hire as one of its founding forward deployed engineers, which shows how young the function is.
Tell us the role and the hours. We send you a shortlist of people who fit.
- No deposit to get started
- Every requirement read by us
- A best-fit shortlist, not a pile of CVs
- One agreement, one invoice
Forward deployed engineer vs similar roles
These roles overlap, which is why job titles confuse people. The difference is who you serve and whether you ship code.
| Question | Forward deployed engineer | Software engineer | Solutions architect | Consultant |
|---|---|---|---|---|
| Main output | Working software in one customer's environment | Product features for all customers | Designs, demos and technical guidance | Recommendations and plans |
| Writes production code | Yes, every day | Yes, every day | Rarely on customer systems | Usually not |
| Customer contact | Constant, often on site | Low | High, mostly before the sale | High |
| Works for | The product company | The product company | The product company | A services firm |
| Time horizon | Long term, through to production | The ongoing product roadmap | The deal or project | The length of the project |
| Feeds the product | Yes, by design | Is the product | Sometimes | No |
Each role varies by employer. These are the usual patterns.
Why the role grew with AI
For most of its history the forward deployed engineer was a Palantir job. That changed when AI models became useful but hard to deploy, and customers needed help on site.
Wikipedia records that Amazon Web Services set up a unit to embed engineers with customers, Microsoft committed money and staff to an AI implementation unit, and Google Cloud said it would hire engineers to help customers adopt its AI.
The reason is practical. A model on its own does not change how a bank handles claims. Someone has to connect it to messy data, older systems and real workflows, then keep it working. That someone is an engineer who sits with the customer.
Skills a forward deployed engineer needs
On the engineering side: strong Python plus another language, data work, system design and fitting new software into an existing stack. Palantir's post names Python, Java, C++ and TypeScript. For AI roles, Anthropic asks for production experience with LLMs, including prompt engineering, agent development and evaluation.
On the customer side: discovery, scoping, clear communication with engineers and executives on the same day, and comfort with ambiguity. OpenAI asks its engineers to make trade-offs between scope, speed and quality.
How to become a forward deployed engineer
There are a few common routes in. Palantir runs new graduate and internship tracks. Software engineers can move across by building something real for users outside their own team. People from solutions engineering, consulting or a startup usually need to close the gap on production code.
Anthropic's post welcomes software engineers with consulting or product experience, and names former technical founders as a fit. Whichever route you take, you need proof that you can ship in front of a customer. Our roadmap sets out the skills in order.
Forward deployed engineer salary
Pay varies a lot by company, level and city. Our salary page shows posted pay bands by company, with the source for every figure.
Hiring one
Most companies do not need a whole team of forward deployed engineers. They need one engineer who can sit with their people and ship one real system. Send your requirement, and we send you a shortlist of people who fit.
Tell us what you need.
Send your requirement. We send you a shortlist of senior leaders who fit. One agreement and one invoice, with the terms agreed in writing before anything starts.
- No deposit to get started
- Every requirement read by us
- A best-fit shortlist, not a pile of CVs
- One agreement, one invoice
Send your requirement
- No deposit to get started
- Every requirement read by us
- A best-fit shortlist, not a pile of CVs
- One agreement, one invoice
Apply to join
Talent never pays to apply, be shortlisted or be placed.
FAQ
Questions about the forward deployed engineer role
What does forward deployed engineer mean?
The "forward deployed" part comes from military language for units based near the action, not at headquarters. In engineering it means the engineer works out with the customer instead of back at the office.
What is a forward deployed software engineer?
The same role under a longer name. Palantir calls it forward deployed software engineer, and OpenAI uses both titles for different posts. The work is the same: building software inside customer environments.
Who invented the forward deployed engineer role?
Palantir. It made the role a standard job. Accounts differ on the exact year, but not on who started it.
Do forward deployed engineers code?
Yes. The job posts we read at Palantir, OpenAI, Anthropic, Google and Salesforce all ask for strong production coding. The customer work comes on top of the engineering. It does not replace it.
Is a forward deployed engineer the same as a solutions architect?
No. A solutions architect mostly advises and designs. A forward deployed engineer builds and ships. The Pragmatic Engineer reports that solutions architects rarely write code on customers' infrastructure.
Is forward deployed engineer a good career?
It suits engineers who like variety, customers and visible results, and who are happy to travel for work. If you would rather stay deep in one codebase, a product engineering role may suit you better.
Explore more
- How it works
What happens after you send your requirement, step by step.
- Fees
No deposit. One agreement and one invoice when someone starts.
- What is fractional
Senior leaders for part of the week, and when that makes sense.
- Locations
Talent based across Asia, Europe, the Middle East, Africa and the Americas.
How it works
Fees
What is fractional
Locations