Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

10 stories

Likes earn the author +10 XP for the first 3 likes each day

PalantirSoftware Engineer
Oct 2026

Rejected After the Learning Round

Just got the notification that I was rejected after the learning round. I'd prepared for a long time, Palantir is a company I really wanted to get into and Delta is a role I really admired, so I'm a bit down. Wanted to share some of my experience, maybe it can help someone. A friend referred me, and about a week later I got scheduled for the first screen, 20 minutes. At first I thought it was a r…

RejectedOnsite0
PalantirSoftware EngineerIntern
Oct 2026

One Coding Question on Summing Stock Prices by Day

Coding interview: You're given stocks on different days where Find the total sum of each day and use the previous values of each day if they are not included. For each day that a company does not have a price in, use the previous day's value to add to the sum so that the sum is always incrementing. The result for input_data would be:

Technical Screen0
PalantirSoftware EngineerIntern
Aug 2026

Three-Part FDE OA Building a Grocery Coupon System, Watch the Rounding

I got the OA and worked through it in about an hour and a half. Nothing was especially hard, but watch out for rounding. I've organized everything and posted it all below. Part 1 — Initial Problem You're building a discount system for Trader Yojoe's, a growing grocery chain. Their business is thriving, but they're starting a new pilot program where shoppers can bring coupons and apply them to ite…

Online Assessment0
PalantirSoftware Engineer
Reported Jul 2026

Palantir Software Engineer 30-minute deployment strategist screen

I expected a heavy technical process, but the first call surprised me. I had a 30-minute phone screen with a deployment strategist, and it went very well. We talked mainly about my resume, projects, and general background. It felt like a conversation about how I think and what I had been doing, not an immediate coding test. I did not receive an offer. What stayed with me was that the early stage…

0
PalantirForward-Deployed Engineer
Reported Jul 2026

Palantir Forward-Deployed Engineer interview: referral, decomposition, and long decision wait

After applying with a referral, I went through an HR screen and a decomposition round, then an onsite with three separate interviews on coding, learning, and decomposition. A final hiring-manager conversation ended the process. The format felt deliberate. Even before the onsite, the rounds appeared to build toward the same skill: taking an open-ended situation and making it actionable through bot…

RejectedHR Screen0
PalantirForward-Deployed Engineer
Reported Jul 2026

Forward-Deployed Engineer interview at Palantir: collaborative debugging

After I applied, a recruiter reached out and the process moved quickly into a technical conversation. I expected the recruiter to conduct the early screen, but an engineer joined instead. The exchange felt collaborative: I could ask questions, explain my thinking, and offer different approaches. The technical work was mostly coding and problem solving. One session was a straightforward LeetCode-l…

Technical Screen0
PalantirSoftware Engineer
Reported Jul 2026

Palantir Software Engineer interview experience

The process began with a basic recruiter call, then an OA, followed by a first technical round that already felt like a moving target. I had to do decomp and debug in the interview flow. The final technical round combined coding and behavioral questions. The journey had a coin-flip quality: it seemed possible to be solid technically and still not proceed, or to perform roughly and still advance d…

Online Assessment0
PalantirSoftware Engineer
Reported Jul 2026

Palantir Software Engineer interview: algorithms, REST API, and learning loop

After a recruiter call about my background and interests, I took a coding assessment with two medium-style algorithm questions and a REST API task. About a day later, I had a 45-minute technical interview that stayed focused on practical problem solving instead of theory alone. The process then moved into an onsite-style loop about learning and decomposition. In one round, I broke down an ambiguo…

Technical Screen0
PalantirSoftware Engineer
Mar 2026

Graph Code Review, Dijkstra, and a Multithreaded System Monitor

This company isn't that hard — it's basically all repeat questions from previous write-ups on this forum. If you go through the compiled experiences here, you'll run into the exact same problems. Phone screen. Onsite 1 had three technical rounds. Each one also asked some behavioral questions and asked about the projects on my resume. Coding round: a stock question from this forum, exactly the sam…

Onsite0
PalantirSoftware EngineerSenior+
Reported Jan 2026

Deep Dive on LLM Agent and Tool-Calling Design

Background I have spent most of my career in systems-heavy engineering: real-time software, autonomy, and multi-agent architectures built around LLMs. In the stretch before this interview I was putting together agent systems that combine retrieval, tool orchestration and structured reasoning across messy, complicated data. My work lives where software engineering and applied AI overlap, and there…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP