Received a link to do an online HackerRank problem. The problem statement was long, but not terribly difficult.
Four weeks passed with no response. I reached out to my recruiter asking if there would be further steps and got an interview with a recruiter set up for a week later. Standard behavioral questions were asked, with an emphasis on why Palantir.
Had a technical phone screen set up for a week later. The interviewer mistakenly called me a day early but was apologetic, and we still proceeded with the interview the next day. It was a pretty simple array and string parsing question through HackerRank codepair.
Things got a bit weird. I sent a message indicating that I had offer deadlines in a few weeks and received a rejection about an hour later. Then I got a call later saying it would be tough to work with my deadlines, but they would still like me to do an on-site. We scheduled one for 10 days later.
The on-site was done very well (I interviewed in DC). Meals were generously taken care of, and the hotel was lovely. The interviews consisted of three technical interviews: a problem-solving (i.e., LeetCode/HackerRank-style) question, then a debugging session on a laptop, then a decomp interview, followed by a product demo. After the product demo, I was kept for a final interview with a hiring manager that was a more 'real-world' problem-solving question. I felt very confident at this point.
This was easily the worst part about the process. I received a call about a week later asking for another interview with a hiring manager for their NY office. I was told this would be mostly behavioral with some small problem-solving portion. Then I got an email twenty minutes later asking if I could interview in twenty minutes. So, 45 minutes from when I received the call, I was interviewing again. The first twenty minutes were as expected with behavioral questions, but then we did 45 minutes worth of an in-depth technical question that was more difficult than what I had seen on-site. At this point, I felt as though my time was disregarded and that I was misled on the interview content. Needless to say, it left a bad taste in my mouth about Palantir's hiring process.
Received a rejection call the next day.
Overall, the process was drawn out and, while alright during the middle phases, felt disrespectful towards the end.
What about Palantir attracts you?
The following metrics were computed from 15 interview experiences for the Palantir Forward Deployed Software Engineer role in Washington, District of Columbia.
Palantir's interview process for their Forward Deployed Software Engineer roles in Washington, District of Columbia is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Palantir's Forward Deployed Software Engineer interview process in Washington, District of Columbia.