What Is a Forward Deployed Engineer? (And Do You Need One?)

On June 30, 2026, Amazon Web Services announced it was putting $1 billion behind a job title. Three days later Microsoft launched a $2.5 billion business built around roughly 6,000 experts who work inside customer companies. The job they are betting on is the forward deployed engineer, and OpenAI alone listed 26 openings for it on its careers page this week.

AI models are easy to buy and hard to put to work. Someone has to connect them to a company's real data and tools, then stay until the system runs every day. This guide explains what a forward deployed engineer (FDE) is, where the role came from, and what it pays. If you own a business and are weighing AI agents, the second half covers how to get the same kind of help without hiring a $200,000 engineer.

What is a forward deployed engineer?

A forward deployed engineer (FDE) is a software engineer who works inside a customer's business, rather than at the vendor's office, to build and launch software on that customer's real data and systems. Palantir created the role. OpenAI, Anthropic and AWS now use FDEs to get AI agents into production.

Key Takeaways

• An FDE writes production code inside the customer's systems and stays after launch. Solutions engineers mostly help close the sale, and consultants mostly advise.
• Palantir invented the job and called these engineers "Deltas." Until 2016 it employed more of them than regular software engineers.
• Demand jumped with AI. Indeed's index of FDE job postings rose roughly 729% year over year as of April 2026, and AWS and Microsoft have committed billions to embedded engineering teams.
• OpenAI's current U.S. FDE postings list base pay of $185,000 to $300,000, which puts a full-time hire out of reach for most small and mid-sized companies.
• Businesses can get the same working style from an AI agent implementation partner that builds inside their own tools, measures results and hands over what it built.

What is a forward deployed engineer?

A forward deployed engineer is an engineer the vendor sends into a customer's business to make its product work there. The name comes from the military idea of being "forward deployed," stationed close to where the work happens instead of back at headquarters. In software, that means sitting with the customer's team (in person or remotely), learning how the business runs, and writing the code that connects the product to it.

The definition most people quote comes from Palantir. In a post on its engineering blog, Palantir described the difference between its product engineers and its forward deployed engineers this way: a product engineer's focus is "one capability, many customers," while the FDE's focus is "one customer, many capabilities" (Palantir Blog, "Dev versus Delta").

What does FDE stand for?

FDE stands for forward deployed engineer. Palantir's formal title is Forward Deployed Software Engineer, or FDSE. At Anthropic, FDEs sit on the company's Applied AI team (Anthropic job posting, retrieved October 8, 2026).

Where the role came from: Palantir's Deltas and Echos

Palantir created the forward deployed software engineer role in the early 2010s and nicknamed it "Delta" (The Pragmatic Engineer, August 12, 2025). The name dates from the company's early days, when each business development team was named after a letter of the NATO alphabet. Deltas sat in business development, and their mandate, in Palantir's words, was "to achieve technical outcomes for our customers" (Palantir Blog). The model was central to the company: until 2016, Palantir had more Deltas than regular software engineers (The Pragmatic Engineer, 2025).

Deltas rarely worked alone. Palantir paired them with Deployment Strategists, known internally as "Echos." Palantir's own description is that Echos lean toward product management and Deltas are more technical, though "the lines between the two roles blur heavily quite often" (Palantir Blog, "A Day in the Life of a Palantir Deployment Strategist").

The pairing still makes sense. One person understands the business problem and the people involved, and the other builds the system. We think it's the right way to staff an AI agent project too.

Palantir paired engineers ("Deltas") with deployment strategists ("Echos").

What does a forward deployed engineer actually do?

An FDE owns the path from a customer problem to working software in production. The details change by company, but the work usually follows the same loop:

1. Discovery: Sit with the people who do the work, find the problem worth solving and agree on how success will be measured.
2. Access: Get into the systems that matter, such as the CRM, inbox, phone system, databases and internal tools, with the right permissions.
3. Build: Write the integrations, data pipelines and application code on the customer's real data.
4. Testing: for AI systems this means evals, repeatable tests that show whether the model is accurate enough to trust with real work.
5. Launch and support: Launch, watch how people use it, fix what breaks and improve it.
6. Product feedback: Report patterns from the field to the vendor's product team so the next customer gets a better product.

