Vibe Engines Learn
Forward Deployed Engineer  /  FDE vs FDSE vs DS
FDE Track~12 min readUpdated Jul 2026
Role comparison

Two ladders,
one deployment

Palantir did something the rest of the industry copied halfway: it split forward-deployed work into two distinct roles with different ladders, different interviews and different compensation, and then everyone else adopted the title without the split. That is why “FDE” now means two different jobs depending on who is saying it — and why candidates regularly interview for one while preparing for the other.

01

The split, as Palantir describes it

Palantir’s own framing is “Dev versus Delta”: the product organisation that builds the platform, and the forward-deployed organisation that makes it work at a customer.13 Inside the forward-deployed side there are then two roles, and the distinction is not seniority — it is what you are accountable for.

FDSE — Forward Deployed Software EngineerDeployment Strategist
Accountable forThe system working: pipelines, integrations, applications on the customer’s dataThe deployment succeeding: the problem chosen, the stakeholders, the outcome
A normal dayData models, transforms, ontology, application logic, debugging someone else’s schemaWorking sessions with operators, mapping a workflow, deciding what gets built next
LadderEngineeringNot an engineering ladder
InterviewCoding, decomposition, systems — an engineering loop19Case-style, structured problem solving, communication
CompensationEngineering bands, self-reported at roughly $171K–$295K total, median near $211K16 self-reportedA separate track with its own bands
Failure modeBuilding an excellent system for the wrong problemChoosing the right problem and being unable to judge whether the build is sound
→ Why the pair exists

Because the two failure modes above are real and they defend against each other. An engineer left alone with a customer optimises the thing they can see; a strategist left alone commits to outcomes nobody has costed. Pairing them is a deliberate structure, and it is the single most-copied and least-understood idea in the whole forward-deployed model — most companies hire the engineer and expect them to do both jobs.

02

What the rest of the industry did with it

Adopted the title, dropped the pairing, kept the expectations of both.

When OpenAI, Anthropic, and a long list of AI companies adopted “forward deployed engineer”, almost none adopted the two-role structure.910 The result is a single title that absorbs both accountabilities — which is exactly why the role is hard to fill and why the bar is often described as staff-engineer engineering plus a temperament most engineers have never been asked to develop.11

Where a company kept a version of the split

  • Two people land at each customer, one engineering-weighted and one outcome-weighted.
  • There is a named person whose job is choosing the problem, and it is not the person building.
  • The engineer is not the one negotiating scope in the steering committee.
  • Job descriptions for the two are visibly different documents.

Where one title carries both

  • You do discovery, scoping, building, demos, the security review and the QBR.
  • “Owns the full arc of a deployment” appears in the posting.9
  • Nobody senior is accountable for whether the chosen problem was worth solving.
  • This is the common case, and it is why the role burns people who were hired for one half of it.
→ The question to ask in the interview

“Who decides what we build at a customer, and are they the same person who builds it?” A company with a real split answers immediately. A company without one answers “the FDE, with the account team”, which is a truthful description of a job that contains two jobs. Neither answer is disqualifying — but the second one should change what you negotiate and how you plan your week.

03

Which one are you being interviewed for?

The loops diverge sharply, and candidates routinely prepare for the wrong one. The signal is in the rounds.

FDSE

Engineering loop with a deployment accent

Incremental coding where each stage invalidates your last design, a decomposition round scored on your clarifying questions, a learning round on unfamiliar documentation, and a systems discussion grounded in messy customer data.1920 Prepare by building and by practising the rounds — the decomposition and learning simulators cover the two most distinctive.

DS

Case-style loop

Structured problem solving on a business situation, stakeholder judgement, prioritisation under ambiguity, and communication under pressure. Coding is not the axis being measured. Prepare the way you would for a consulting case, plus enough technical literacy to know when an engineer is telling you something is hard.

Both

The shared bar

Every version of this role tests whether you can sit with ambiguity in front of someone who is paying, and produce a next step rather than a caveat. That is what the roleplay simulator drills, and it is the axis on which both ladders actually promote.

→ The career mistake this page exists to prevent

Treating Deployment Strategist as a junior FDSE, or as a step toward it. It is a different ladder, with its own progression and its own bands. Moving between them is possible and it is a lateral change of career, not a promotion — and the people who are unhappiest in forward-deployed roles are frequently those who joined one ladder believing it led to the other.

04

Picking, if you have the choice

