forward deployed engineer what they do, when you need one

Do You Need a Forward Deployed Engineer? A Buyer's Guide

Staff Augmentation

A forward deployed engineer (FDE) is a software engineer placed inside one customer's organization to build working software against that customer's own systems and data, and judged by whether the customer's way of working actually changes. The role began on the product-vendor side of a deal, and the title now travels further: Illinois Tech quotes the CEO of a talent firm saying companies need "FDEs, not FTEs." It describes a job that sits between building a product and getting it to work in someone else's company.

If you lead engineering, you may meet the term in a vendor's proposal, in a services pitch or in a page of search results full of job postings. All three raise the same question: do you need one, or do you need a different hire? An FDE closes the gap between a product that works in a demo and one that works in your systems. It does not fill a seat on your team, and the two get confused. This guide is for the person deciding, so it leaves out how to become one, what they earn and where they are hiring.

What is a forward deployed engineer?

A forward deployed engineer is an engineer that a vendor embeds with its customers to build custom software in the customer's real systems, usually AI solutions. Illinois Tech's explainer credits Palantir with coining the term and notes that what the FDE learns in the field flows back into the vendor's core product. Palantir's own job posting claims the role as its own: "We pioneered this unique position, embedding talented engineers directly with our customers."

The explainer, summarizing Palantir's framing, gives the shortest contrast with a regular developer: a developer focuses on one capability across many customers, while a forward deployed engineer focuses on one customer across many capabilities.

Two neighboring roles are often mistaken for it. A consultant "advises and leaves a document," while an FDE "writes production-grade code inside the customer’s environment and answers for whether the workflow changed," according to a practitioner guide on the role. The same guide draws the line with a solutions architect at production code: an architect "designs and builds proofs of concept," and an FDE "ships code that runs."

What does a forward deployed engineer do?

A forward deployed engineer scopes a problem with the people who live with it, builds the solution in the customer's own stack, and stays until the workflow changes. Palantir's posting says these engineers "work side by side with our customers" and lists the work: "Developing custom applications tailored to customer needs," "Engaging directly with customer stakeholders, from technical teams to executives," and owning "the end-to-end execution and implementation of high-stakes projects." It also expects travel of "up to 25%" to client sites.

Code is only part of the week. The practitioner guide puts it at "about half," with the rest going to mapping processes with the people whose work is about to be automated, meetings about whose team owns the data, and infrastructure work. That mix matters to a buyer: you are paying for someone who negotiates your organization as much as someone who codes in it.

Which problems does a forward deployed engineer solve?

An FDE solves the gap between a working product and a working deployment. Illinois Tech states the cause plainly: "AI is easy to demo and hard to deploy." The practitioner guide describes what fills that gap: someone has to decide which workflows deserve automation, untangle data that arrives in several formats, define what a good answer looks like when your own team disagrees, and stay until people actually use the result.

An FDE does not solve three other problems that often travel with it:

  • A defined role you cannot fill. If you already know the role, the skills and the start date, the answer is to hire the person for your own team.
  • Ownership after the engagement. The FDE's work is scoped around one customer's deployment. What stays in your systems when the engagement ends is a separate question, and you have to ask it.
  • Decisions about access. An embedded engineer needs reach into your most important systems, and how much reach belongs to you to decide.

Forward deployed engineer or an engineer on your team?

The difference is who the engineer works toward. An FDE is placed with you by whoever sells the product or the service, so that your deployment succeeds, and at a product vendor the work also improves the vendor's product. An engineer who joins your team works on your roadmap, under your leads.

‍

Forward deployed engineer Engineer who joins your team
Placed by The vendor or service provider that sells the deployment A partner that finds and employs them
Works toward One customer's deployment of a product or platform Your roadmap and your priorities
What the work feeds The customer's workflow and, at a product vendor, the core product Your codebase and your team
Fits when A product you bought has to work in your systems You know the role and need the person

DevLatam fills the second kind of seat. Its home page says "You direct the work. Architecture, code review, and product decisions stay with your engineering leaders. You keep the project, and we fill the position." The need an FDE answers, a person who understands how your business runs and can make AI work inside it, can also be met this way. As the home page puts it, "Making AI work inside your business takes an engineer who learns how your business runs." What changes is who directs the engineer and whose product the work serves. The profiles DevLatam finds for this are on the page about AI, security and data engineers, starting with "Engineers who take LLMs and agents from prototype to production."

How do you decide whether you need one?

Run the decision through five questions before you sign anything:

  1. Is what you need to deploy a product or platform that someone sells? If yes, ask the seller what its embedded engineers will do and apply the four questions in the next section. If you are building the capability yourself, the hiring path fits better.
  2. How much of the work is discovery? If the deployment is a configuration of a documented product, a good implementation plan covers it. If nobody can say yet what the finished workflow looks like, someone has to find out inside your systems, and that is the case for an embedded engineer.
  3. Who answers the engineer's questions on your side? An embedded engineer needs a counterpart who knows how the business runs. Without one, the engagement waits on meetings, and a role you define and fill on your own team may move faster.
  4. Who decides what the engineer can touch? DevLatam's page on who legally employs its engineers notes that "AI, security, and data roles need access to your most important systems to do their job," and that "someone in your organization has to decide what that access includes, what it excludes, and who reviews it when the work changes." Writing that decision down is the subject of DevLatam's AI governance framework for engineering teams.
  5. What stays when they leave? Work recorded in documentation, tests and decision records stays. Work that lives in one person's head does not, whoever employs the person.
forward deployed engineer what they do, when you need one

What should you ask a partner or service provider that offers a forward deployed engineer?

Ask four things, because the title does not guarantee the job. The practitioner guide warns that some postings carry the title for work that is not this job, such as onboarding, technical support and business reviews, and the same caution applies to a proposal.

  • What code will this person write, and in whose repository?
  • Who reviews that code before it merges?
  • What access do they need to our systems and data, and for how long?
  • What do we keep when the engagement ends?

If the answers describe advice and a slide deck, you are buying consulting. If they describe production code that your team can read and maintain, you are buying engineering.

When an FDE is the answer, and when it is not

An FDE is the right answer to a deployment gap on a product you have bought. It is the wrong answer to a hiring gap on a team you run. If your gap is a person, with a role you can describe in twenty minutes, start with the role: see how an AI-augmented team works when the work repeats, or tell DevLatam which profile you need on the AI, security and data page.

Frequently asked questions

What is the difference between a forward deployed engineer and a regular developer?

In Palantir's framing, a regular developer builds one capability that many customers use, while a forward deployed engineer builds many capabilities for one customer. The FDE works inside the customer's systems and, at a product vendor, feeds what they learn back into the product.

Is a forward deployed engineer a consultant?

No. A consultant's output is advice, usually in a document. An FDE's output is working code in the customer's systems, and the FDE is accountable for whether the customer's workflow changes.

‍