In AI work the deliverables have become very specific. Anthropic's FDE posting asks engineers to "work within customer systems to build production applications with Claude models" and to deliver "MCP servers, sub-agents, and agent skills that will be used in production workflows." It also expects 25% to 50% travel to customer sites (Anthropic).

Product feedback is what separates an FDE from a contractor. At OpenAI, FDEs working with a call center customer built evals for a voice model that was not yet good enough to deploy. They took the data back to OpenAI's research team, the model improved, the customer became the first to put it into production, and the improvements reached every customer through OpenAI's Realtime API (The Pragmatic Engineer, 2025). OpenAI's FDE team also contributes to its Agents SDK.

Mukul Saha, a senior director analyst at Gartner, summed up the difference from older roles: "A true FDE is typically expected to go further into implementation, working alongside the customer from problem discovery through building and production deployment, while also feeding what they learn back into the core product" (IT Brew, October 1, 2026).

Why is everyone hiring forward deployed engineers right now?

Companies are hiring FDEs because most AI projects stall between a promising demo and daily use, and FDEs are paid to close that gap.

The numbers on that gap are rough. MIT's NANDA initiative reported in 2025 that about 95% of organizations it studied were getting no measurable profit-and-loss return from their generative AI pilots (Fortune, reporting on MIT's "The GenAI Divide: State of AI in Business 2025", August 18, 2025). Gartner predicted in June 2025 that more than 40% of agentic AI projects will be canceled by the end of 2027, citing rising costs, unclear business value and weak risk controls (Gartner, June 25, 2025).

The "last mile" is the work of connecting a capable model to the systems a business already runs on.

In June 2025, Andreessen Horowitz called the FDE "the hottest job in startups" and compared enterprise AI buyers to "your grandma getting an iPhone": they want to use it, but someone has to set it up (a16z, "Trading Margin for Moat", June 2025). At the time, 22 of the 311 open roles on OpenAI's careers page were forward deployed or solutions engineering jobs.

Job posting data shows the same jump:

• Indeed Hiring Lab data reported by the Financial Times showed FDE job listings up more than 800% between January and September 2025 (Financial Times).
• By April 2026, Indeed's index of FDE postings stood 5,230% above its January 2025 level, roughly 729% higher than a year earlier. Business Insider notes these are index values against a January 2025 baseline, not raw posting counts (Business Insider, May 16, 2026).
• On October 8, 2026, OpenAI's careers board listed 26 roles with "forward deployed" in the title out of 816 openings, and Anthropic's listed 6 (our count from the public job boards).

In 2026 the large cloud companies followed. AWS created a Forward Deployed Engineering organization backed by $1 billion to "embed thousands of experts with customers to co-develop and deploy agentic AI solutions" (About Amazon, June 30, 2026). Microsoft launched Microsoft Frontier Company with $2.5 billion and about 6,000 embedded experts (Microsoft, July 2, 2026). Google Cloud's CEO said in May 2026 that it was also hiring for the role (Business Insider, 2026).

There is a skeptical view too. Some argue that "forward deployed engineer" is partly a new label for solutions and integration engineering, a point Wikipedia attributes to a16z, which called it "title arbitrage" (Wikipedia, retrieved October 8, 2026). Either way, the useful test is whether the person writes and owns production code for the customer.

Forward deployed engineer vs. solutions engineer vs. software engineer vs. consultant

An FDE builds and owns the working system inside one customer's business, a solutions engineer helps win the deal, a product software engineer builds features for every customer, and a consultant advises.

• Forward deployed engineer: Makes the product work inside one customer's business, writes production code in the customer's systems, shows up after the contract through launch and beyond, is measured on the customer's result in production, and owns it after launch and keeps improving it.
• Solutions engineer / architect: Designs the solution and helps close the sale, rarely writes production code (mostly demos and prototypes), shows up mostly before the sale, is measured on technical win and deal size, and does not own the work after launch.
• Software (product) engineer: Builds features used by all customers, writes production code in the core product, shows up ongoing inside the vendor, is measured on product quality and speed, and owns only the product itself after launch.
• Consultant: Analyzes and recommends, usually does not write production code, shows up for a defined project, is measured on deliverables and hours, and does not own the work after launch.

