By FDE Interview Prep, a SourceStrongAI company

In this post11 sections
  1. What Palantir publishes about the learning interview
  2. How long is the Palantir learning interview, and when does it come?
  3. What candidates report being taught
  4. What the format rewards
  5. The technique: restate, example, smallest version, confirm, extend
  6. What to say when you are stuck
  7. Practice prompts to run with a friend
  8. Mistakes that cost the most
  9. Questions people ask
  10. Keep reading
  11. More from the blog

You spent weeks on arrays, graphs and dynamic programming, and now your Palantir loop has a round called “learning” that no problem list covers. The interviewer teaches you something you have never seen, then watches you use it in code. You can’t memorize what they will teach you, but you can rehearse how you learn it, and this post gives you the routine, the exact words and five practice prompts. Learning sits beside decomposition in Palantir’s onsite; the FDE interview guide covers the rest of the loop.

The short answer: Palantir’s early-talent timeline lists the learning interview as one of two one-hour onsite interviews, next to decomposition. Source 1Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring page Candidates report being taught a concept, a library or a piece of code, then asked to write or change code with it. Source 2Palantir Learning & Decomposition Interview (Blind)PublisherBlindSource typecandidate report on BlindSource 3Palantir learning interview (Blind)PublisherBlindSource typecandidate report on BlindSource 4Palantir interviewPublisherBlind (teamblind.com)Source typecandidate report on BlindSource 5Palantir FDSE Full Interview Loop Process (post by u/Not_the_Sauron)PublisherReddit r/csMajorsSource typecandidate report on RedditSource 6Interviewing at Palantir Technologies : FDSE InternshipPublisherMedium (Meghna Dutta)Source typecandidate’s personal write-up You cannot memorize the content. You can rehearse the process: restate what you were taught, ask for one example, build the smallest version, confirm it, then extend it, all out loud.

What Palantir publishes about the learning interview

Palantir names the round in one place we could find: a graphic on its students careers page. Its “Students and Early Talent Application Timeline” lists six steps: a HackerRank coding challenge, a 30-minute chat with a technical recruiter, a 30-45 minute technical interview, a virtual onsite, a hiring manager interview and an offer. Source 1Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring page

The onsite is where the lives. In that graphic, the virtual onsite is two one-hour interviews, learning and decomposition, with behavioral and technical questions, followed by a hiring manager interview customized based on onsite feedback. Source 1Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring page

Two things to keep straight:

Palantir also publishes how it wants you to talk. Its recruiting blog, in an August 2022 post for intern and new-grad candidates, advised thinking out loud in the technical interview and sharing questions and observations so interviewers can see how you approach the problem. Source 9From Pipeline to Prospect: Insights and Advice from Palantir Recruitment (Palantir Blog; archived copy)PublisherPalantir Technologies (Palantir Blog on Medium)Source typearchived company page In a round where the interviewer is watching you learn, that advice is most of the game.

How long is the Palantir learning interview, and when does it come?

Palantir’s graphic lists it as a one-hour onsite interview. Source 1Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring page The December 2025 Government-track candidate described theirs as 15 minutes behavioral and 45 minutes technical. Source 5Palantir FDSE Full Interview Loop Process (post by u/Not_the_Sauron)PublisherReddit r/csMajorsSource typecandidate report on Reddit Before their rounds, a Commercial Delta poster wrote, in July 2026, that theirs would be a first round of 30-45 minutes, and an FDSE intern poster wrote, in August 2026, that theirs came straight after the recruiter screen, which they thought was out of order. Source 7Palantir FDE Commercial Delta Interview (post by u/Popular_Elephant_349)PublisherReddit r/csMajorsSource typecandidate report on RedditSource 8Palantir FDSE Intern Learning Interview (post by u/Realistic-Major9132)PublisherReddit r/csMajorsSource typecandidate report on Reddit Be ready for it at any stage. For the rest of the loop, see what Palantir publishes and what FDSE candidates report.

