DoorDash interview notes, page 30 of 42

“The setup sounds manageable until you actually sit down to write it.” The rest of the author's notes on Data Scientist 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 jumped straight to 'maybe grocery stores are faster' and kind of stopped there, which in hindsight was a weak answer.” 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.

“This tripped me up more than I expected.” The rest of the author's notes on Data Scientist 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.

“This is where I spent way too long listing possibilities without organizing them.” The rest of the author's notes on Data Scientist 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 spent way too long on the data model upfront and the interviewer had to nudge me toward the actual delivery pipeline.” 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.

“This is a big question and I underestimated how much ground it covers.” The rest of the author's notes on Machine Learning 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.

“This part I actually felt okay about.” 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 jumped straight to restaurant-level breakdowns and forgot to first sanity-check whether the spike was even real, like ruling out a logging bug or a change in how wait time is measured.” The rest of the author's notes on Data Scientist 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.

“Tricky because you have to context-switch into a company you don't work at and make judgment calls with incomplete info.” 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 while 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.