Poor work-life balance. If you don't mind 24/7 on-calls and frequent "surges," this is your home.
Professional growth perspectives are virtually non-existent. It's all very random and mostly luck/politics dependent. If you are "unlucky" and got assigned a crappy team/project early on, you will struggle to ever get considered for anything better. You will not learn much and just get stuck. There are few good teams, but since most others are so mediocre, you are unlikely to get into a good one, and moving "upwards" internally is very hard.
It's worse if you also get a lead (Palantir term for "manager") who lacks motivation, time, or power to support you. As burnout gets more widespread, more long-timers either quit or become jaded and stop caring; the chance of getting such a manager is higher.
In terms of coding, you will mostly fiddle with internal frameworks. If you are "lucky," you might get to work on something new; otherwise, expect vast legacy codebases with plenty of tech debt and support issues. Or they could put you as a "dev" on infra.
Leadership is still rather inexperienced and often not sure what they are doing. They try to call it "flat structure"; in practice, there are few unofficial "power clusters," centered around people who are actually important, and their decisions are enforced. Some got this authority by merit, others just by being close to founders/directors, "tenure," or being good at office politics. The result is low transparency on decisions affecting you, wasted effort, and frequent reinventing the wheel.
If you are extremely unlucky, they might put you on BD (business development). The main purpose of engineers there is to help customers use Palantir products, especially when they break (and boy, do they break often). Once you are in BD, Palantir will not let you "escape BD" until you quit.
Swallow your pride and hire some experienced senior managers/directors from companies with mature engineering cultures, so they can help you build the same within your company. Burning through graduate hires and investors' cash to keep trying random things won't work forever.
Had a recruiter call covering general questions, followed by a phone screen. The screen featured a LeetCode-type problem: compute the price of a stock portfolio for every day it remains active.
The recruiter initially scheduled and conducted my first interview. This was a phone-based behavioral interview where we discussed my background, experiences, and potential fit for the role.
One phone screen. It included generic behavioral questions, followed by a technical assessment. The technical portion involved parsing data and efficiently storing and manipulating it to create an output. This required knowledge of hash maps and sor
Had a recruiter call covering general questions, followed by a phone screen. The screen featured a LeetCode-type problem: compute the price of a stock portfolio for every day it remains active.
The recruiter initially scheduled and conducted my first interview. This was a phone-based behavioral interview where we discussed my background, experiences, and potential fit for the role.
One phone screen. It included generic behavioral questions, followed by a technical assessment. The technical portion involved parsing data and efficiently storing and manipulating it to create an output. This required knowledge of hash maps and sor