The position was local, based in their Georgetown office.
The interview process was, overall, not much different than at other companies, but there were some troubling oddities.
Despite their reputation for hard interviews, this was an average experience. The recruiter reached out to me and conducted a phone screen with someone from California. Next, someone from the UK called to prepare me for an on-site interview, which was followed by the on-site itself. I met with four different engineers separately, and they all asked similar questions. I had to whiteboard a solution to a problem, was pounded with Linux CLI questions like a contestant on Jeopardy, and had to describe various "what would you do" scenarios.
As for the oddities:
In the end, they declined to extend an offer, stating I wasn't experienced enough. This was despite my possessing a number of relevant high-level certifications, a security clearance, and a lengthy track record of success working for top technology companies. I was not disappointed because they left an uninspiring impression, and I would not have accepted the position if it had been offered.
What's the difference between RAID 0 and RAID 5, and when would you choose one versus the other?
The following metrics were computed from 2 interview experiences for the Palantir Site Reliability Engineer role in Washington, District of Columbia.
Palantir's interview process for their Site Reliability Engineer roles in Washington, District of Columbia is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Palantir's Site Reliability Engineer interview process in Washington, District of Columbia.