The evidence map: what employers publish, what candidates report, how to read both

Three Palantir FDSE posters on Blind listed their rounds between February 2025 and May 2026, and no two named the same set. ^{[1, 2, 3]}Source 1Palantir FDSE virtual onsitePublisherBlind (teamblind.com)Source typecandidate report on BlindSource 2Palantir Forward Deployed Software EngineerPublisherBlind (teamblind.com)Source typecandidate report on BlindSource 3Palantir hm callPublisherBlind (teamblind.com)Source typecandidate report on Blind A plan built on a prep site’s loop diagram trains you for one loop, and it may not be yours. This lesson replaces it with a map of what employers publish, what candidates report and what nobody knows, added to your posting page. It follows the bridge story into what the loop checks. Examples span AI labs and AI products (OpenAI, Anthropic, Cognition, ElevenLabs, Scale AI), Google Cloud, and enterprise and data companies (Palantir, Databricks, C3 AI).

Three kinds of evidence

You will sort anything said about a loop into one of our three lanes; the lane tells you what to do.

In short: plan from published, practice from reported, and ask about unknown.

Your recruiter’s answer about your own loop beats all three: date it, keep the email, and put it at the top of your map.

A fourth source, leaders saying on the record what they hire for, describes people, not rounds; what hiring leaders say reads it.

Our guides to Google, Palantir, Databricks and OpenAI run this method; build your map first, then check it against ours.

Company-wide processes that include FDE hiring

You will pull tools, formats and warnings from pages that never say “FDE”.

All four pages cover every role, and none describes an FDE loop: they give you formats and tools. Google publishes that rubrics exist, not what they say. Some FDE postings add a step: as of September 2026, Cresta’s Senior FDE posting puts a self-paced CoderPad assessment first after résumé review, ^[8]Source 8Senior Forward Deployed Engineer (AI Agent)PublisherCresta (Greenhouse job board)Source typecompany job posting and Cloudflare’s FDE posting says offer-stage applicants may be asked to interview in person. ^[9]Source 9Forward Deployed Engineer (FDE)PublisherCloudflare (Greenhouse job board)Source typecompany job posting Copy such steps into your published lane verbatim.

The employers’ own warnings. OpenAI’s interview guide calls its process “an example”, ^[10]Source 10Interview Guide | OpenAIPublisherOpenAISource typecompany hiring page and says skills-based assessment formats vary by team and may include pair coding, take-home projects and technical tests. ^[10]Source 10Interview Guide | OpenAIPublisherOpenAISource typecompany hiring page Palantir says the number and format of interviews are personalized to your skills and the role. ^[7]Source 7Getting Hired - Palantir CareersPublisherPalantir TechnologiesSource typecompany hiring page So prepare round types, not a sequence.

The one process page that names the FDE role is for early careers. Palantir’s early-talent page says the process differs for Forward-Deployed Software Engineer, but not how. ^[11]Source 11Students | Palantir CareersPublisherPalantirSource typecompany hiring page Its timeline graphic, which names no role, ends with a virtual onsite of learning and decomposition interviews, then a hiring-manager interview and an offer. ^[11]Source 11Students | Palantir CareersPublisherPalantirSource typecompany hiring page

How to read a candidate report: who, when, which role

You will run five checks on any report before it goes on your map, each shown on a real report.

