As of September 2026, Palantir’s application for its New Grad role asks you to confirm you want it “as opposed to Software Engineer”. Source 1Apply: Forward Deployed Software Engineer, New Grad - Commercial (New York, NY) - Palantir on LeverPublisherPalantir Technologies (Lever)Source typecompany job posting Leo Mehr, Director of Engineering at Ramp, said on dearCC in June 2026 that asking candidates what excites them is one way Ramp decides between and another engineering role. Source 2What 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 So treat “why FDE?” as a routing question: Palantir makes you pick the role before you meet anyone, and at Ramp what you say excites you helps place you. You will leave with a two-minute , a three-sentence answer, and senior and staff versions.

What hiring leaders say predicts a good FDE

No employer publishes a scoring rubric for motivation, and nothing below is one. We suggest an answer that carries two signals.

Show only the first and it can read as leaving engineering. Carry both, and let each company’s words set which leads: Mehr’s Ramp blog post puts drive, communication and the will to solve customer problems end to end ahead of “technical perfection”. Source 4Forward Deployed Engineering (Leo Mehr, Director, Engineering)PublisherRamp Builders (engineering blog)Source typecompany blog

Evidence you already have

You do not need a customer-facing title. Ruth Hickin, a Salesforce vice president, said in March 2026 that for its FDEs it’s “curiosity over credentials”, and the most important thing is whether you can solve a customer’s problem. Source 5How Forward Deployed Engineers Are Proving AI Makes Tech Jobs More HumanPublisherSalesforce NewsroomSource typecompany blog

List recent work like this, strongest first:

  • An integration you built for one named customer, with their engineers.
  • A customer’s production problem you diagnosed on a call and fixed.
  • An internal tool that changed how a team outside engineering works.
  • A pilot you took from a vague request to daily use.

Tell only the top one. A finance, support or operations team counts as a customer if you sat with them yourself; a PM handing you requirements does not.

Teaching, founding and a first career

Teaching. Tell the stuck student, not “I was a TA”: “A student failed the same pointer lab twice; I stopped re-explaining, watched him debug, and saw he never read the compiler warnings.” Mehr’s Ramp post says instructors and teaching assistants who “actually enjoyed it” have “the ability and interest to do this well”, meaning customer work. Source 4Forward Deployed Engineering (Leo Mehr, Director, Engineering)PublisherRamp Builders (engineering blog)Source typecompany blog

Founding. Tell it as a customer story, failed or not: who paid, and for what. “We had three pilots and one paying customer, who paid for a report we built in a week, not the product we pitched.” Colin Jarvis, who leads forward deployed engineering at OpenAI, said in May 2026 that its FDE team includes a lot of ex-founders, and that what its varied hires share is being very outcome focused. Source 6The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview

A different first career. The bridge is why you left: “As a process chemist, I wrote the Python the plant engineers ran every shift, and I wanted that to be the job.” Palantir’s Chief Architect, Akshay Krishnaswamy, said in January 2026 that one standout FDE archetype comes from another field, such as physics, with a reason for wanting this work and “a bit of a chip on the shoulder.” Source 7How Palantir Scaled: Why the Best Software Is Built Backwards (YouTube auto-generated English captions)Publishera16z Deep Dives, YouTubeSource typerecorded talk or interview

The shape of a bridge story

The structure is ours, not an employer’s rubric.

  1. Where you were. Your role and system, in one sentence.
  2. One customer. A person or team, and their problem in their words: “the head of claims operations”, not “stakeholders”.
  3. Asked versus needed. The request as it reached you, and what you saw in their workflow that changed it. This beat makes the story FDE-shaped.
  4. What you built. One thing, plus a detail only the builder would know: the , the schema you reverse-engineered.
  5. What changed. For them, and who noticed: before and after in their unit, such as days to close, as the question page’s model answer does. The examples here leave it out.
  6. The turn. What that work taught you about the job you want next.

Filled in, for a fictional engineer:

Where you were. I was a backend engineer on the billing platform at a company selling dispatch software to trucking fleets.

One customer. Our biggest customer’s controller said her team’s month-end hand-matching of our invoices against their ERP made their close run late.

Asked versus needed. The request was a CSV export. I spent an afternoon watching her team and saw they matched on their purchase-order number, which our invoices didn’t carry, so an export would have moved the manual work, not removed it.

What you built. I added the PO number at order entry and built a nightly sync into their ERP’s API, upserting with our invoice ID as the ERP’s external ID, so a rerun could never post an invoice twice.

What changed. Her team stopped the month-end reconciliation, and the controller dropped us from her list of reasons the close ran late.

The turn. The afternoon in their office decided what I built, and that is the work I want more of.

The same work, beats stripped out:

I collaborated with stakeholders on an ERP integration that improved the customer’s finance workflow.

No person, no asked versus needed, no builder’s detail, nothing anyone noticed.

The same beats, for an AI deployment:

I was a platform engineer at a company selling claims software to insurers. The head of claims operations asked for a chatbot for her adjusters. Sitting with them, I saw their time went into finding the policy clause that applied; a chatbot in another window would add a step. I built clause retrieval into the claim screen, with an evaluation set of real adjuster questions their senior adjuster graded; the set blocked a release when a chunking change started citing the wrong endorsement. The adjusters dropped their clause cheat sheets, and that is the work I want more of.

