# The FDE is the one who stays after the signature: from Palantir's "Delta" to Anthropic's job ads

> A sales engineer's work ends when the customer signs. A forward deployed engineer stays responsible until the system runs in production. That word, "production", is also what two job ads from Palantir and Anthropic have in common.

Original: https://fdetimes.net/en/guides/fde-vs-sales-engineer-production/

Suppose that this week you open two job ads, both titled Forward Deployed Engineer. Palantir's describes building custom applications, LLM workflows and production solutions designed around the realities of one particular customer.

Anthropic's asks candidates to work directly inside customers' systems, building production applications with Claude models, and to already have experience running LLMs in production.

The two companies are very different, yet both ads keep returning to the same word: production. Understand that word and you understand the job. You will also know what to practise before you apply.

It also helps you avoid two traps that catch engineers moving into FDE work: mistaking the FDE for a sales engineer, and comparing pay the wrong way.

## Delta is the one who builds

An analysis of the profession on Substack identifies Palantir as the first company to have FDEs. Palantir's job ad describes how they work: engineers are sent on site to the customer to solve the customer's most pressing problems.

Inside Palantir these engineers are called Deltas. According to FDE Academy, Deltas work alongside Echoes, or Deployment Strategists. An Echo's work is closer to a product manager's, while the Delta is chiefly responsible for the technical build.

The notable detail is that even where the title began, the FDE was never a go-between relaying messages between customer and product team. Someone else did that, under a different title. The Delta is the one who sits down and writes the code.

Paraform, a recruiting platform, defines the FDE as a hybrid role that combines software engineering with hands-on deployment for customers. It also points out what separates an FDE from a consultant: an FDE works with one customer over the long term and writes production code. The whole profession rests on those two ideas: stay for the long term, and write code that actually runs.

## A day at the customer's site

Imagine you are an FDE at an AI company, sent to an insurer. In the morning, a claims handler tells you that the LLM workflow you built last week cannot read data from the legacy claims system.

You do not open a ticket for headquarters and wait. You go into the customer's system, write the missing integration and test it on a handful of real claims. In the afternoon you measure whether the workflow actually cuts processing time, because the customer will use that number to decide whether to keep using it.

The example is imagined, but every step matches the real job ads. Palantir writes about solutions built around the customer's realities. Anthropic writes about working directly inside the customer's systems.

Christian & Timbers, an executive search firm, fills in the rest. In its view, a sales engineer's work is done when the customer signs, whereas an FDE stays responsible after the contract is signed, until the system runs in production and produces measurable results.

## Read a job ad like a specification

One method is easy to apply: sort every line of an ad into one of three groups, namely what you must build, where you work and what is required. Sorting the two ads from the start of this article that way gives the following table.

| Part | Palantir | Anthropic |
|---|---|---|
| What you must build | Custom applications, LLM workflows, production solutions | Production applications with Claude models |
| Where you work | On site with the customer | Directly inside the customer's systems |
| Emphasised requirement | Fitting each customer's realities | Experience running LLMs in production |

Split this way, the two ads plainly agree on what must be built: whatever you make has to run in production for a specific customer. The difference lies in the requirements. Anthropic wants people who have already taken LLMs to production, while Palantir stresses the ability to work to each customer's particular context.

**Key point:** When reading an FDE job ad, look for the word production before you read the list of technologies.

If you have never taken an LLM to production, do not rule yourself out, but do not apply to ads like Anthropic's with only a demo either. Build a small workflow, hand it to a real user and keep it running reliably. That is exactly the kind of experience the requirement is looking for.

## Pay: what does the number include?

According to Paraform's data, FDE base salaries range from $150,000 to $217,000, with a midpoint of $183,000. A compilation by Valletta Software shows that US base pay for FDEs varies widely between companies. Palantir alone posts $125,000 to $200,000 base, excluding equity and bonus.

Try a calculation. Suppose you are offered $165,000 base. The figure sits inside both Paraform's range and Palantir's posted range, so it sounds fine, but it is $18,000 below Paraform's midpoint.

Your decision depends on what sits outside the base. Palantir's posted range excludes equity and bonus, so before you reply, ask about those two components specifically and write base, equity and bonus on three separate lines.

If equity and bonus are substantial, the $18,000 gap in base may not be worth fighting over. If they are small, $18,000 is a concrete figure to negotiate with, and you have market data to cite.

Anthropic's ad states EUR 205k–220k a year. That is a different currency and a different market, so do not convert it and set it beside the US dollar ranges. Ask the recruiter directly what the figure includes.

## Why a polished demo is not enough

The most common trap is treating the FDE as a sales engineer who can code. FDE Academy notes that sales engineers usually write little code, mostly for demos or prototypes, while FDEs write integration code that runs in production. A CV with nothing but polished demos therefore tells the story of the other role. Yours needs real systems and real users.

Another mistake is a CV that only lists technologies. Every line in the two job ads above revolves around a specific customer and a system that has to work for them, so a CV should be written along the same lines.

A good CV line usually answers four questions: which team had the problem, whom you worked alongside, what you built, and how the system runs now.

To start in your current job, volunteer for a request from an internal team that nobody else wants to take on. Sit with that team's users for a session, ship the fix to production yourself, then check whether it actually helps them. Do that for three months and you will have an interview story that fits the job.

The name Delta may belong to Palantir alone, but the way of working behind it is something anyone can practise: when others consider the contract the end of the job, you stay until the code works for the customer.

**Try this week:**

- Open two FDE job ads and sort each line into three groups: what you must build, where you work, what is required. Then count how many times the word “production” appears
- Rewrite one line of your CV so it answers four questions: whose problem it was, whom you worked alongside, what you built, how the system runs in production
- If you have no experience running LLMs in production, build a small LLM workflow for a real user at your company and have them use it for a full week

## Sources

- [What is a forward deployed engineer? A complete guide | Paraform](https://www.paraform.com/insights/what-is-a-forward-deployed-engineer)

- [Palantir Technologies - Forward Deployed Software Engineer](https://jobs.lever.co/palantir/5168e8fd-fec1-4fea-b7a1-81bdaea65850)

- [Palantir Deployment Strategist vs Forward Deployed Engineer: What's the Real Difference?](https://fde.academy/blog/palantir-deployment-strategist-vs-forward-deployed-engineer)

- [Forward Deployed Engineer (Anthropic)](https://jobs.generalcatalyst.com/companies/anthropic/jobs/76428242-forward-deployed-engineer)

- [Forward Deployed Engineer Salary: Real 2026 Bands](https://vallettasoftware.com/blog/post/forward-deployed-engineer-salary)

- [Forward Deployed Engineer vs. Sales Engineer: The Difference Is Production Ownership](https://www.christianandtimbers.com/insights/forward-deployed-engineer-vs-sales-engineer)

- [Forward Deployed Engineer vs Solutions Engineer, Sales Engineer and CSE](https://fde.academy/blog/forward-deployed-engineer-vs-solutions-engineer-sales-engineer-and-customer-success-engineer)

- [What is a Forward Deployed Engineer?](https://joseponsvega.substack.com/p/what-is-a-forward-deployed-engineer)