The interview process began with a two-level phone screen, primarily based on Java programming.
The on-site interview involved a brief meeting with the CEO (literally 30 seconds), followed by a series of 30-minute interviews that lasted essentially all day.
There were about 10-15 other candidates present simultaneously, so we were essentially shuttled between different "stations" and asked to perform Java exercises on whiteboards.
The company has a traditional startup feel, so interest in that environment is crucial for a good fit.
I anticipated working 60 hours a week and receiving a reasonable share in the company. At the time of my interview, they stated they had approximately 100 software engineers on staff.
Long story short, they expect employees to work about 60 hours a week, but the compensation package does not reflect this expectation.
The interview process itself was quite intense (expect 8-10 half-hour interview sessions), but it was friendly and not overly difficult.
How would you find the shortest path between two nodes in a graph?
Write code in Java to do this.
The following metrics were computed from 47 interview experiences for the Palantir Software Engineer role in Palo Alto, California.
Palantir's interview process for their Software Engineer roles in Palo Alto, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Palantir's Software Engineer interview process in Palo Alto, California.