Same OA format as FDSE I think but onsite was stats focused, hypothesis testing and model evaluation metrics. Behavioral was embedded into every round, that was different. Coding bar felt pretty high.
Questions Asked
1.“Whats the difference between L1 and L2 regularization? When would you use each?”
Software Engineer
San Francisco, CA
Fall 2025No Offer
MIT · Computer Science
3rd year · 3.7+ GPA · 3 past internships
Hard Interview
TechnicalMultiple roundsBehavioral
The problem decomposition round was unlike anything I'd practiced for. Recruiter call about culture and projects, then an OA with coding, SQL and an API task. Virtual onsite had behavioral woven into every round
Questions Asked
1.“Why do you want to work at Palantir?”
2.“Tell me about the most technically complex problem you've solved”
Software Engineer
San Francisco, CA
Fall 2025No Offer
University of Michigan · Computer Science
3rd year · 2.9-3.2 GPA · 1 past internship
Hard Interview
TechnicalMultiple roundsUnexpected Questions
Karat screen with 3 easy problems plus time complexity discussion. the onsite is where it gets interesting, they had a problem decomposition round where you design a chess game and break it into pieces and then a learning interview where they literally drop you into an unfamiliar codebase and you have to navigate it with some guidance. I think my decomp round wasn't structured enough because I jumped into coding too fast instead of planning the architecture first. every round also has 20 min of behavioral questions mixed in so you can't just be a good coder
Questions Asked
1.“Given a linked list reverse it in-place”
2.“Detect if a linked list has a cycle and return the node where it begins”
Forward Deployed Software Engineer
San Francisco, CA
Summer 2026No Offer
University of Toronto · Computer Science
2nd year · 3.3-3.6 GPA · 0 past internships
Easy Interview
Technical
Pymetrics and HireVue then a call with HR about availability, then nothing for 3 weeks got an email saying they moved on and never got a real interview