The parent role
What is a Forward Deployed Engineer?
A forward deployed engineer (FDE) is an engineer, most often a software engineer, who embeds inside a customer organization to build, deploy, and operate a custom production system on the vendor's platform. The role is defined by ownership: the FDE is accountable for whether the deployed system actually works and gets adopted, not for shipping a spec and handing it off, which is what separates it from consulting and professional services.
The role originated at Palantir and re-emerged across the AI industry as generative AI hit the enterprise last mile: the gap between a capable model and a working production system. It has since branched into specializations, including the forward deployed creative on generative-AI creative platforms.
This page is an independent reference. It is not affiliated with any company hiring for the role, and it synthesizes public listings and primary sources on the forward deployed model.
Function
What a forward deployed engineer does
A forward deployed engineer works inside a customer organization rather than from the vendor's office. The job blends scoping the customer's real problem, building production integrations and custom software on the vendor's platform under the customer's constraints, operating what gets shipped, and routing field insight back to the product team. It is a hybrid of software engineering, consulting, and product work, with one defining trait: the FDE owns the outcome, not just the deliverable.
The role differs from classic professional services in ownership and from sales engineering in timing. A sales engineer demonstrates the product before the deal; a forward deployed engineer arrives after the deal is signed and makes the product actually work inside the customer's systems, data, and processes. Success is measured in deployed, adopted, production software, not in demos delivered or hours billed.
Naming
The engineer's other names
The title is not settled. Palantir's original long form was Forward Deployed Software Engineer (FDSE), and OpenAI still posts that title separately from Forward Deployed Engineer, at a higher experience bar, where it is a distinct role rather than a synonym. Elsewhere the same function appears as Deployment Engineer, AI Deployment Engineer, Technical Deployment Engineer, or Technical Deployment Lead, and some companies route the work through titles that drop the vocabulary entirely, such as Solutions Implementation Engineer or Technical Account Manager.
The functional test cuts through the naming: is the person employed by the platform company, embedded with a customer, building the system in production, and carrying what they learn back into the product. Where that holds, the work is forward deployed engineering regardless of the words on the posting.
Where "forward" gets dropped
Among the frontier labs the practice diverges. Anthropic uses the full phrase without exception across its postings, from individual contributor roles through Manager, Forward Deployed Engineering. OpenAI keeps Forward Deployed Engineering as the team name and Forward Deployed Software Engineer as a distinct senior title, while posting some embedded roles as Deployment Engineer, AI Deployment Engineer, and Deployed Product Manager, with the modifier removed.
The teams are also specializing by industry. OpenAI staffs sector-specific Forward Deployed Engineering groups, including semiconductor, financial services, and government teams, each hiring for the domain knowledge and compliance surface that sector demands, and hires domain experts such as design verification engineers to grow into full forward deployed engineer roles. The vertical changes the domain knowledge required; the operating model, embedded delivery that hardens into reusable solution patterns, stays constant.
The literal title has also spread outside software entirely. Companies building physical or multidisciplinary systems, robotics, aerospace, and advanced manufacturing among them, post "Forward Deployed Engineer" for a hardware, mechanical, or systems engineering background rather than a software one, applying the same embedded, customer-facing model to physical product integration. It is a minority use next to the software-engineering center of the title, but it is real, and it means the title alone does not guarantee a software background the way it does at Palantir, OpenAI, or Anthropic.
What the shorter form signals is not yet clear from the postings themselves. It does not track seniority in any consistent way across companies: Anthropic's forward deployed engineer openings ask three to four years of experience, below the bar OpenAI sets for either of its engineer titles. Read the responsibilities rather than the modifier.
Origin
Where the FDE role comes from
-
1
Military doctrine
"Forward deployed" is Cold War military vocabulary for forces stationed near a theater of operations rather than at a home base, positioned to act at the point of action. The US Navy formalized this as Forward Deployed Naval Forces. The military usage is typically hyphenated ("forward-deployed forces"); the tech-role usage more often drops the hyphen ("forward deployed engineer").
-
2
Palantir coins the role
In its early years, Palantir adapted the term for the Forward Deployed Software Engineer, later shortened to Forward Deployed Engineer: a technical generalist embedded inside a customer organization, owning the problem end to end. Internally these engineers were called Deltas, and until 2016 Palantir had more of them than traditional software engineers.
-
3
The AI-era re-emergence
As generative AI moved into the enterprise, the role spread across AI companies to solve last-mile deployment, with OpenAI and Anthropic among those building their own forward-deployed teams. Postings rose sharply year over year, and the role was widely called one of the hottest jobs in tech. Both labs have since scaled the model further: within a week of each other in May 2026, OpenAI launched the OpenAI Deployment Company and Anthropic announced a standalone enterprise-services firm, each a separately-capitalized entity built to extend forward deployed delivery past what an in-house team alone can reach. More on how the practice scales is covered on the forward deployed engineering page.
-
4
The role branches
The model is now specializing by function. The most visible branch is the forward deployed creative, the same embedded, outcome-owning model applied to creative production on generative-AI platforms. Others are tracked on the forward deployed roles hub.
The practice
Forward deployed engineering, the discipline
Forward deployed engineer names a person. Forward deployed engineering names the practice. Anthropic and OpenAI both title the function that way when they mean the team rather than the individual: Anthropic hires a Manager, Forward Deployed Engineering to run its practice; OpenAI describes a Forward Deployed Engineering team that partners with customers and turns early deployments into reusable patterns.
The distinction matters for anyone reading a posting. A role named for the practice is usually about building or leading the capability. A role named for the person is usually about doing the work inside a customer account. Read as a practice rather than a job title, forward deployed engineering is defined by three properties that recur across every company running the model: the engineer stays employed by the platform company, knowledge moves in both directions between customer and platform, and one-off solutions get abstracted into product.
What is forward deployed engineering, as a team and practice → · What does "forward deployed" mean, across every role →
Comparison
Forward deployed engineer vs forward deployed creative
Same embedded operating model, different medium. A forward deployed engineer builds and operates custom software inside a customer's systems, closing the gap between a platform and the customer's data and infrastructure. A forward deployed creative does the same for custom creative workflows on a generative-AI platform, bridging a generative tool and the customer's creative production. Both own the outcome end to end and send hard technical signal back to the platform team.
Distinction
FDE vs solutions engineer and sales engineer
The clean split is pre-sale versus post-sale, and demo versus production. Solutions and sales engineers work before the deal: they scope, demonstrate, and prove the product can solve the problem. A forward deployed engineer works after the deal: they embed with the customer, build the production system, and stay accountable for whether it works and gets adopted. Many FDE listings explicitly distinguish the role from pre-sales and consulting for exactly this reason.
Compensation
Forward deployed engineer salary
US pay-transparency law forces the frontier labs to publish exact base bands, which makes the engineer's salary unusually well documented for a role this new. Across the companies that disclose, published base sits between roughly $134,500 and $391,000. Anthropic lists $200,000 to $300,000 for its Applied AI forward deployed engineer. OpenAI's forward deployed engineering postings span $146,000 to $385,000, with a midpoint near $261,000. Deloitte, staffing Anthropic deployments, publishes $134,500 to $265,100 for the engineer and $189,200 to $372,900 for the lead.
Every figure above is base salary. Equity sits on top and is where the reported spread comes from: the frontier labs grant on private valuations, so total compensation at senior levels varies with a number the labs revise every six to nine months. Aggregate figures circulating for total compensation should be read with that in mind, and this reference lists a number only where the hiring company published it.
Seniority moves the band more than geography does. The title spans mid-level through principal, and companies level it differently.
The creative branch of the family publishes lower ranges so far; the forward deployed creative salary section tracks those figures as they appear.
Common questions
Frequently asked questions
- What does forward deployed engineer mean?
- A forward deployed engineer is an engineer, most often a software engineer, who embeds inside a customer's organization to build, deploy, and operate a custom production system on the vendor's platform, owning whether the deployed system works and gets adopted rather than handing off a specification. The term "forward deployed" is borrowed from military doctrine for forces stationed at the point of action rather than at a home base; Palantir adapted it for engineers embedded in the field with customers.
- What does FDE stand for?
- Forward Deployed Engineer. Palantir's original long form was Forward Deployed Software Engineer (FDSE), and the shortened form became the industry standard as the role spread.
- Do forward deployed engineers write production code?
- Yes. The role is defined by building and operating real production systems inside the customer's environment, not by advising or demonstrating. Listings consistently require hands-on engineering.
- Is a forward deployed engineer a consultant?
- No. Consultants recommend and hand off; a forward deployed engineer builds, ships, and stays accountable for the outcome in production. The placement is similar, the ownership is not.
- Which companies hire forward deployed engineers?
- Palantir originated the role, and it now appears across the AI industry, including OpenAI and Anthropic, as well as enterprise software companies adopting the embedded deployment model. The creative platforms hiring the related FDC role are tracked on the main page.
- Is there a creative version of a forward deployed engineer?
- Yes. The forward deployed creative (FDC), also titled forward deployed creative technologist (FDCT), applies the same embedded model to creative production on generative-AI platforms. It is covered in full on this site's main reference.
- Is a deployment engineer the same as a forward deployed engineer?
- Often, yes, but the title alone does not settle it. Some companies post Deployment Engineer, AI Deployment Engineer, or Technical Deployment Engineer for work that matches the forward deployed engineer model exactly: employed by the platform company, embedded with a customer, building in production, feeding learning back to the product. OpenAI posts both forms. Anthropic uses the full phrase throughout. Other companies use Deployment Engineer for internal release engineering, which is unrelated work. Read the responsibilities: if the engineer is embedded with a customer and owns the production outcome, it is the same role under a shorter name.
- What is forward deployed engineering?
- Forward deployed engineering is the practice; a forward deployed engineer is the person who does it. Companies use the gerund when naming the team or the discipline, as in Anthropic's Manager, Forward Deployed Engineering or OpenAI's Forward Deployed Engineering team. Read as a practice, forward deployed engineering is defined by three properties that recur across every company running the model: the engineer remains employed by the platform company rather than a consultancy, knowledge flows in both directions between customer and platform, and solutions built for one customer are abstracted into reusable product.
Methodology and sources
How this reference is compiled
This is an independent resource. The role definition is synthesized from public listings and primary sources on the forward deployed model, with claims linked to their sources in the text. Figures are hedged where the underlying data is directional rather than published.
Origin · Palantir forward deployed engineering model; military forward-deployment doctrine
Market · published FDE role reporting and compensation coverage
Creative branch · the FDC reference on this site's main page