Real, anonymous reports from people who interviewed for Software Engineer at Palantir, newest first and distilled into what to expect across the loop.
After a recruiter call that was mostly about my background and interests, I got pulled into a coding assessment. It was short but specific: two medium-style algorithm questions plus a REST-API task. About a day or so later I had a 45-minute technical interview where the focus stayed on practical problem solving rather than just theory.
My process started with a basic recruiter call, then an OA. The OA was followed by a first technical round, and that’s where things already started to feel like a moving target: I had to do decomp and debug as part of the interview flow.
The interview process typically begins with a recruiter call focused on gauging interest in the company and fit for the role, followed by an online assessment that includes coding questions, often in a LeetCode format.
Candidates can expect one or more technical coding interviews that focus on medium-level algorithm problems, with an emphasis on problem-solving and clarity in communication during coding.
A critical part of the interview process involves decomposition and learning rounds where candidates must break down ambiguous problems and demonstrate their ability to learn and apply new concepts on the fly.
Candidates will encounter behavioral interviews that assess alignment with the company's mission and values, emphasizing the importance of understanding the role and its impact.
The final round often includes a mix of behavioral questions and technical challenges, where the hiring manager assesses both technical competence and fit for the team and company culture.
Candidates report a sense of randomness in the evaluation process, where performance in earlier rounds may not guarantee progression, and small mistakes can significantly impact outcomes.