Software Engineer Interview Experience
Interview process
My interview process included a recruiter screen, technical coding interviews, and a final behavioral and problem-solving round. What went well was that the interviewers were clear, collaborative, and gave me opportunities to explain my thinking. I also felt strong when discussing tradeoffs and working through ambiguous problems. What did not go as well was my time management on one coding question—I spent too long refining my first approach instead of moving quickly to a working solution. Overall, the process was challenging but positive, and it helped me identify areas to improve.
- Recruiter screen
- Phone interview
- Technical interview
- Final round
Interview rounds
2 questions across 4 roundsRecruiter screen
1 questionSpecific questions asked
Phone interview
Overview
Leetcode medium coding questions
Technical interview
Overview
Learning and decomposition round.
Final round
1 questionSpecific questions asked
Interview tips
Practice coding problems, explain your thinking clearly, and be ready for open-ended questions. I was surprised by how collaborative the interviews felt. Focus on communication, not just the final answer.
Company culture
The team seemed thoughtful, mission-driven, and comfortable tackling difficult, ambiguous problems.
Get full access with a membership, or share your experience to try it free.
More Palantir interview experiences
“The process was much more difficult than I expected. Leetcode and a mini data project was presented. The leetcode project was a sliding window question. ”
“I went into the decomposition round expecting a consulting case, and that was the exact wrong frame. What they really cared about was whether I could take a huge messy problem, turn it into data and logic, and bring them along for the ride.”
