I applied online. The process took 4 weeks. I interviewed at Palantir Technologies in Sept 2014
Interview
The interview process was very long. The first 3 stages were quite easy and took about 3 weeks. Then they scheduled me for 2 phone interviews. They were much harder than all the previous stages. In the first interview they asked me a very difficult algorithmical task (basically, either you know the task from before the interview and you solve it correctly or you don't know it and it's very, very hard to come up with a solution during the 45 min call). The interviewer asked me to code in Java. It's the first time I was asked to code in one specific language during an interview; all other companies allowed me to choose a language I felt most comfortable with. The interviewer was very quiet and didn't mention any problems with the solution I proposed. In the end I ended up coding the wrong solution and the interviewer said it was ok although it was clearly wrong.
I got an auto-reply rejection letter a few days after the second phone interview. I think it's very unprofessional that after 5 stages of the interview process they only sent me an auto-reply email without offering any feedback. They even got the name of the position that I applied for wrong in the rejection letter.
Interview questions [1]
Question 1
In one of the interviews I got a question to design and implement a backend for a very hard and abstract problem.
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.