Choose the engineering ladder ifChoose the strategy ladder if
You want to keep writing code, and losing that would bother you within a yearYou are energised by the room more than by the repository
Your satisfaction comes from a thing working that did not work beforeYour satisfaction comes from an organisation changing how it operates
You want optionality back into product engineering laterYou are aiming at product, operations or general management
You would rather debug a schema than run a steering committeeYou would rather run the steering committee than debug the schema
→ The honest note on coding

Both roles carry a real risk of technical atrophy, and it is worse on the strategy ladder. If you take a forward-deployed role, protect the depth deliberately — the market re-prices you against engineers who spent those years in a codebase, and “I was customer-facing” is not a defence a systems interview accepts. Is the role worth it covers this and the other costs properly.

Practise the distinctive rounds

Whichever ladder, the loop is unusual

The Palantir loop Decomposition simulator Learning round lab Stakeholder politics
Frequently asked

Quick answers

What is the difference between an FDSE and a Deployment Strategist at Palantir?

They are two different ladders, not two levels of one. A Forward Deployed Software Engineer is accountable for the system working — pipelines, integrations, applications on the customer’s data — and sits on the engineering ladder with an engineering interview loop. A Deployment Strategist is accountable for the deployment succeeding: which problem is chosen, the stakeholders, the outcome. That role is not an engineering ladder, is interviewed case-style, and is compensated on its own track.

What does “Dev versus Delta” mean?

It is Palantir’s framing for the split between the product organisation that builds the platform and the forward-deployed organisation that makes it work at a specific customer. The forward-deployed side is then itself split into the engineering role and the strategy role, which is the structure most other companies adopted the title of without adopting the structure.

Is “FDE” at other companies the same as Palantir’s FDSE?

Roughly, but usually with more scope. Most companies that adopted the title did not adopt the two-role pairing, so a single FDE absorbs both accountabilities — discovery, scoping, building, demos, the security review and the business review. That is a large part of why the role is hard to fill and why the bar is often described as staff-level engineering plus a temperament most engineers have not been asked to develop.

Which role should I interview for?

Match the loop to your strengths. The engineering ladder tests incremental coding where each stage invalidates your last design, a decomposition round scored on your clarifying questions, and a learning round on unfamiliar documentation. The strategy ladder tests structured problem solving on a business situation, stakeholder judgement and communication. Both test whether you can sit with ambiguity in front of a paying customer and produce a next step.

Can you move from Deployment Strategist to FDSE?

Yes, and it is a lateral change of career rather than a promotion. Treating the strategy role as a junior version of the engineering one is the most common career mistake in this family of titles — they have separate progressions and separate compensation bands, and people who join one expecting it to lead to the other are consistently the least satisfied.

Receipts

Sources

Every number on this page traces to one of these. Where a figure is self-reported or crowd-sourced rather than first-party, it is labelled inline.

Cited on this page

  1. OpenAI — Forward Deployed Engineer job description — “full arc of a deployment”. openai.com/careers/forward-deployed-engineer-(fde)-nyc-new-york-city/
  2. Anthropic — Forward Deployed Engineer, Applied AI (JD) — 40/30/30 split; MCP servers, sub-agents and agent skills as deliverables. jobs.menlovc.com/companies/anthropic/jobs/69674588-forward-deployed-engineer-applied-ai
  3. First Round Review — “So you want to hire a forward deployed engineer” — the staff-engineer bar. review.firstround.com/so-you-want-to-hire-a-forward-deployed-engineer/
  4. Palantir blog — “Dev versus Delta” — FDSE and Deployment Strategist as distinct forward-deployed roles. blog.palantir.com/
  5. levels.fyi — Palantir FDSE compensation — www.levels.fyi/companies/palantir/salaries/software-engineer/title/fdse
  6. Exponent — Palantir Forward Deployed Engineer interview guide — www.tryexponent.com/guides/palantir-forward-deployed-engineer-interview
  7. Blind — Palantir FDSE interview, decomposition round (candidate account) — anonymous first-hand report; lower confidence than a first-party source. www.teamblind.com/post/advice-wanted-palantir-fdse-interview-decomp-round-1ffoysoz
FDE vs FDSE vs Deployment Strategist · part of the FDE track · Vibe Engines · 2026
Finished this one? 0 / 206 Handbooks done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

Interview Prep Forward Deployed Engineering

More Handbooks

Explore more from Vibe Engines

Roadmaps →
System Designs →
AI System Designs →
Algorithms →
Labs →
Paper Breakdowns →