A LinkedIn recruiter reached out to me with an initial, long phone call. She asked many questions about why I wanted to work at Palantir, what I was interested in, and why I chose my current job.
Since I was nearing deadlines, she then scheduled me for an onsite interview at the Georgetown office.
The onsite was very short. It started with an employee taking my picture for a candidate profile, which I found unusual. This was followed by a quick tour of the office.
Next, I participated in two technical interviews:
Following the technical interviews, there was a demo with other interviewees watching a Palantir employee in New York on a TV. This demo was also combined with lunch.
After the demo and lunch, we were all escorted out of the building.
Two days later, I received a phone call stating I wasn't a fit for Palantir. I assume this was likely due to the system design round, but I received no feedback.
Onsite: A debugging round where you figure out why some sample code isn't producing the correct output. You're given a Mac laptop (and may need to ask your interviewer how to use commands if you're not familiar with Java or IntelliJ) and asked to correct the code. If you understand recursion and Java, you'll do fine. However, it wasn't clear if this was meant to be a "think aloud while debugging" question.
The following metrics were computed from 11 interview experiences for the Palantir Software Engineer role in Washington, District of Columbia.
Palantir's interview process for their 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 Software Engineer interview process in Washington, District of Columbia.