I applied through a recruiter. The process took 3 months. I interviewed at Palantir Technologies (New York, NY) in Dec 2016
Interview
I had a phone interview, and then an onsite (3 interviews + demo).
My main recruiter essentially didn't contact me aside from scheduling. I had another recruiter ask for a phone call with me as a follow-up to my phone interview, which was kind of random as my original recruiter didn't say anything about this. It went well but had to be rescheduled twice, once without notice (where I was only told the day after).
I was not given any details about the onsite prior to getting there except the FAQ and some other documents, and the time I would be starting. The FAQ said my recruiter would contact me prior to the onsite with more information regarding the day, but they never did. I was also left in the interview room with no idea of when my interviewer would get there or when my next interview would start. The interviewers were pleasant for the most part, although felt really rushed and on a time crunch. They all seemed to be running late though. I wasn't given an office tour, with the exception of here's the dining area and the rooms are all named after a theme. My recruiter didn't seem to enjoy my presence. The demo was pretty good though, I learned a lot more about the company and the answers the presenter had to the questions asked seemed genuine.
I interviewed at Palantir Technologies (Miami, FL) in Jun 2026
Interview
Started with a recruiter screen where the whole point is just checking if you actually care about their mission and the real-world impact of their software, rather than just wanting a cool tech job. After that was a 90 minute hackerrank OA that felt more like an implementation mini-project with SQL and Python instead of abstract algorithms.
The onsite was a 4-round loop chosen from decomp, re-engineering, learning, coding, and sys design. Decomp is the most important one - they give you a super vague prompt like designing a chess game or tracking a disease from scratch, and you have to map out the inputs and logic out loud. Re-engineering gives you around 1000 lines of code with a very subtle logical bug to fix, and the learning round drops you into a random API with barely any documentation to see how fast you pick it up lol. Coding was standard LC mediums but they squeeze a 20-minute behavioral chat right into the middle of it, and sys design was heavy on data governance and fault tolerance. The final chat with the hiring manager is pretty intense too ngl. They will actually make you redo parts of the onsite you struggled with. For prep, don't just mindlessly grind LeetCode. Practice reading other people's code fast and structuring ambiguous problems. I got a really good Palantir coach on Prepfully who helped a lot to catch my blind spots and get a reality check before the actual loop. Overall, not very easy though
Interview questions [1]
Question 1
A payment processing module has a race condition that produces incorrect totals under concurrent writes. Walk through how you would identify the root cause and propose a fix.
I applied through a recruiter. I interviewed at Palantir Technologies (Palo Alto, CA) in Jun 2026
Interview
Standard interview similar to their new grad. Recruiter, two technicals decomp and learning, and then hiring manager half behavioral half technical leetcode style. Really focused on why palantir, mission alignment, and role alignment.
I interviewed at Palantir Technologies (New York, NY)
Interview
Great interview process - 1. Recruiter call 2. Leetcode style technical 3. Scoping style (decomp) interview 4. Frontend coding 5. Another scoping (decomp round).
Interviewers were fun and engaging, and I felt challenged in a positive way.
Interview questions [1]
Question 1
Why do you want to work here?
What are you looking for in your next role.