The same shape at senior or staff level

A senior story shows you owned an outcome, not just the code. As of September 2026, Okta’s Principal FDE posting draws the line: a Senior FDE owns the outcome inside one account, and the Principal owns the patterns every account and every FDE inherits, while still writing code. Source 8Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOktaSource typecompany job posting

At senior level, the first story adds its last mile: “I ran the rollout. I walked her accounts payable lead through the exception list, carried the sync’s on-call through its first close, and handed her IT team the runbook.” At staff or principal level, the beats scale up. Four years later:

Several customers. Three of our trucking customers each asked for an invoice export to a different ERP.

Asked versus needed. I sat with all three finance teams and found they reconciled on the same field, the PO number, so I built one connector framework instead of three exports.

The design. Every connector upserted on our invoice ID, failed runs went to a replay tool, and none shipped without a reconciliation report the customer could check.

What changed. Two engineers built the next four connectors from it without me, and all three finance teams stopped matching by hand.

The turn. I want the job where finding that pattern is the work, and I answer for the customers who get it first.

The short ‘why FDE’ answer, built from the story

Use three sentences: the part you want more of; why that part is the whole job in an FDE role and a side task in a product role; and the cost you accept, such as a less predictable week or travel. For the first story:

The work I did best was that afternoon with the controller and the sync that followed: learning how a customer actually runs, then building what fits. On a product team that happened when a big customer escalated, and then I went back to the roadmap. I want that to be the job, and I accept the cost: less depth in one codebase, and weeks inside systems I don’t control.

Lead with the three sentences, then stop; give the story if asked. In a July 2025 Palantir video for software engineering candidates, a hiring manager said, “We don’t necessarily want to hear your sort of prepared statement of what you think we want to hear.” Source 9From Code to Career: Meet Palantir's Hiring Managers (YouTube uploaded English captions)PublisherPalantir, YouTubeSource typerecorded talk or interview Learn the beats; say them fresh.

The same Palantir application also asks for “a time you changed your mind about something”, in 150 words at most. Source 1Apply: Forward Deployed Software Engineer, New Grad - Commercial (New York, NY) - Palantir on LeverPublisherPalantir Technologies (Lever)Source typecompany job posting Beat three is that story: the CSV export, until the afternoon with the controller’s team. Tell beats two to five.

Reasons that collapse under follow-ups

Each breaks on the first push.

  • “I like working with people.” Breaks on “Product engineers talk to users too.” Say: “I want to watch how a customer’s team works, then change the code that week.”
  • “I want variety.” Breaks on “What will you miss from building one product in depth?” Say: “I want one customer’s result to be mine, from their data to the rollout.”
  • “I want to work on your models.” Breaks on “Would you take a software engineering role here instead?” It picks a company, not a role. The exchange below answers it.
  • “I want less infrastructure.” Breaks on “Which part of the engineering do you expect someone else to do?” It makes FDE the lighter job. Say: “Their data, their systems, and my code running in them.”
  • “I want to found a company.” Breaks on “So this is a stop on the way?” Say: “Before anything of my own, I want to have shipped for customers like yours.”
  • “I want my work to reach more users.” Breaks on “Why not staff engineer on the platform team?” The senior trap: scale alone fits a platform role too. Say: “The platform work I’m proudest of started as one customer’s fix.”

Interviewer: If we offered you a software engineering role here instead, would you take it?

Candidate: I’d rather not, because I’m choosing the work, not just the company. I was good at roadmap work, and I still volunteered for every big customer’s escalation; that is how I ended up in the controller’s office. I’d rather do that on purpose, and here that is the FDE job.

It answers straight, names the work, and returns to the story.

Rehearsing against the follow-ups

The practice question scripts its follow-ups, including travel. The travel lesson lists what to ask. Expect an engineer to probe what you built:

Interviewer: What happened when their ERP rejected an invoice halfway through the nightly run?

Candidate: The run kept going: each invoice was its own upsert, so one rejection didn’t block the rest. Rejected ones went to a table with the ERP’s error text, and her accounts payable lead got a morning list. Rerunning after a fix was safe, because the upsert keyed on our invoice ID. What I’d change: once her period closed, posted invoices were locked, so a price correction came back as a rejection. I’d send corrections as credit memos from day one.

One rehearsal round

  • Write the story as one line per beat, and the short answer as three sentences. At staff level, add the several-customer version.
  • Say both aloud against a two-minute timer. If you run long, cut the first beat, never the builder’s detail.
  • Answer each follow-up above aloud, without notes: go back to the story, say something a product engineer could not, and accept a cost.
  • Take an engineer’s two probes: a failure case, as above, and a design choice you would change.
  • End “Tell me about yourself” and “What customer-facing experience do you have?” with this story, changing only the last sentence.

That completes Module 0. Module 1 opens with the free lesson The evidence map. Pro opens the illustrative answers to the routing question itself, what you are most excited to work on, and to a “why this lab?” question.

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 engineerGlossaryBridge storyA short account that connects your past work to FDE work by naming a customer, what you built for them and what changed.More on Bridge storyGlossaryIdempotency keyA client-supplied identifier that lets a server apply a repeated request once, making retries safe.More on Idempotency key