OpenAI draws the line between its own solutions architects and FDEs in the same place. Its FDEs are more hands-on and "write code directly on customer infrastructure" (The Pragmatic Engineer, 2025).

For business owners, this comparison is also a buying guide. Some firms selling "AI agents" work like consultants: they run a workshop, hand over a slide deck or a prototype, and leave. Look for one that works like the FDE column.

How much do forward deployed engineers make?

Forward deployed engineers in the U.S. typically earn well into six figures. Recent sources:

• OpenAI: U.S. FDE postings list base pay of $185,000 to $300,000 plus equity. Its Forward Deployed Software Engineer role in San Francisco lists $185,000 to $325,000 (OpenAI careers, retrieved October 8, 2026).
• Anthropic: its London FDE posting lists £225,000 to £255,000 (Anthropic, retrieved October 8, 2026).
• Indeed: pay for the role runs from about $170,000 to over $200,000 (Business Insider, May 2026).

Those figures are salary alone, before benefits, recruiting costs and the months it takes to find someone. For many small and mid-sized companies, one senior FDE would cost more each year than their entire AI budget.

Why businesses hire forward-deployed AI agent teams instead of an FDE

Most small and mid-sized businesses don't need a full-time forward deployed engineer. They need the FDE way of working applied to one or two AI agent projects that matter: answering leads, booking appointments, following up on quotes, triaging the inbox or updating the CRM.

Working with an outside team can also raise the odds of success. In MIT's 2025 study, AI tools bought through partnerships with specialized vendors reached deployment about 67% of the time, compared with about 33% for systems companies built entirely in-house (Fortune, August 2025). The authors note the comparison rests on a small interview sample, so treat it as a signal rather than a guarantee.

A forward-deployed AI agent team should give you what the big players promise their enterprise customers, at a scale that fits your business:

• An agent that runs on your real tools and data from the first week.
• A named person who learns how your team works before building anything.
• A clear metric agreed up front, such as response time, booked calls or hours saved.
• Testing before launch and monitoring after.
• Documentation, prompts and access that stay with you when the project ends.

AWS describes the goal of its own program in similar terms, saying customers should leave its FDE engagements "self-sufficient" with "runbooks, architectural documentation, and trained internal champions" (About Amazon, June 2026). A small business can ask for the same.

What to look for in an AI agent implementation partner

A good partner works the way a forward deployed engineer does. Check these six things before you sign.

They build inside your systems

Ask where the agent will run and what it will connect to. You want work done in your CRM, inbox, phone system and data from the start, with access scoped to what the agent needs.

They start with one outcome and one number

A good partner narrows the first project to a single workflow and agrees on how to measure it. Be wary of anyone promising to "transform the business" in the first engagement.

They test before launch and monitor after

Ask how they will know the agent is accurate. They should be able to describe their evals (test cases drawn from your real conversations or records) and how they will watch the agent once it is live.

They take security seriously

Find out what data the agent can see, where it is stored, who can access it and how actions are logged. Permissions should follow the principle of least privilege.

They stay through adoption

Plenty of work happens after launch. Ask who fixes problems in week two, how your staff will be trained and how improvements will be handled.

You own what they build

Prompts, agent skills, integrations and documentation should belong to you. Avoid setups that leave you locked into one vendor's account.

Red flags

• Demos that run on sample data only.
• No production references you can call.
• Vague answers about how accuracy is measured.
• "Agent washing," Gartner's term for rebranding chatbots and automation tools as agents without real agent capabilities (Gartner, 2025).

Checklist: are you ready for an AI agent project?

You are ready to bring in a forward-deployed AI agent team when you can tick most of these boxes:

• One owner on your side who can make decisions and answer questions.
• One high-volume, repetitive workflow to start with (for example, new lead follow-up).
• Access to the systems involved: CRM, email, phone, calendar or helpdesk.
• A sample of real data, such as past conversations, tickets or records.
• A success metric and today's baseline for it.
• A budget range and a decision timeline.
• Someone responsible for security and data access.
• A plan for who on your team will use and oversee the agent.

