By FDE Interview Prep, a SourceStrongAI company

On this page13 sections
  1. The difference on one screen
  2. Palantir’s Devs and Deltas
  3. Where the FDE title says “software engineer”
  4. The SWE bar
  5. What each role is measured on
  6. How the interviews differ
  7. What FDE hiring leaders say goes wrong, and how it shows in a loop
  8. Which one fits you
  9. Moving between the two
  10. Practice the difference out loud
  11. Posts on this topic
  12. Questions people ask
  13. Keep reading

You write software for a living, and a recruiter has just asked whether you would consider the forward deployed version of the job. Or you are a new grad whose Palantir application asks you to confirm that you want the role rather than Software Engineer. Source 1Apply: Forward Deployed Software Engineer, New Grad - Commercial (New York, NY) - Palantir on LeverPublisherPalantir Technologies (Lever)Source typecompany job posting Here is the short answer. In Palantir’s words, a software engineer’s (SWE’s) focus is “one capability, many customers,” and a ’s (FDE’s) is “one customer, many capabilities.” Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 3A Day in the Life of a Palantir Forward Deployed Software EngineerPublisherPalantir BlogSource typecompany blog Where employers have said so on the record, the technical bar is not lower: at Ramp, FDE candidates must pass the software engineering interview loop. Source 4What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interview What changes is what you answer for, which is one customer’s result, and, at the employers that add them, rounds built on open-ended problems and customer conversations. If the role itself is new to you, start with what a forward deployed engineer is.

The difference on one screen

The table is our summary. The sections below give the sources for each row.

Software engineerForward deployed engineer
ScopeOne capability, many customersOne customer, many capabilities
Where the code runsInside your company’s productIn or beside the customer’s systems
Who sets prioritiesThe product roadmapOne customer’s goal
Judged onHow the capability works for everyoneWhether the customer’s goal moved
InterviewCoding, design, behavioralThe same core, plus rounds built on a customer problem, at some employers

Two rows need a warning. “Judged on” is our reading of what employers write, not a published rubric. And the interview row varies more by employer than by title, which is why the interview section below goes company by company.

Palantir’s Devs and Deltas

The cleanest statement of the difference comes from the company whose posting says it pioneered the role. Source 5Palantir Technologies - Forward Deployed Software Engineer (New York, NY)PublisherPalantir (Lever job board)Source typecompany job posting Palantir’s blog says software engineers and forward deployed software engineers are its biggest engineering roles by headcount, and that it calls them “Devs” and “Deltas” internally. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog The name Delta goes back to Palantir’s early days, when each Business Development team was named after a letter of the NATO alphabet. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog

The org chart tells you the rest. Palantir’s careers page says Deltas sit in its Business Development organization, with a mandate to achieve technical and operational outcomes for customers, while Devs sit in Product Development. Source 6Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring page The one-line contrast at the top of this guide comes from the same blog: a Dev builds one capability that many customers use, and a Delta brings many capabilities to one customer. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 3A Day in the Life of a Palantir Forward Deployed Software EngineerPublisherPalantir BlogSource typecompany blog Our Palantir company guide collects what the company publishes about its loop.

Dev: one capability, used by three customers.Dev: one capability, many customerscapabilitycustomercustomercustomerDelta: one customer, served across three capabilities.Delta: one customer, many capabilitiescapabilitycapabilitycapabilitycustomer
A software engineer owns one component used by every customer; a forward deployed engineer owns whatever one customer needs, across components.

Palantir adds details worth knowing before an interview:

  • A Delta is not a consultant. Palantir calls that a common misconception: in a Delta’s words on its blog, consultants generally create a one-time analysis, recommendation or solution, while Deltas build a long-term solution with the customer. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog
  • There used to be two kinds. A Palantir blog post from October 2025 says forward deployed engineers were originally called “Echos” and “Deltas”, monikers that roughly map to engineers who are better at talking to humans and engineers who are better at talking to machines. Source 7Beyond Founder Mode: Mission Mode (Palantir Blog)PublisherPalantir BlogSource typecompany blog
  • The human-facing half now has its own job. Palantir’s New York posting is filed under the team label “Echo”, and its FDSE posting under “Delta”. Source 8Palantir Technologies - Deployment Strategist (New York, NY)PublisherPalantir (Lever job board)Source typecompany job posting If you would rather own the customer conversation than the code, read the Deployment Strategist posting too. OpenAI made a similar split: Colin Jarvis said on a South Park Commons panel in May 2026 that OpenAI’s FDE team started with only FDEs, then added an “echo” role to handle account work. Source 9The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview

The same request, on two desks

Here is the difference as a scenario of our own. A hospital customer says, “Your discharge report is too slow.”

  • The Dev asks whether the report is slow for every customer. They profile the query, find a missing index that hurts every large tenant, fix it in the product and ship it in the next release. Everyone benefits, and this hospital waits for the release.
  • The Delta sits with the discharge nurses and learns that the report is only slow at the start of the day shift. They check what the report is waiting on at that hour (the query is below), and find it blocked behind the nightly load, which truncates and reloads the discharges table and is still running when the nurses arrive. The load belongs to the hospital’s data team, so the Delta does not move it on their own: they show that team the evidence and agree to finish the load before the shift starts. They add a small check that warns when the data is stale, and the problem is gone the same week. Then they write up the load-timing issue for the product team, because other hospitals will hit it too.

