Pros: It has good leadership at the top under Dr. Karp. A lot of their work will provide a sense of purpose and genuinely has a positive impact on the world. The office perks are also excellent, especially the food.

Cons: Palantir is arrogant and even borderline cultish. Below Dr. Karp, it suffers from immature leaders and managers. Being a people lead only implies that you have power over people, not that you have people skills. Few checks exist on a manager's power to ruin your career, especially if they subjectively determine that you are not a good "culture fit." A lack of "culture fit" means that it's OK to mistreat you because you're different, not that you don't fit into Palantir's culture.

Pros: High ownership and smart people.

Cons: Not very much coding day to day.

Pros: 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: * Technical challenging projects that allow you to grow your technical skills. There is plenty of help from experienced engineers in the organization to ensure you don't feel lost. * Excellent leadership at the Director level and first-line leads. Directors are open to any feedback, are very approachable, and always trying to help out engineers. * Good work-life balance. I'm hearing some horror stories from my colleagues in the tech industry, but I haven't had many problems here. I have been able to spend plenty of time with my family all these years. * Absolute meritocracy and very little bureaucracy. There are very good resources available in terms of systems, facilities, etc. * Very good perks.

Cons: 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.