The primary reason I joined Palantir, and continue to work at Palantir, is the opportunity I have to learn and grow.
Palantir highly encourages technical growth, and I have often been paired with another developer on projects in order to further my skills.
This sort of learning also happens through self-organized, informal efforts, such as:
One of the primary criteria for choosing where to work was how much I would continue developing as an engineer.
At Palantir, I have not only improved significantly, but also continued learning about interesting new developments and technologies.
In addition to this, I’ve found that Palantirians tend to be well-aligned in our goals and objectives, which makes it all the more gratifying to work as part of a team.
Everyone at Palantir is focused on the same outcomes — delivering the most value to our customers in the most effective way.
Palantir seeks to give as much context as possible to everyone at the company and strives to make sure everyone understands the decisions that affect them.
This way, with everyone on the same page, it truly feels like working towards a shared vision.
As a rapidly growing company, we often find processes that once worked in the past no longer do so. Process changes can be painful, and it often takes some experimentation and iteration to determine what the new best process will be.
This is somewhat mitigated by the leadership's transparency around new initiatives and a willingness to admit failure when things don't work.
Keep soliciting feedback from all Palantirians, particularly new folks.
People who have been employed with the company for a while know that they can engage with management, but newer folks will be less inclined to do so.
It's extraordinarily important that everyone know their opinions are important and that they are being heard.
Applied online. Got a call. They gave one problem. Couldn't solve it fully. Rejected the next day. Basically, if you cannot solve the problem, you will be rejected.
Campus career fair, followed by a phone screen and an onsite interview.
I was interviewed on campus after submitting my resume at the career fair. They had a bunch of candidates on the day I interviewed. The interview included: * 1 on 1 whiteboard coding sessions. * Questions were very similar to any interview prepara
Applied online. Got a call. They gave one problem. Couldn't solve it fully. Rejected the next day. Basically, if you cannot solve the problem, you will be rejected.
Campus career fair, followed by a phone screen and an onsite interview.
I was interviewed on campus after submitting my resume at the career fair. They had a bunch of candidates on the day I interviewed. The interview included: * 1 on 1 whiteboard coding sessions. * Questions were very similar to any interview prepara