Here is the check, in Postgres. It lists every session waiting on a lock, what is blocking it, and how long the blocker has been running:

SELECT w.application_name AS waiting,
       b.application_name AS blocked_by,
       left(b.query, 40)  AS blocker_query,
       date_trunc('second', now() - b.xact_start) AS blocker_running_for
FROM pg_stat_activity w
JOIN pg_stat_activity b ON b.pid = ANY (pg_blocking_pids(w.pid))
WHERE w.wait_event_type = 'Lock';

-- waiting          | blocked_by   | blocker_query                           | blocker_running_for
-- discharge_report | nightly_load | COPY discharges FROM STDIN (FORMAT csv) | 00:41:12

Read the result like this. The report is waiting on the nightly load, and the last column says how long the load’s transaction has been open. The blocker’s query column shows what the load is running now, the reload; the lock it holds was taken by the truncate at the start of the same transaction, and a truncate blocks even plain reads of the table until the load commits.

Both are engineering. The Dev’s question is “what is wrong with the capability?” The Delta’s question is “what does this customer need to happen?” Our advice: in an FDE interview, let the second question lead, and show you would still ask the first. The Dev’s half, reading a slow query’s plan, is its own skill; practice it with the free question on reading a query plan and fixing a slow query.

Where the FDE title says “software engineer”

If you are hunting for a clean line between the two jobs, the titles will not give you one. Several employers put the FDE role inside a software engineering title:

  • Ramp posts “Software Engineer, Forward Deployed”, on its Forward Deployed team. Source 10Software Engineer, Forward Deployed @ RampPublisherRamp (Ashby job board)Source typecompany job posting
  • Microsoft posts a “Software Engineer - FDE” series for its Frontier Company, and says those engineers work in small crews with data scientists, product managers and domain experts. Source 11Microsoft Careers: Software Engineer - FDEPublisherMicrosoftSource typecompany job posting
  • Sierra has no FDE title on its main board; its customer-facing role for building agents is “Software Engineer, ”, on the Agent Engineering team. Source 12Software Engineer, AgentPublisherSierra (Ashby)Source typecompany job posting
  • OpenAI posts a separate “Forward Deployed Software Engineer” title and says it is looking for customer-focused software engineers. Source 13Forward Deployed Software Engineer - SF (Ashby)PublisherOpenAI (Ashby job board)Source typecompany job postingSource 14Forward Deployed Software Engineer - NYC (Ashby)PublisherOpenAI (Ashby job board)Source typecompany job posting
  • C3 AI’s new-grad FDE posting calls the job a full-stack software engineering role with direct customer exposure. Source 15Forward Deployed Engineer, New Grad 2027 | C3 AIPublisherC3 AISource typecompany job posting

The reverse also happens: some roles titled FDE are closer to implementation or pre-sales. Industry writer Thomas Otter said, in December 2025, that he suspects many roles labeled FDE today are implementation or pre-sales roles with a cooler label. Source 16on the forward deployed engineerPublisherThomas Otter (Substack)Source typeindustry writer’s personal blog That is one writer’s suspicion, not a measurement, but it is the right reason to read past the title.

So read the lines that say what you will build and where it runs. Our free lesson on telling FDE, SWE, SA and SE roles apart gives you four tests to run on any posting, and how to read an FDE job posting line by line shows them on real postings.

The SWE bar

A worry software engineers raise is that FDE is a softer technical job. The employers who have spoken about it say otherwise, with some nuance.

The same loop, at some employers. Leo Mehr, Director of Engineering at Ramp, said on the dearCC podcast in June 2026 that FDE candidates at Ramp face the same technical bar and have to pass the software engineering interview loop. Source 4What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interview One poster on Blind reported, in April 2026, that a Ramp recruiter described the FDE role as the same as SWE internally, with customer conversations included. Source 17Ramp FDEPublisherBlind (teamblind.com)Source typecandidate report on Blind

A bar to clear, not a score to maximize. Ramp’s engineering blog says it validates coding, debugging, data structures and system design as a bar to pass, but does not over-index on perfection. Source 18Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog The same blog says candidates who performed just okay in coding interviews, with mixed or soft yeses, have turned out to be incredible FDEs once they joined. Source 18Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog Read those two together: you need to clear the bar, and clearing it well is not what sets you apart.

Palantir’s early FDEs. Tiffany Siu, a former Palantir recruiter, told First Round Review in February 2026 that Palantir’s early FDEs had to pass the same interview loops and facets as software engineers. Source 19So You Want to Hire a Forward Deployed EngineerPublisherFirst Round ReviewSource typenews report In remarks reported by Lenny’s Podcast in May 2025, Nabeel Qureshi, a former Palantir FDE, said Palantir had two types of FDE: one had to pass a software engineering interview, and the other got a technical interview more about whether the candidate could reason about data. Source 20How Palantir built the ultimate founder factory | Nabeel S. Qureshi (YouTube uploaded en-US captions)PublisherLenny's Podcast, YouTubeSource typerecorded talk or interview

