The process took around a month.
I was reached out to by the recruiter via LinkedIn.
I took the HackerRank challenge and passed 8/11 test cases. I am assuming they care more about the structure and your approach rather than the correctness.
After that, I had a phone call with the recruiter, where she went over general behavioral questions, followed by a technical phone interview with an engineer.
The technical question was not bad; it was an easier form of the UTF-8 encoding problem on LeetCode.
Then I was invited to the onsite interview, which had three rounds:
The first round was a bit challenging, and I took a couple of hints to come to the most efficient solution, which might have been why Palantir did not move forward with me.
The second round was an open-ended problem, and the goal is to cover the problem in as much depth as possible, which was easy in my opinion.
The third round was debugging, and they try to see your approach and how accurately and efficiently you fix the bad part of the code.
Signed NDA, but the problems were not really hard in my case.
Leetcode mediums.
The following metrics were computed from 10 interview experiences for the Palantir Software Engineer New Grad role in New York, New York.
Palantir's interview process for their Software Engineer New Grad roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Palantir's Software Engineer New Grad interview process in New York, New York.