The recruiter reached out via LinkedIn. The technical phone screen was one week later. The final round consisted of three interviews, all of which covered behavioral components. Two interviews included coding questions, and the last focused on OO/system design.

The recruiter chat and technical phone screen were fairly standard. Palantir is kind of unusual in that they have a second round of three technical interviews before finally conducting an interview with a hiring manager at a later date. I guess it's not worth the hiring manager's time to talk with you until you've passed the technical bar.

The coding questions were fairly standard, although one ended up being quite rushed since the interviewer arrived 15 minutes late, only leaving 15 minutes to code. I was unable to finish the question. The system design question was a bit odd since I was asked to dive deep into OO design and implement classes, yet the interviewer seemed disappointed that I didn't spend as much time on infrastructure. Again, the interview was rushed, under 30 minutes. I felt I could have demonstrated much more given even five to ten more minutes.

All in all, the technical questions are fairly standard for the industry. However, I believe Palantir could probably get a higher fidelity read on candidates' technical abilities by allocating a bit more time to the technical sections of interviews.

A variation of merge K sorted arrays.