Coding as the floor. Sarah Khalid, an FDE Director at Salesforce, said in Salesforce’s newsroom in March 2026 that coding is “table stakes” for the role, and, recalling one insurance engagement, that the work there was more judgment, trust and communication than coding. Source 21How Forward Deployed Engineers Are Proving AI Makes Tech Jobs More HumanPublisherSalesforce NewsroomSource typecompany blog Our short version: coding gets you in, and judgment does the job. The Engineering Leadership newsletter reported, in August 2026, from a conversation with OpenAI’s Colin Jarvis, that OpenAI wants FDEs who are strong software engineers and also good communicators. Source 22Inside OpenAI's Forward Deployed Engineer RolePublisherEngineering Leadership (Gregor Ojstersek)Source typenews report Kevin Bai, on Anthropic’s applied AI team, described an FDE at the AI Engineer World’s Fair 2026 as someone you would hire as a software engineer who you would also trust in front of a customer; he said he was giving a general view, not Anthropic’s hiring criteria. Source 23Forward Deployed Engineering 101 (Kevin Bai, Member of Technical Staff, Anthropic; AI Engineer World's Fair 2026)PublisherAI EngineerSource typerecorded talk or interview

Depth in the employer’s own stack. At a data platform company, the posted requirements can include the platform itself, not only general coding. As of September 2026, Databricks’ US Sr. FDE postings ask for deep Apache Spark experience, including knowledge of Spark runtime internals. Source 24Sr. Forward Deployed Engineer (FDE) - Financial Services (New York City)PublisherDatabricks (careers site / Greenhouse)Source typecompany job posting Our advice, if you are a data or backend engineer aiming there: be ready to explain how a Spark job runs, as well as to code.

The dissent. One commenter on Blind wrote, in April 2026, that Palantir’s FDE loop is less technically deep than the SWE loop “since you’re mostly building on top of Foundry”. Source 25Palantir FDE interview process (Blind)PublisherBlindSource typecandidate report on Blind The commenter does not say they went through the loop, so treat it as one opinion.

The employers quoted here describe the technical bar as shared or as the floor. Our reading is that the FDE loop adds a second bar on top, and our Pro lesson on the double bar is built around that idea. Whether a particular FDE job is a step down is a narrower question, and our post is FDE a step down from software engineering? weighs the hiring-bar evidence for it.

Clear the coding bar, then think like the customer

Prepare coding as if you were applying for a software engineering job, because the customer rounds sit on top of it, not in place of it. Ramp’s blog, quoted above, treats coding as a bar to pass rather than a score to maximize. Source 18Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog In the room, we read that as: reach clean, correct code in the time, then spend any spare minutes on the edge cases the customer’s real data would hit, rather than on a cleverer algorithm. Our free lesson on what FDE coding rounds test sorts the evidence by company.

What each role is measured on

Titles blur and loops overlap, but what counts as success on the job is different. This is where the two jobs part ways.

The FDE: the customer’s outcome

Employers who describe how FDE success is judged put the customer’s result first:

The SWE: the capability, for everyone

Palantir puts its Devs in Product Development, and, as its line at the top of this guide says, a Dev’s work is one capability for many customers. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 3A Day in the Life of a Palantir Forward Deployed Software EngineerPublisherPalantir BlogSource typecompany blogSource 6Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring page In our reading, a product engineer’s win is a capability that works for the whole customer base, and no single customer’s bad week decides whether it succeeded. The success signal is a number the product team owns across every tenant, such as the feature’s error rate or its weekly use, moving the right way.

The loop back to the product