1. Had the round happened? One candidate wrote on Reddit, in July 2026, that after a Google FDE recruiter screen, the recruiter described their coming role-related knowledge round as one real-world business problem, designed in a Google Doc. ^{[12, 13]}Source 12Need help in preparation for Google Forward Deployed Engineer(FDE) interview (post by u/Wonderful-Ad6418)PublisherReddit r/leetcodeSource typecandidate report on RedditSource 13Need help in preparation for Google Forward Deployed Engineer(FDE) interview (comment by u/Wonderful-Ad6418)PublisherReddit r/leetcodeSource typecandidate report on Reddit They had not taken it, so label it “described before the round”.
2. When? One candidate’s report on Aced (formerly Exponent), for an entry-level (L3) Databricks FDE role, lists February 2026 as the interview month; it was posted in August 2026. ^[14]Source 14Databricks Forward Deployed Engineer Interview ExperiencePublisherAced (formerly Exponent)Source typecandidate’s personal write-up Date the interview, not the post. Our tie-break, not a finding: when reports disagree, list the newer interview first, and ask.
3. Which role, and who named it? In a Reddit thread titled “Palantir FDSE Technical Interview”, a commenter, in May 2026, described their loop without naming the company or the role. ^[15]Source 15Palantir FDSE Technical Interview (comment by u/MShakeed)PublisherReddit r/csMajorsSource typecandidate report on Reddit The thread title is someone else’s words.
4. The poster’s view, or the employer’s? A poster’s reason for a rejection is not the employer’s reason: one Palantir FDSE candidate on the Government track wrote, in December 2025, that “The rejection was not about technical ability but mission alignment.” ^[16]Source 16Palantir FDSE Full Interview Loop Process (post by u/Not_the_Sauron)PublisherReddit r/csMajorsSource typecandidate report on Reddit A poster’s rating of their own rounds is not feedback either.
5. Who is writing? A report on Aced is one candidate’s account, never “Aced says”. A prep-product blog is weaker: gaijineer.co, which promotes an interview-prep product, has an anonymous, possibly compiled write-up of a Cohere FDE loop; treat it as “a prep blog says”, not evidence. ^[17]Source 17Cohere Forward Deployed Engineer Interview ProcessPublishergaijineer.co (a blog that promotes the furustack interview-prep product)Source typeprep-product blog (anonymous, may be compiled) Count posters, not pages: one post quoted on several sites is one report.

Then label each report: checks one, three and five set the label; checks two and four decide what you write down.

The round types candidates report

You will list the round types your target’s reports mention. No two loops below match, but they draw on one short list.

The three Palantir FDSE posters on Blind named coding, decomposition and “Reengineering” for an onsite still to come in February 2025; a use case, learning or decomposition, and a hiring manager in June 2025; and coding, learning and decomposition in May 2026. ^{[1, 2, 3]}Source 1Palantir FDSE virtual onsitePublisherBlind (teamblind.com)Source typecandidate report on BlindSource 2Palantir Forward Deployed Software EngineerPublisherBlind (teamblind.com)Source typecandidate report on BlindSource 3Palantir hm callPublisherBlind (teamblind.com)Source typecandidate report on Blind

A customer can even sit inside a coding round: in a C3 AI Senior FDE thread, a commenter who did not name the company wrote, in September 2026, of a vague coding problem where they “had to dig and ask questions”. ^{[21, 22]}Source 21C3 AI Senior Forward Deployed Engineer (FDE) Interview Process – My Experience (comment by u/becquerwrecker)PublisherReddit r/OfferEngineeringSource typecandidate report on RedditSource 22C3 AI Senior Forward Deployed Engineer (FDE) Interview Process – My Experience (comment by u/becquerwrecker)PublisherReddit r/OfferEngineeringSource typecandidate report on Reddit

Where we teach each type:

How level shows up in reported loops

You will have your level answer ready before the first round: the format does not tell you the level, but in reported loops how the rounds go can change it.

A poster on Blind in India, with 10 years’ experience, wrote in May 2026 that the feedback on their Google FDE coding round was “Hire for L4, not for L5”, that their role-related knowledge round came back “not technical enough to face customers or something like that”, and that they were rejected. ^[23]Source 23Google Rejected for FDE. Need immediate referralPublisherBlind (teamblind.com)Source typecandidate report on Blind One round pointed to a lower level, the other to the customer bar; the double bar reads that split.

One poster on Blind, targeting L5, wrote in July 2026 of a Google FDE offer at L4; ^[24]Source 24Google FDE AdvicePublisherBlind (teamblind.com)Source typecandidate report on Blind another, with three years’ experience, reported in May 2026 a Google Cloud Applied AI FDE offer at L3 after being down-leveled. ^[25]Source 25Google Cloud FDE or Adobe Applied AI SWEPublisherBlind (teamblind.com)Source typecandidate report on Blind

