The self-introduction lasted only about 2 minutes before jumping into the problem. The interviewer was very engaged, actively discussing approaches, guiding me, and providing hints...

I received an email and scheduled the first round phone screen. My solution was deemed not optimal by the interviewer, who indicated a more efficient approach existed. I received a...

The recruiter reached out for a general backend engineering hire. The phone screen had two rounds: a 45-minute project deep dive followed by a coding round. I was rejected the next...

A recent phone screen. The conversation went fine, but I was rejected the next day. I observed that some teams at DoorDash appear to have moved away from the traditional coding for...

I wrote up this report right after finishing the phone screen. I made a mistake on time complexity mid-interview but self-corrected. After a week of no response, I assumed rejectio...

Applied at the end of February for Palantir FDSE. In early March, had a 20-minute phone screen with Mission Ops. This was purely behavioral, covering introduction, resume/projects,...

The phone screen resembled a take-home project where the starter code made the task self-evident; I could prepare in advance and then redo it live. The onsite consisted of four rou...

I went through a full loop: phone screen with a coding problem, then onsite with code craft, debug, system design, and behavioral rounds. The code craft and debug rounds are a newe...

I solved the main problem and ran all test cases successfully. The follow-up question required more thought; I explained a correct approach but did not have time to code it. Two da...