Recruiter Screen
The initial recruiter screen typically involves a behavioral conversation focused on fit and interest in the company's mission, with some candidates noting issues with scheduling reliability.
BehavioralMission FitScheduling Issues
Real, anonymous reports from people who interviewed for Software Engineer at Palantir technologies, newest first and distilled into what to expect across the loop.
I interviewed for Palantir Software Engineer and the journey felt difficult-to-stiff, spanning a few weeks and ending without an offer after OA and follow-up technical rounds.
I interviewed for a Palantir Software Engineer role and had an overall average experience with a relatively standard set of technical rounds, mostly grounded in LeetCode-style questions.
The initial recruiter screen typically involves a behavioral conversation focused on fit and interest in the company's mission, with some candidates noting issues with scheduling reliability.
Candidates complete a 90-minute online assessment featuring LeetCode-style problems, which serves as a critical gatekeeper for advancing in the interview process.
Subsequent technical rounds typically consist of LeetCode-style coding questions, with varying difficulty levels and an emphasis on problem-solving and debugging skills.
Onsite interviews often include decomposition tasks where candidates must unpack vague problems and learning rounds that test their ability to adapt to unfamiliar topics or APIs.
The final round usually involves a conversation with a hiring manager that combines behavioral questions with a review of technical performance, often revisiting earlier weaknesses.
Candidates report a mix of experiences, with some finding the process rigorous and well-structured, while others faced scheduling issues or felt the technical bar was high; many did not receive offers.