People are amazing; the hiring quality is out of this world even for the Valley.
Projects can be extremely interesting.
Tech stack (especially on the Foundry side) is modern and fun to use.
The software is real and works unlike most enterprise technology Palantir competes against.
Work/life balance is highly project dependent. Long hours trend towards brutal if your project is fast-paced or the customer is overly demanding.
Your project may not be all that interesting, and you'll hear about everyone else doing world-changing tech. If your project is uninteresting and has long hours, you can burn out fast.
Some of the Gotham codebase is archaic and hard to understand.
Palantir changes over time, and you'll need to adapt or reinvent yourself if you stay longer than two years. This can be fun but stressful, and the pace never slows down.
So far, so good. I'm only at the technical phone screen, but the recruiter has been very enthusiastic. I have a technical call soon that I'm studying for. I hear the interview questions are hard and stressful.
The process began with an online application, followed by a timed interview test. The timed test was very short for the type of problem presented. The choice of programming language was Python. The timer remained visible on screen throughout the tes
It was a Karat interview with one interviewer. A pretty standard Karat interview, comprising three types of questions. First was a simple algorithm problem. Second involved two subproblems, asking if you knew some basic data structures and algorith
So far, so good. I'm only at the technical phone screen, but the recruiter has been very enthusiastic. I have a technical call soon that I'm studying for. I hear the interview questions are hard and stressful.
The process began with an online application, followed by a timed interview test. The timed test was very short for the type of problem presented. The choice of programming language was Python. The timer remained visible on screen throughout the tes
It was a Karat interview with one interviewer. A pretty standard Karat interview, comprising three types of questions. First was a simple algorithm problem. Second involved two subproblems, asking if you knew some basic data structures and algorith