I joined Palantir in 2010 when the company had about 250 employees. I had worked at one company (> 10,000 employees) for many years before changing jobs in 2010. Needless to say, I was nervous with such a drastic change in my career. I'm now in my sixth year at Palantir, and I have to say that the transition was smooth. I continue to enjoy my work here every single day.
Here are the pros I can think of:
Like any other enterprise software company in this day and age, Palantir faces a stern test when it comes to figuring out what exactly their customers want and how they can deliver software for these needs. Because of this, the company does make significant organizational and philosophical changes frequently. This can cause some confusion amongst engineers, but I've generally seen company leadership providing lots of knowledge on why/how a change in direction was made.
Sometime in the next few months, Palantir will cross the threshold of 2000 employees. I definitely see some growing pains next year because of this. I expect our leadership to be fully ready for challenges they can predict, but many issues they don't anticipate at this time.
I was contacted by a recruiter for a 30-minute phone call to discuss the company. She asked a couple of technical questions that were easy and also found on this website. After that, I had a phone call with an engineer, but it wasn't a typical codin
The very first phone call starts with a recruiter. They ask me some basic questions, e.g., graduate date and skill sets. Plus, there's a very easy question about finding the singleton number from an array. Second phone call is about my resume and an
The interview process involved: * One on-campus screening * Two phone interviews * An on-site interview consisting of four technical interviews, with a product demo after the third. After all pre-on-site stages, a recruiter quickly informed m
I was contacted by a recruiter for a 30-minute phone call to discuss the company. She asked a couple of technical questions that were easy and also found on this website. After that, I had a phone call with an engineer, but it wasn't a typical codin
The very first phone call starts with a recruiter. They ask me some basic questions, e.g., graduate date and skill sets. Plus, there's a very easy question about finding the singleton number from an array. Second phone call is about my resume and an
The interview process involved: * One on-campus screening * Two phone interviews * An on-site interview consisting of four technical interviews, with a product demo after the third. After all pre-on-site stages, a recruiter quickly informed m