Palantir Interview Experiences

10 results

• 

  Three-Part FDE OA Building a Grocery Coupon System, Watch the RoundingPalantir · Software Engineer · Intern · Online Assessment · Aug 2026

  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…

• 

  Forward-Deployed Engineer interview at Palantir: collaborative debuggingPalantir · Forward-Deployed Engineer · Technical Screen · Jul 2026

  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…

• 

  Palantir Forward-Deployed Engineer interview: referral, decomposition, and long decision waitPalantir · Forward-Deployed Engineer · HR Screen · Jul 2026

  Rejected

  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…

• 

  Palantir Software Engineer 30-minute deployment strategist screenPalantir · Software Engineer · Jul 2026

  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…

• 

  Palantir Software Engineer interview experiencePalantir · Software Engineer · Online Assessment · Jul 2026

  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…

• 

  Palantir Software Engineer interview: algorithms, REST API, and learning loopPalantir · Software Engineer · Technical Screen · Jul 2026

  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…

• 

  Palantir technologies Forward-Deployed Engineer interview: decomposition and onsite loopPalantir technologies · Forward-Deployed Engineer · Onsite · Jul 2026

  Rejected

  I applied with a referral and first had a recruiter screen, followed by a decomposition round. I then reached an onsite loop with three interviews covering coding, learning, and decomposition. The rounds felt connected, as if each one was testing whether I could reason through problems in a forward-deployed way. After the onsite, I had a hiring-manager round for the final decision. I did not make…

• 

  Palantir technologies Software Engineer interview: coding, REST API, and decompositionPalantir technologies · Software Engineer · Technical Screen · Jul 2026

  I began with a short recruiter call that felt like a fit and motivation check rather than a technical grilling. I discussed my background and past work, and I got the sense they wanted to know whether I cared about the mission and the real-world impact of the software, not just the title. About a week later, I had a technical screen with a small set of coding questions: a couple of LeetCode-style…

• 

  Graph Code Review, Dijkstra, and a Multithreaded System MonitorPalantir · Software Engineer · Onsite · Mar 2026

  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…

• 

  Deep Dive on LLM Agent and Tool-Calling DesignPalantir · Software Engineer · Senior+ · Technical Screen · Jan 2026

  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…