What candidates report being taught

  • A package-installer concept. A poster on Blind with a Palantir new-grad interview wrote, in a thread from October 2022, that the learning interview introduced a custom package installer, like npm, pulling from more than one repo with multithreading, and that they coded functions using classes from Python’s concurrent library; they added that they did 3 of 5 tasks in an hour, half of which was behavioral. Source 2Palantir Learning & Decomposition Interview (Blind)PublisherBlindSource typecandidate report on BlindSource 3Palantir learning interview (Blind)PublisherBlindSource typecandidate report on Blind
  • Stages of fixes in existing code. A Blind commenter who said the interview was for SWE wrote, in July 2022, of about 4 stages of 5-7 minutes each: looking at application code, discussing limitations and coding fixes, with promises and futures as the topic. Source 2Palantir Learning & Decomposition Interview (Blind)PublisherBlindSource typecandidate report on BlindSource 3Palantir learning interview (Blind)PublisherBlindSource typecandidate report on Blind
  • Learning from documentation. A candidate for the FDSE internship in Sydney wrote, in an August 2022 Medium post, that the round asked them to learn new concepts with the help of documentation and solve 4 problems of increasing difficulty. Source 6Interviewing at Palantir Technologies : FDSE InternshipPublisherMedium (Meghna Dutta)Source typecandidate’s personal write-up
  • A downloader, and an unseen library. A Blind commenter who did not name a role wrote, in October 2022, that their learning round, about a year earlier, was implementing a parallel downloader with futures and threads. Source 4Palantir interviewPublisherBlind (teamblind.com)Source typecandidate report on Blind A second commenter in the same thread, also naming no role, described the round as debugging a code snippet that uses a library you have never seen. Source 4Palantir interviewPublisherBlind (teamblind.com)Source typecandidate report on Blind
  • A schema and its docs. One candidate wrote, in December 2025, that the learning round of their Government-track loop gave them a database schema and documentation and asked them to implement functions on the spot using the documentation. Source 5Palantir FDSE Full Interview Loop Process (post by u/Not_the_Sauron)PublisherReddit r/csMajorsSource typecandidate report on Reddit
  • A builder pattern. A commenter described their learning round, in May 2026, as “just using code written with builder pattern”, in a thread titled “Palantir FDSE Technical Interview”, naming no company or role. Source 10Palantir FDSE Technical Interview (comment by u/MShakeed)PublisherReddit r/csMajorsSource typecandidate report on Reddit
  • A concept, then query functions. A commenter wrote, in August 2026, in a thread titled “Palantir FDSE Intern Learning Interview” and naming no company or role, that the interviewer first taught a technical concept and a scenario, then showed object-oriented code for querying an imaginary database, and that they wrote a series of small query functions that they did not have to run, which the interviewer checked for correctness. Source 11Palantir FDSE Intern Learning Interview (comment by u/Illustrious_Beat4472)PublisherReddit r/csMajorsSource typecandidate report on Reddit

Three shapes recur. You are taught a concept and build it, you are handed a library or documentation and use it, or you are dropped into existing code and change it; the testable-refactor question is free and drills that shape. The last shape overlaps with the round posters call re-engineering; see the Palantir re-engineering interview for that one.

Posters on Blind described threads and futures more than once in 2022. Source 2Palantir Learning & Decomposition Interview (Blind)PublisherBlindSource typecandidate report on BlindSource 3Palantir learning interview (Blind)PublisherBlindSource typecandidate report on BlindSource 4Palantir interviewPublisherBlind (teamblind.com)Source typecandidate report on Blind You should not expect the same topic, but if you have never written concurrent Python, this warm-up is cheap insurance:

from concurrent.futures import (
    ThreadPoolExecutor, as_completed)
urls = ["a", "bb", "ccc"]
def fetch(url):
    return url, len(url)
with ThreadPoolExecutor(4) as pool:
    futs = [pool.submit(fetch, u)
            for u in urls]
    for f in as_completed(futs):
        print(f.result())

Results arrive in completion order, not input order, and result() re-raises any exception the worker hit. The concurrent.futures documentation covers the rest.

What the format rewards

No rubric for this round is published, so this is our reading of the published advice and the reports, not what any interviewer is told to score.

  1. Thinking you can hear. Beyond the blog advice above, a Foundry hiring manager, in a July 2025 Palantir video aimed at software engineers rather than FDEs, said showing how you think through problems is as important as reaching a good final outcome. Source 12From Code to Career: Meet Palantir's Hiring Managers (YouTube uploaded English captions)PublisherPalantir, YouTubeSource typerecorded talk or interview
  2. Correct use of what you were taught. One commenter wrote, in August 2026, that their code was never run and that the interviewer looked for correctness. Source 11Palantir FDSE Intern Learning Interview (comment by u/Illustrious_Beat4472)PublisherReddit r/csMajorsSource typecandidate report on Reddit Your mental model has to be right, because no test run will catch it.
  3. Steady progress through a series of tasks. Both the October 2022 poster and the Sydney intern described several tasks in one session, not one big problem. Source 2Palantir Learning & Decomposition Interview (Blind)PublisherBlindSource typecandidate report on BlindSource 3Palantir learning interview (Blind)PublisherBlindSource typecandidate report on BlindSource 6Interviewing at Palantir Technologies : FDSE InternshipPublisherMedium (Meghna Dutta)Source typecandidate’s personal write-up A small working answer to the first task beats a grand design for all of them.

The technique: restate, example, smallest version, confirm, extend

This is our method, not a published Palantir rubric. It works because each step gives the interviewer a chance to correct you before a wrong idea turns into code.

Here it is on a concept we made up for practice; it is not a reported Palantir prompt. The interviewer says:

“Our ledger never stores a balance. It stores an append-only log of events, each with an id, a time at and a type. The balance is whatever you get by replaying the log from the start. Mistakes are never edited out; you append an event that corrects them.”

Restate it in your own words

Say it back, and add one consequence of your own. The consequence proves you understood rather than memorized.

“So the log is the only source of truth, the balance is derived by replaying it in order, and nothing in the log ever changes. That means undoing something is an append, never a delete. Is that right?”

If the interviewer corrects you here, you have lost ten seconds instead of ten minutes.

Ask for one example

“Could you give me a short log and the balance you’d expect?”

Suppose the answer is a deposit of 100 at time 1, then a withdrawal of 30 at time 2, for a balance of 70. You now have a test case, and you did not have to invent one. The vague requirements question drills this habit of asking before building.

Build the smallest version

Handle only what the example needs:

def balance(log):
    total = 0
    for e in log:
        if e["type"] == "deposit":
            total += e["amount"]
        elif e["type"] == "withdraw":
            total -= e["amount"]
    return total

Say what you left out: “No time filter and no corrections yet. I’ll add them once this matches your example.”

Confirm against the example

Run it if you can. If the round is on paper, or the code is never run, trace it aloud: “Starts at zero, the deposit makes it 100, the withdrawal makes it 70. That matches.”

Extend one step at a time

Now the interviewer asks for the balance as of a given time, and for a reverse event that cancels an earlier event by its id. Ask before you code: “Is the log always in time order, and can a reversal ever be reversed?” Suppose the answers are yes, it is in time order, and no, a reversal is never reversed. If a reversal could be reversed, you would replay reversals in order instead of collecting them into a set, so say that out loud. Then extend:

def balance(log, until=None):
    seen = [e for e in log
            if until is None
            or e["at"] <= until]
    undone = {e["target"] for e in seen
              if e["type"] == "reverse"}
    total = 0
    for e in seen:
        if e["type"] == "reverse":
            continue
        if e["id"] in undone:
            continue
        if e["type"] == "deposit":
            total += e["amount"]
        elif e["type"] == "withdraw":
            total -= e["amount"]
        else:
            raise ValueError(e["type"])
    return total

Two details show you kept the rule you were taught. You never remove anything from log; you skip reversed events while replaying. And a reversal that happens after until does not count, because at that time it had not happened yet. Confirm both out loud with a small case, then stop and ask what comes next.

“Checking out loud: your example still gives 70, as of time 1 it’s 100, and if I reverse the withdrawal it’s back to 100 with all three events still in the log.”

StepWhat you say
Restate“Let me say it back, plus one thing it implies.”
Example“Could you give me one input and the output you expect?”
Smallest“I’ll handle only your example first.”
Confirm“Tracing it: this matches.”
Extend“Before I add that, one question.”

Narration carries the whole routine. Narration, the board and the clock shows how to think out loud without rambling and when to check in.

What to say when you are stuck

Getting stuck is part of the round. Being stuck in silence is what hurts. Keep these lines ready:

  • Your model broke. “I expected this to print one thing and it printed another, so my model is wrong somewhere. Let me try the smallest case.”
  • You do not know a term. “I haven’t used the builder pattern. Is the idea that each call returns the object, so the calls chain?”
  • You need to read. “I’m going to look for one thing in the docs: how errors come back. I’ll tell you what I find.”
  • You cannot recall the syntax. “I’ll write this line as pseudocode and come back to the exact call, so we don’t lose the thread.”
  • You are running out of time. “I won’t finish this extension. Here is how I would do it, and here is the case I’d test first.”

Every one of these turns a stall into evidence of how you learn. The interviewer can only help you if they can see where you are.

Practice prompts to run with a friend

These prompts are our own inventions, written for practice. None is a reported Palantir prompt.

For the friend who teaches: pick a prompt the candidate does not know. Teach it in a few minutes without showing code. Give the first task, then the extensions one at a time. Answer questions, but do not volunteer the surprise.

  1. . A breaker sits in front of a flaky service and is closed, open or half-open. Too many failures open it; after a cool-down, one trial call is allowed through. Task: write allow() and record(ok). Extension: what happens if the trial call fails?
  2. Grouping with itertools.groupby. Teach it from the Python documentation. Task: count orders per customer from a list of names. The surprise: groupby only groups consecutive items, so an unsorted list splits a customer in two. A candidate who confirms on an unsorted example catches it.
  3. A tiny template language. {{name}} is replaced by a value, and {{name|guest}} falls back to a default. Task: write render(template, values). Extension: a missing name with no default, and an escaped brace.
  4. Undo and redo. Every command has do and undo, and the app keeps a stack. Task: implement undo(). Extension: add redo(), then decide what happens to the redo stack when a new command runs.
  5. Ordered migrations. Database migrations are numbered, applied in order and recorded in a table. Task: given the applied list and the available files, return what to run. Extension: detect a migration missing from the middle.