Single reports: no rate, and no “Google down-levels”. Ask your recruiter: “Which level is this loop for, and can the rounds change it?” If level is decided after the loop, say: “That makes sense. So that I prepare well, which rounds tell you most about level for this role?” Then practice the level question and an offer a level down.

What no employer publishes

You will spot a loop statistic with nothing behind it. No employer in our research publishes a full FDE loop for experienced hires, a pass rate, a round weight, an end-to-end FDE timeline, what its interviewers write down or what its rubrics contain, and no report we read gives a pass rate or a round weight. Treat a figure as circulating, not evidence, and keep it off your map, when:

• it names no employer source;
• it gives one number for a round that reports show varies;
• several prep sites repeat it, and none shows an original.

Our free post what no one publishes traces circulating figures to pages that show no data.

Turning the map into a practice list

You will turn the map into this week’s reps and your questions. Here it is on real Google FDE sources: the stronger the evidence, the fuller the rep.

In words: the recruiter’s answer first; confirmed rounds get full reps; single, secondhand or unnamed reports get lighter ones; disagreement becomes a question.

Coding is unknown because posters on Blind disagree: an L5 poster wrote, in August 2026, of no LeetCode but a real-scenario question about streaming; ^{[26, 27]}Source 26Google FDE vs Remain Amazon SDEPublisherBlind (teamblind.com)Source typecandidate report on BlindSource 27Google L5 FDE vs Remain Amazon L5 SDEPublisherBlind (teamblind.com)Source typecandidate report on Blind an L6 poster wrote, in July 2026, that their recruiter described LeetCode medium or hard; ^[28]Source 28URGENT!! GOOGLE FDE 4 (L6)PublisherBlind (teamblind.com)Source typecandidate report on Blind and a poster in India described “leetcode medium hard” in May 2026. ^[23]Source 23Google Rejected for FDE. Need immediate referralPublisherBlind (teamblind.com)Source typecandidate report on Blind Drill both, such as the sliding-window rate limiter, and ask which languages you may use: one candidate wrote, in July 2026, that they were told Python was mandatory. ^{[12, 13]}Source 12Need help in preparation for Google Forward Deployed Engineer(FDE) interview (post by u/Wonderful-Ad6418)PublisherReddit r/leetcodeSource typecandidate report on RedditSource 13Need help in preparation for Google Forward Deployed Engineer(FDE) interview (comment by u/Wonderful-Ad6418)PublisherReddit r/leetcodeSource typecandidate report on Reddit

Ask on the screen call, then confirm in one short email:

Thanks for today. So I prepare for the right things, could you confirm:

1. Which kinds of interview are in my loop, and in what order?
2. Is the coding round algorithm-style or a practical task, and which languages and tools, including AI assistants, can I use?
3. Which level is this loop for, and can the rounds change it?

Then write it down, as in this block for a fictional Examplecorp; the take-home has a posted month, since it had not happened.

loop:  # fictional
  published:
    - what: "recruiter call; coding, design"
      source: "careers page, all engineers"
      checked: "September 2026"
  reported:
    - what: "decomp, interviewer as client"
      who: "two posters, two sites"
      interviewed: ["February 2026", "May 2026"]
      label: "candidates report"
    - what: "coding in a shared doc"
      who: "one candidate, review site"
      interviewed: "March 2026"
      label: "one report"
    - what: "take-home in the product"
      who: "one poster, via recruiter"
      posted: "June 2026"
      label: "described before the round"
  unknown:
    - "coding: algorithm or practical?"
    - "customer role-play?"
    - "AI tools allowed?"
practice:
  timed: ["coding", "system design",
          "decomp case"]
  lighter: ["coding in a plain doc",
            "scope a take-home"]

In words: one published line, three dated, labeled reports, three unknowns, and their reps.

Your map is ready when you can say it to the recruiter in two sentences, naming no forum: “From what I’ve read, loops for this role can include decomposition and a practical coding round. I haven’t seen anything about a customer role-play: is that part of this loop?”

The rest of this module is in Pro: what hiring leaders say reads the fourth source, the double bar shows the two bars a loop checks at once, and AI assistance rules fills your AI-tools line.