The best FDE work does not stay with one customer. The Pragmatic Engineer names and among the jobs close to FDE, and said in an August 2025 article that the difference is that FDEs also contribute to the product their company sells. Source 29Forward Deployed Engineers (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report Ramp’s Core FDE posting says FDEs drive the core product roadmap, deciding when to build a custom solution and when to speed up a broader initiative. Source 10Software Engineer, Forward Deployed @ RampPublisherRamp (Ashby job board)Source typecompany job posting Vinoo Ganesh, who led Palantir’s rotation that turned software engineers into FDEs, wrote in Latent Space in September 2026 that the engineers who mattered were those who came back and changed what was built, not those who shipped the most for customers. Source 30The Rise of the Forward Deployed Engineer — and How To Do the Job RightPublisherLatent SpaceSource typenews report

Our practice question custom build or product change? drills that call.

The same request, at an AI lab

The hospital scenario above is enterprise work. Here is the same split at an AI lab or an AI product company, again as a scenario of our own. A retailer that runs a support agent on your platform says, “Your agent gives wrong refund answers.”

  • The product engineer on the agent platform asks whether refund answers are wrong for every tenant. They look at tool calling and retrieval quality across customers, improve ranking for everyone, and ship it in the next release. Every tenant gets a little better, and this retailer waits.
  • The FDE pulls last week’s real transcripts where a shopper asked about a refund, and turns each one into a test case: the question, and the policy fact a correct answer has to state. Running them shows the failures cluster on one topic, gift cards. The retailer’s gift-card policy lives in a document the ingestion job skipped, so retrieval never finds it and the agent guesses. The FDE gets the document indexed with the retailer’s support team, reruns the cases, and makes the case set a gate that every prompt or model change must pass. Then they send the failure class, policy documents silently skipped at ingestion, to the product team.

Here is the core of that harness, cut down to two cases. It runs as written and prints 1/2 pass; failing: ['Refund to a gift card?']:

# Each real transcript becomes a test case: the question, and the policy
# fact a correct answer has to state.
cases = [
    {"q": "Can I return opened headphones?", "must": "30 days"},
    {"q": "Refund to a gift card?", "must": "store credit"},
]

def agent(question):
    # Stand-in for the retailer's agent. The gift-card policy is missing
    # from what retrieval returns, so the agent guesses.
    if "headphones" in question:
        return "Yes, opened headphones can be returned within 30 days."
    return "Refunds go back to your original payment method."

def run(cases):
    failing = [c["q"] for c in cases if c["must"].lower() not in agent(c["q"]).lower()]
    print(f"{len(cases) - len(failing)}/{len(cases)} pass; failing: {failing}")
    return not failing  # gate a release on this being True

run(cases)

A substring check is crude; a real harness adds a grader for answers that state the fact in other words. The point is the order of work: the FDE starts from this customer’s failures, not from the model.

The words to say, in the interview or on the customer call:

“Before I touch the prompt, I’d turn last week’s wrong answers into test cases, each with the fact a right answer must contain. Then we’ll know whether it’s retrieval, the policy text or the model, and we’ll know when it’s fixed.”

OpenAI’s San Francisco FDE posting names eval-driven feedback that changes product and model roadmaps as one way FDEs measure success. Source 26Forward Deployed Engineer (FDE) - SFPublisherOpenAI CareersSource typecompany job posting In this scenario, that is the case set and the failure class you send back. Two free questions practice it: design an eval harness for a support agent, and how do you know your AI system works?, which asks you to say it to a customer. For the rest of the AI-lab picture, our post FDE vs AI engineer sets the two jobs side by side.

What the week looks like

In a 2019 post, Palantir’s blog quoted two Deltas. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog Dyon, in Abu Dhabi, said that most weeks they spent a couple of days at the customer’s premises, some of it in meetings with technical or business stakeholders and the rest monitoring, debugging, deploying or configuring the software. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog G.M., in São Paulo, said some weeks go mostly to developing and reviewing the team’s code, and others mostly to scoping a project with a client or working with users. Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blog

Travel is the line in an FDE posting you should check before you apply. As of September 2026, Palantir’s FDSE posting asks for the ability and interest to travel up to 25%, flexible based on personal preferences. Source 5Palantir Technologies - Forward Deployed Software Engineer (New York, NY)PublisherPalantir (Lever job board)Source typecompany job postingSource 8Palantir Technologies - Deployment Strategist (New York, NY)PublisherPalantir (Lever job board)Source typecompany job posting OpenAI’s San Francisco FDE posting requires travel of up to 50%. Source 31Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job posting Anthropic’s FDE posting estimates 25% travel. Source 32Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting The range is wider than those three suggest. Palantir’s London posting for a Forward Deployed Software Engineer on its NATO work asks for the ability to travel throughout Europe 70 to 90% of the time. Source 33Forward Deployed Software Engineer - NATO (London) - Palantir on LeverPublisherPalantir Technologies (Lever)Source typecompany job posting Most of Databricks’ standard FDE postings say travel to customers 20% of the time. Source 24Sr. Forward Deployed Engineer (FDE) - Financial Services (New York City)PublisherDatabricks (careers site / Greenhouse)Source typecompany job postingSource 34Sr. Forward Deployed Engineer (FDE) - Digital Native Business (San Francisco)PublisherDatabricks (careers site / Greenhouse)Source typecompany job posting Decide what you can live with before the recruiter asks, and read the travel line in every posting you apply to.

Is an FDE paid more than a software engineer?

Start with what employers post. As of September 2026, OpenAI’s Forward Deployed Software Engineer posting in San Francisco lists a salary range of $185K to $325K and says it offers equity. Source 13Forward Deployed Software Engineer - SF (Ashby)PublisherOpenAI (Ashby job board)Source typecompany job postingSource 14Forward Deployed Software Engineer - NYC (Ashby)PublisherOpenAI (Ashby job board)Source typecompany job postingSource 35Forward Deployed Software Engineer - Seattle (Ashby)PublisherOpenAI (Ashby job board)Source typecompany job posting Also as of September 2026, Palantir’s New York FDSE posting lists a salary range of $135,000 to $200,000 a year, and says total compensation may also include RSUs and a sign-on bonus. Source 5Palantir Technologies - Forward Deployed Software Engineer (New York, NY)PublisherPalantir (Lever job board)Source typecompany job posting Neither posting sets a software engineer range beside it, so a posted FDE range on its own does not answer the question.

Recruiters do not agree either. Two posters on Blind wrote, in June 2026, that Google recruiters had told them different things: one was told regular SWEs and FDEs are on the same pay bands, and doubted it, while the other, who had not yet interviewed, was told FDE pay can be higher than SWE at the same level because of market demand and customer-facing scope. Source 36Google L5 Offer Ridiciously Low? - BlindPublisherBlindSource typecandidate report on BlindSource 37Google Cloud FDE role - BlindPublisherBlindSource typecandidate report on Blind So ask the recruiter which level and band the FDE offer maps to, and compare it with the SWE band at that level.

For the numbers, the FDE salary guide sets out the bands employers post and what the H-1B filings show, with the dates and limits of each.

How the interviews differ

Start with the one employer that says so in writing. Palantir’s careers site says its engineering interview process varies by whether you are going for Forward-Deployed Software Engineer or Software Engineer. Source 6Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring page It structures the process around engineering competencies and publishes guides on writing good code, analyzing the efficiency of code, navigating open-ended questions, solving technical problems and working inside existing systems. Source 38Getting Hired - Palantir CareersPublisherPalantir TechnologiesSource typecompany hiring page

No employer publishes how its rounds are weighted or how many candidates pass. What you can compare is what each company says it looks for, and what candidates report.

What employers and their recruiters say

  • Open-ended problems. Palantir’s guide to open-ended questions tells candidates to state alternatives and trade-offs but reach a concrete approach, delivering a functioning idea first and expanding it afterwards. Source 39Navigating Open-Ended Questions - Palantir CareersPublisherPalantir TechnologiesSource typecompany hiring page Shilpa Balaji, who joined Palantir as an FDE and went on to lead its FDE recruiting, told First Round Review in February 2026 that many of Palantir’s FDE interview questions were oriented around high-level problem solving on customer problems rather than Google-style coding tests, Source 19So You Want to Hire a Forward Deployed EngineerPublisherFirst Round ReviewSource typenews report and gave as her example explaining insider trading to a candidate and asking them to design a solution, including what data they would need and what they would ask the customer. Source 19So You Want to Hire a Forward Deployed EngineerPublisherFirst Round ReviewSource typenews report
  • Leading a customer meeting. Ramp’s blog names four axes for judging FDE candidates: drive and work ethic, engineering fundamentals, customer empathy and great communication. Source 18Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog It describes the communication it wants as clear enough that the author would be excited to have the candidate lead a meeting with a customer. Source 18Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog
  • Choosing between the two roles. Ramp’s Leo Mehr said that asking candidates what they are excited about is one way Ramp decides whether someone suits FDE or another engineering role. Source 4What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interview

What candidates report

The rounds, side by side

This is our reading of the evidence above, not any employer’s rubric.

RoundWhat a SWE loop checksWhat the FDE version adds
CodingCorrect, efficient codeA problem framed as a customer scenario
DesignA system that scalesA system for one customer’s constraints
Open-endedDepends on the employerA vague problem to scope and cut down
CustomerDepends on the employerLeading a conversation, saying no
BehavioralOwnership, conflictOwnership of someone else’s outcome

In our view, the open-ended row is the one a software engineering job trains least, because a product team rarely hands an engineer a problem with no scope at all. Our decomposition method is built for that round. One caution if you are applying to Palantir as a software engineer: the guide on navigating open-ended questions sits on Palantir’s Getting Hired page, which speaks to engineers in general rather than to one role. The page says that because there are many kinds of engineers, the company structured its interview process around the engineering competencies it values most. Source 38Getting Hired - Palantir CareersPublisherPalantir TechnologiesSource typecompany hiring page Our advice is to prepare for open-ended questions there whichever role you apply for.

One prompt, two instincts

Take the insider-trading prompt above. The two answers below are ours, written to show the difference; they are not transcripts of anyone’s interview.

The product-engineer default opens with architecture: a streaming anomaly-detection pipeline over every trade, with a model scoring each one. It is a sound system, and it answers a question nobody has asked yet. Strong software engineers ask about users too; the difference is which question they ask first.

The FDE default opens with a person: “Who acts on an alert? If it’s a compliance analyst, how many cases can they review in a day?” If the answer is about twenty, a first version that flags thousands of trades is useless. So it starts small:

  1. Join trades to the employee roster.
  2. Join those to the earnings-announcement calendar.
  3. Flag employee trades inside a window before an announcement, and send them to the analyst’s review queue.

That is a query and a queue, not a model, and an analyst can use it this week. Here is the query, in SQLite, with the three tables it needs and a small test set. Of the three test trades, it returns one: an employee’s buy in the days before that company’s announcement.

CREATE TABLE trades    (trade_id INT, account_id TEXT, ticker TEXT, side TEXT, qty INT, traded_at DATE);
CREATE TABLE employees (employee_id TEXT, name TEXT, account_id TEXT);
CREATE TABLE earnings  (ticker TEXT, announced_at DATE);

INSERT INTO employees VALUES ('E1', 'Ana', 'A-100'), ('E2', 'Ben', 'A-200');
INSERT INTO earnings  VALUES ('ACME', '2026-03-20'), ('GLOBEX', '2026-04-15');
INSERT INTO trades    VALUES
  (1, 'A-100', 'ACME',   'BUY',  500, '2026-03-14'),  -- employee, 6 days before
  (2, 'A-200', 'GLOBEX', 'SELL', 200, '2026-03-01'),  -- employee, outside the window
  (3, 'C-900', 'ACME',   'BUY',  900, '2026-03-18');  -- not an employee account

-- Employee trades in the 14 days before an earnings announcement
SELECT e.name, t.ticker, t.side, t.qty, t.traded_at, x.announced_at,
       julianday(x.announced_at) - julianday(t.traded_at) AS days_before
FROM trades t
JOIN employees e ON e.account_id = t.account_id
JOIN earnings  x ON x.ticker = t.ticker
WHERE t.traded_at >= date(x.announced_at, '-14 days')
  AND t.traded_at <  x.announced_at
ORDER BY days_before;

-- name | ticker | side | qty | traded_at  | announced_at | days_before
-- Ana  | ACME   | BUY  | 500 | 2026-03-14 | 2026-03-20   | 6.0

The window in that query is a number to confirm with compliance, not a fact; say that out loud. The answer then names what the first version misses and how you would know it works, in words like these:

“This misses trades through relatives’ accounts and anything outside the window, so I’d tell compliance that on day one. I’d know it’s working if analysts escalate a meaningful share of what we flag, not just close them.”

It closes with what to ask the customer next: who counts as an insider (employees only, or family members and contractors too?), and what a closed case looks like, so the next version can learn from the analyst’s decisions.

Both candidates can code. The second one fitted the problem to the customer before building. In our reading, that is also what Palantir’s open-ended guide asks for: a concrete approach and a functioning idea first. Source 39Navigating Open-Ended Questions - Palantir CareersPublisherPalantir TechnologiesSource typecompany hiring page

What to say, round by round

In the coding round, get to a working solution and state its complexity first. Only then add one line that shows you think about the customer’s real input:

“This sorts first, so it’s O(n log n); a hash set makes it O(n) time for O(n) memory, so I’ll switch to that. Before I tune further: how big does the real input get? If it’s a nightly file of a few thousand rows, speed is fine and the risk is malformed rows, so I’d add a test for a blank ID and a duplicate that differs only in case.”

In the open-ended round, ask about the user before the data. A line that works:

“Who opens this first thing in the morning, and what do they do differently if it’s right? That tells me what the first version has to get right, and what can wait.”

In the customer round, show you can hold scope without losing the customer:

“I can get you the export by Friday. The dashboard needs the data cleaned first, so here is what I’d do this week and what it unblocks next week.”

In the “why FDE?” question, answer with the unit of work, not your personality. Here is the shape, with brackets for your own details:

“For [three years] I built [billing] features every customer got. The week I’m proudest of was inside one [logistics] customer’s data, finding why their [invoices double-counted returns] and shipping the fix, then getting it into the product. I want that week to be the job, not the exception.”

A generic version (“I like working with people”) invites the harder follow-up, “why not product engineering?”, and our post on answering ‘why FDE?’ so it survives the follow-ups walks through them. Our free lesson on the bridge story shows how to find your week, and the free question why FDE and not software engineering? has the structure, the follow-ups and a model answer.

What FDE hiring leaders say goes wrong, and how it shows in a loop

Hiring leaders described the first four patterns, in the job or in who they hire; a candidate reported the fifth. Each comes with how it shows up in an interview and the fix we teach.

Polishing the abstraction. In remarks reported by Y Combinator’s Lightcone podcast in September 2025, Bob McGrew, introduced as an early Palantir executive, said that for Deltas you want someone who is really good at prototyping, and that the wrong profile is a craftsman who loves getting the abstractions exactly right. Source 46The FDE Playbook for AI Startups with Bob McGrew (YouTube auto-generated English captions)PublisherY Combinator, YouTubeSource typerecorded talk or interview In a loop, it shows as a long stretch of class design before anything runs. The fix: in an open-ended round, build the ugliest thing that answers the customer’s question first, then say out loud what you would clean up and when.

Loving what you built. Colin Jarvis, who leads forward deployed engineering at OpenAI, named as a failure pattern people who come to love the form of what they built more than its function, and said the best FDEs will tear a solution up when users do not use it. Source 9The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview In a loop, it shows when an interviewer says users ignored what you built and you defend the design instead of asking why. The fix: bring one story where you threw your own work away because of what users did. The question on a time you threw away something you built because it was not delivering value asks for exactly that.

Taking the stated scope at face value. Jarvis was quoted in The Pragmatic Engineer, in August 2025, as saying that what customers describe in scoping often does not match the data and system reality, so the team moves fast and re-scopes to the most useful thing it can do. Source 29Forward Deployed Engineers (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report Ramp’s Leo Mehr said at an AI Engineer talk that when a sales rep urgently demands an integration, a well-trained FDE pauses to ask what is driving the urgency, who will use it and whether the workarounds are exhausted. Source 47How Forward Deployed Engineering is done at Ramp — Leo Mehr (YouTube auto-generated English captions)PublisherAI Engineer, YouTubeSource typerecorded talk or interview In a loop, it shows as building exactly what the prompt or the role-played customer asked for. The fix: in any round with a customer in it, ask one “why now?” question before you design anything.

Arriving with a playbook. Shilpa Balaji, the former Palantir FDE recruiting lead, told First Round Review that a candidate who came in overly dogmatic or set in their ways was a red flag, and gave as her example people who had spent more than 10 years at a FAANG company, who were in the “no fly zone”. Source 19So You Want to Hire a Forward Deployed EngineerPublisherFirst Round ReviewSource typenews report In a loop, it shows as “at my last company we did it this way” offered as the answer rather than as one option. The fix: when you describe how you would approach a problem, name the assumption you would test first, and what you would do if it turned out wrong.

Leaning on communication to carry the coding. This one runs the other way. One candidate reported on Reddit, in June 2026, that with 3 years of experience, two as a software engineer at a bank and one as an FDE at a small company, they had reached 4 final rounds while job hunting mostly in the FDE space, and that all four gave the same feedback: a great communicator, but technical skills not what the companies were looking for; they added that in some cases it seemed to be a mismatch with the specific domains the companies wanted. Source 48Good communicator, but technical skills not up to par; pivot options? (post by u/calculusbitch99)PublisherReddit r/cscareerquestionsSource typecandidate report on Reddit The poster did not name the companies or the roles. The fix: prepare the coding rounds as if the job were SWE, as the section on the SWE bar sets out.

Which one fits you

This self-check is ours, not an employer’s. Answer each question with an example from the last year of your work, not a preference.

FDE or SWE: a self-check

  • When a customer reported a problem, did you want to be on the call, or did you want the ticket?
  • Have you shipped something ugly that solved one user’s problem, and felt fine about it?
  • Can you name a time you changed what you were building because of what a user did, not what they said?
  • Would you rather know one codebase deeply, or learn a new customer’s stack every few months?
  • Does the travel line in the postings you are reading fit your life for the next two years?
  • When you picture a good week, is it a merged design you are proud of, or a customer who stopped needing a workaround?

If most of your examples point at the customer, that is the signal Ramp’s Leo Mehr says predicts FDE fit: software engineers who say they want to be closer to customers or users. Source 4What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interview If your examples point at the codebase, a product engineering role may suit you better, and that is a real answer, not a failure.

Moving between the two

The move is not one-way, and it is not new.

  • SWE to FDE. Vinoo Ganesh wrote in Latent Space that he led Palantir’s Project Frontline, the rotation that took software engineers and turned them into forward deployed engineers, and that about 250 people went through it. Source 30The Rise of the Forward Deployed Engineer — and How To Do the Job RightPublisherLatent SpaceSource typenews report Recruiters sometimes make the move for you: one poster on Blind reported, in July 2026, that after a strong technical screen for an OpenAI backend software engineer position, the recruiter said the position was filled and suggested the FDE role. Source 49OpenAI Forward Deployed Engineer vs Backend Software EngineerPublisherBlind (teamblind.com)Source typecandidate report on Blind
  • FDE to SWE. The Pragmatic Engineer reported, in August 2025, that until about 2016 Palantir had more FDEs than regular software engineers, and that after Foundry launched that year more FDEs moved back into software engineering. Source 29Forward Deployed Engineers (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report

Whichever way you move, the interview will ask why. For a software engineer applying to FDE roles, your strongest material is the part of your current job that already looks like forward deployed work: the integration you owned for one big customer, the week you spent on their side of the firewall, the fix you shipped for them and then pushed into the product. Our post on moving from software engineer to forward deployed engineer sorts what transfers from what does not, and the free lesson on the bridge story shows how to shape it into a short answer.

Practice the difference out loud

Reading the difference is not the same as saying it under a follow-up. Three questions test it directly:

The first one is the place to start. The first two are free, model answers included, and every one of the site’s 180 practice questions shows its framework free.

To feel the customer half of the job, run the free practice case. It puts you in front of an AI customer with a vague problem on a 10-minute clock, and it is free once you sign in.

For the rest of this topic, here is what Pro adds. The model answers to coding with vague requirements and custom build or product change?, the lesson on the double bar this guide leans on, and the Pro practice cases, moving analytics to a new data platform and claim intake on a model the insurer already bought. Pro starts with a 7-day free trial. The pricing page has the plans.

For the other neighbors of the role, see FDE vs solutions architect and FDE vs sales engineer. For the whole loop, round by round, see the FDE interview guide.

Start now: say your answer to why FDE and not software engineering? out loud, then compare it with the free framework and model answer.

GlossaryForward deployed software engineerPalantir’s title for its FDE role, called Delta internally; OpenAI and EY also post FDSE titles, each with its own duties.More on Forward deployed software engineerGlossaryForward deployed engineerA software engineer who builds and ships production systems inside a customer’s problem and environment, accountable to that customer’s outcome.More on Forward deployed engineerGlossaryDeployment strategistA customer-facing role that works out the customer’s questions and scope beside FDEs; at some employers the title means a product-manager or quota-carrying role instead.More on Deployment strategistGlossaryAgentA system in which a model chooses steps and tool calls to complete a task, within limits the design sets.More on AgentGlossarySolutions architectA customer-facing technical role that designs, advises and often builds proofs of concept; postings place it before the sale, after it, or both.More on Solutions architectGlossarySales engineerA technical role on or beside a sales team that helps win deals with demos and proofs of concept; the U.S. Bureau of Labor Statistics says employers usually pay it salary plus commissions or bonuses.More on Sales engineerGlossaryDecomposition roundAn open-ended interview in which you work out loud from a vague problem with several possible solutions to a concrete approach and a first working version.More on Decomposition round

Posts on this topic

Each takes one part of this guide further.

  1. The FDE role

    FDE vs AI engineer: same models, different job

    Both build with LLMs, but only one works inside the customer’s systems. How FDE and AI engineer postings differ, side by side, and how to choose.

    11 min readPublished

Questions people ask

Is a forward deployed engineer a software engineer?

Yes, by the employers’ own titles. Palantir’s role is the Forward Deployed Software Engineer, and Ramp posts its role as Software Engineer, Forward Deployed. What changes is the scope: Palantir describes a Dev’s focus as one capability, many customers, and a Delta’s focus as one customer, many capabilities.Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 3A Day in the Life of a Palantir Forward Deployed Software EngineerPublisherPalantir BlogSource typecompany blogSource 10Software Engineer, Forward Deployed @ RampPublisherRamp (Ashby job board)Source typecompany job posting

What is the difference between a Dev and a Delta at Palantir?

Palantir calls its software engineers Devs and its forward deployed software engineers Deltas. Its careers page puts Deltas in Business Development, with a mandate to achieve technical and operational outcomes for customers, and Devs in Product Development.Source 2Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 6Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring page

Is the FDE interview easier than the software engineer interview?

Not by what employers say on the record. Ramp’s Director of Engineering has said FDE candidates at Ramp must pass the software engineering interview loop. Palantir’s careers site says its engineering interview process varies by whether you apply for FDSE or Software Engineer. No employer publishes a pass rate for either loop, so ask the recruiter which rounds the two roles share.Source 4What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interviewSource 6Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring page

Do forward deployed engineers write production code?

In OpenAI’s and Anthropic’s postings, yes. OpenAI’s FDE posting asks for people who write and review production-grade code, and Anthropic’s asks FDEs to build production applications with Claude inside customer systems. Read each posting for what you will build and where it runs, because some roles with the title are closer to implementation or pre-sales work.Source 31Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job postingSource 32Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting

What have posters on Blind said about FDE vs SWE pay?

Recruiters give different answers. Two posters on Blind wrote, in June 2026, that Google recruiters had told them different things: one was told regular software engineers and FDEs are on the same pay bands, and doubted it; the other, who had not yet interviewed, was told FDE pay can be higher than software engineer pay at the same level because of market demand and customer-facing scope. Ask the recruiter which level and band the FDE offer maps to.Source 36Google L5 Offer Ridiciously Low? - BlindPublisherBlindSource typecandidate report on BlindSource 37Google Cloud FDE role - BlindPublisherBlindSource typecandidate report on Blind

How much do forward deployed engineers travel?

It depends on the posting. As of September 2026, Palantir’s FDSE posting asks for the ability and interest to travel up to 25%, OpenAI’s San Francisco FDE posting requires travel of up to 50%, and Anthropic’s FDE posting estimates 25%.Source 5Palantir Technologies - Forward Deployed Software Engineer (New York, NY)PublisherPalantir (Lever job board)Source typecompany job postingSource 8Palantir Technologies - Deployment Strategist (New York, NY)PublisherPalantir (Lever job board)Source typecompany job postingSource 31Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job postingSource 32Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting

Can a software engineer switch to an FDE role?

Yes, and some employers look for that motive. Ramp’s Director of Engineering has said that software engineers who say they want to be closer to customers or users are a great predictor of FDE fit. Prepare for the rounds a software engineering job does not train: open-ended problems and customer conversations.Source 4What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interview

What does FDSE stand for?

Forward deployed software engineer. It is Palantir’s title for the role, and Palantir’s posting says the company pioneered the position. Other employers shorten it to FDE or put forward deployed after a software engineer title.Source 5Palantir Technologies - Forward Deployed Software Engineer (New York, NY)PublisherPalantir (Lever job board)Source typecompany job postingSource 10Software Engineer, Forward Deployed @ RampPublisherRamp (Ashby job board)Source typecompany job posting

Keep reading

Guides

Lessons

Questions