What the friend watches for

  • Did they restate the concept, with a consequence of their own, before coding?
  • Did they ask for an example instead of inventing one?
  • Was there working code for the first task early in the session?
  • Did they confirm against the example before extending?
  • Did they catch the surprise, or ask the question that exposes it?
  • Could you follow their thinking the whole time?

Then swap roles.

Mistakes that cost the most

  • Nodding along. Saying “makes sense” and then coding a model the interviewer never described. Fix: restate before you type.
  • Reading everything first. Working through the whole documentation before writing a line. Fix: turn the task into a question and read only for its answer, as in learn a new library fast.
  • Borrowing names from a tool you know. The concept looks like npm, so you type npm’s names. Fix: use the names on the page in front of you.
  • Building the general version first. Designing for every extension before the first task works. Fix: smallest version, confirmed, then the next step.
  • Breaking the rule while extending. In the ledger above, deleting an event to undo it passes a quick test and breaks the concept. Fix: before each extension, say which rule it must respect.
  • Treating the behavioral part as small talk. The October 2022 poster said half their hour was behavioral, and the December 2025 candidate described the round as 15 minutes behavioral and 45 minutes technical. Source 2Palantir Learning & Decomposition Interview (Blind)PublisherBlindSource typecandidate report on BlindSource 3Palantir learning interview (Blind)PublisherBlindSource typecandidate report on BlindSource 5Palantir FDSE Full Interview Loop Process (post by u/Not_the_Sauron)PublisherReddit r/csMajorsSource typecandidate report on Reddit Palantir’s graphic says both onsite interviews include behavioral questions. Source 1Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring page Fix: have a true story ready in this shape: what you had to learn, the deadline, the first thing you read and why, what you shipped, and what you’d do faster now. Learning an unfamiliar domain fast drills it.

To weigh reports like the ones above against what employers publish, the evidence map gives a method, and what FDE coding rounds test covers the other coding formats you may meet.

The model answer to learn a new library fast walks through a documentation-first build, spike by spike, and it is included in Pro, which starts with a 7-day free trial on the pricing page. Then run the drill again with a friend and one of the prompts above, and work through the coding questions below.

GlossaryRe-engineering roundAn interview in which you learn, debug or extend code or a library you have never seen, against the clock and out loud.More on Re-engineering roundGlossaryForward 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 engineerGlossaryCircuit breakerA pattern that stops calling a failing dependency for a while, then probes it, so failures do not cascade.More on Circuit breaker

Questions people ask

What is the Palantir learning interview, and what do candidates report?

Candidates report being taught something new, such as a concept, a library or a piece of code, and then asked to use it in code. Palantir’s early-talent timeline lists learning and decomposition interviews in its virtual onsite, with behavioral and technical questions.Source 1Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring pageSource 2Palantir Learning & Decomposition Interview (Blind)PublisherBlindSource typecandidate report on BlindSource 3Palantir learning interview (Blind)PublisherBlindSource typecandidate report on BlindSource 4Palantir interviewPublisherBlind (teamblind.com)Source typecandidate report on BlindSource 6Interviewing at Palantir Technologies : FDSE InternshipPublisherMedium (Meghna Dutta)Source typecandidate’s personal write-up

Can you prepare for the Palantir learning interview, when a Blind commenter said you can’t?

For the content, yes. One Blind commenter wrote, in October 2022, that you cannot prepare for it, and described debugging a snippet that uses a library you have never seen. You can still practice the process. Restate what you were taught, ask for an example, build the smallest working version and confirm it before extending.Source 4Palantir interviewPublisherBlind (teamblind.com)Source typecandidate report on Blind

Do candidates report Palantir learning interviews outside intern and new-grad hiring?

Palantir publishes the learning interview in its early-talent timeline, and posters who named other roles mention it too. One poster applying for a Palantir FDE Commercial Delta role said, in July 2026, that their first round was a learning interview, and another described a learning round in a Government FDSE loop in December 2025.Source 1Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring pageSource 5Palantir FDSE Full Interview Loop Process (post by u/Not_the_Sauron)PublisherReddit r/csMajorsSource typecandidate report on RedditSource 7Palantir FDE Commercial Delta Interview (post by u/Popular_Elephant_349)PublisherReddit r/csMajorsSource typecandidate report on RedditSource 8Palantir FDSE Intern Learning Interview (post by u/Realistic-Major9132)PublisherReddit r/csMajorsSource typecandidate report on Reddit

Keep reading

Guides

Company guides

Lessons

Questions

More in Interview rounds, page 2