Save this checklist for your first conversation with an implementation partner.

If you can tick only a few, start with the first two. A clear owner and a single workflow are enough for a scoping call.

Frequently asked questions

What does FDE stand for?

FDE stands for forward deployed engineer: an engineer who works inside a customer's business to build and launch software on its real systems. Palantir's formal version of the title is Forward Deployed Software Engineer (FDSE).

Is a forward deployed engineer a sales role?

No. FDEs work closely with customers, but their main job is building and running production software. Solutions engineers and sales engineers focus on the sale, while FDEs typically arrive after the contract is signed.

How is an FDE different from a solutions engineer?

A solutions engineer designs the approach and helps win the deal, usually before the sale. An FDE builds the system inside the customer's environment after the sale and stays responsible for it in production.

How much does a forward deployed engineer make?

In the U.S., recent OpenAI postings list FDE base pay of $185,000 to $300,000 plus equity, and Indeed data puts typical pay at about $170,000 to over $200,000 (October 2026 and May 2026 figures).

Is the forward deployed engineer a new role?

No. Palantir created it in the early 2010s. What is new is the scale: since 2025, OpenAI, Anthropic, AWS, Microsoft and Google Cloud have built or expanded forward deployed teams to get AI into production for customers.

Does my small business need to hire a forward deployed engineer?

Usually not. Most small and mid-sized businesses get better value from an AI agent implementation partner that works the same way: it builds inside your tools, measures results, stays through launch and hands over what it built.

How much does it cost to build and deploy an AI agent?

It depends on the number of systems the agent connects to, how messy your data is, how much testing it needs, how risky its actions are and how much ongoing monitoring you want. Ask any partner to price one scoped workflow first.

Work with a forward-deployed AI agent team

If you have a workflow you would like an AI agent to handle, contact Reach Them AI to scope the project. Bring the readiness checklist above, and we can work out which workflow to start with and which systems the agent would need to reach.

Last updated: October 9, 2026

Sources

1. Palantir Blog, "Dev versus Delta: Demystifying engineering roles at Palantir." https://blog.palantir.com/dev-versus-delta-demystifying-engineering-roles-at-palantir-ad44c2a6e87
2. Palantir Blog, "A Day in the Life of a Palantir Deployment Strategist." https://blog.palantir.com/a-day-in-the-life-of-a-palantir-deployment-strategist-951cb59a5a96
3. Gergely Orosz, "What are Forward Deployed Engineers, and why are they so in demand?" The Pragmatic Engineer, August 12, 2025. https://newsletter.pragmaticengineer.com/p/forward-deployed-engineers
4. Andreessen Horowitz, "Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in Startups," June 2025. https://a16z.com/services-led-growth/
5. Financial Times, Indeed Hiring Lab data on forward deployed engineer listings, 2025. https://www.ft.com/content/91002071-7874-4cb7-9245-08ca0571c408
6. Cadie Thompson and Lakshmi Varanasi, "Job postings for this tech role have grown more than 700% in the last year," Business Insider, May 16, 2026. https://www.businessinsider.com/forward-deployed-engineer-jobs-in-demand-2026-5
7. Francessca Vasquez, "AWS invests $1 billion to embed AI forward deployed engineers with customers," About Amazon, June 30, 2026. https://www.aboutamazon.com/news/aws/aws-1-billion-forward-deployed-ai-engineers
8. Microsoft, "Microsoft Frontier Company: AI engineering that amplifies and protects your intelligence," July 2, 2026. https://blogs.microsoft.com/blog/2026/07/02/microsoft-frontier-company-ai-engineering-that-amplifies-and-protects-your-intelligence/
9. Anthropic, "Forward Deployed Engineer" job posting (London), retrieved October 8, 2026. https://job-boards.greenhouse.io/anthropic/jobs/5423029008
10. OpenAI careers, Forward Deployed Engineer and Forward Deployed Software Engineer postings, retrieved October 8, 2026. https://jobs.ashbyhq.com/openai
11. Patrick Kulp, "What it's like to work in tech's hottest new role," IT Brew, October 1, 2026. https://www.itbrew.com/stories/forward-deployed-engineer-role