J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 1 jour. J'ai passé un entretien chez Palantir Technologies (Palo Alto, CA) en oct. 2011
Entretien
I submitted my resume at a campus job fair. A week or so later, I was contacted for a phone screen. The interviewer briefly described three different software teams and asked which I was most interested in. All of the rest of the questions were about data structures and algorithms. Specifically, all questions were of the form "give me an algorithm to do X. What are the time and space complexity?" Some of the questions were the same or very similar to others posted on this site (for similar positions). The interviewer was a new engineer (< 6 months) himself. I found him to be very polite and helpful, not arrogant or condescending in any way. There were no questions about my background, experience, or anything else on my resume. I received a rejection email within five hours of the interview. At least they didn't leave me hanging! There's no question that the bar is very high at Palantir.
Questions d'entretien [1]
Question 1
For an array of integers, give an algorithm to determine if there are three elements that sum to zero. What are the time and space complexity? Generalize to the case where the sum of k elements is 0.
J'ai passé un entretien chez Palantir Technologies (Miami, FL) en juin 2026
Entretien
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
Questions d'entretien [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.
J'ai passé un entretien chez Palantir Technologies (New York, NY)
Entretien
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.
Questions d'entretien [1]
Question 1
Why do you want to work here?
What are you looking for in your next role.
J'ai passé un entretien chez Palantir Technologies
Entretien
Recruiter flaked me 3 times and this was always during the time of the interview. I would join the interview meeting and the recruiter would say ahh sorry I got a conflict, next time.