DoorDash interview notes, page 3 of 42

“I went straight to the tracking screen and talked about ETA accuracy, which felt safe but probably too obvious.” The rest of the author's notes on Product Manager interview at DoorDash, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the data model which felt safe.” The rest of the author's notes on Software Engineer interview at DoorDash, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The question was about a competitor's product, which threw me off a bit since I was interviewing at a food delivery company.” The rest of the author's notes on Product Manager interview at DoorDash, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one took me a minute to even parse.” The rest of the author's notes on Software Engineer interview at DoorDash, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to volume of reviews and average rating, which in hindsight was pretty shallow.” The rest of the author's notes on Software Engineer interview at DoorDash, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The 'simpler product' framing is a trap because the moment you pick order tracking you're suddenly talking about real-time updates, polling vs websockets, eventual consistency.” The rest of the author's notes on Frontend Engineer interview at DoorDash, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The Spotify framing was a curveball for a DoorDash interview.” The rest of the author's notes on Product Manager interview at DoorDash, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one shows up a lot apparently and I still fumbled the extension.” The rest of the author's notes on Software Engineer interview at DoorDash, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to BFS from each walkable cell separately, which works but is obviously O((m*n)^2) in the worst case and they were not happy with that.” The rest of the author's notes on Software Engineer interview at DoorDash, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started by sketching out a state machine in my head and that was probably the right instinct, but I got sidetracked thinking about data structures before I'd even nailed down the core logic.” The rest of the author's notes on Software Engineer interview at DoorDash, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.