← Back to Directory

DoorDash interview notes, page 22 of 42

Large Enterprises

Most of these DoorDash write-ups come from Software Engineers (265), then Data Scientists (69) and Product Managers (52). The most reported rounds are the technical phone screen (201), the system design round (93), the product sense round (55) and the behavioral / leadership round (36).

416 interview notes · updated Oct 2026

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026
DoorDash system design round that was basically one big question about building an image carousel with comments, voting, and efficient data structures. More depth than I expected for a single problem.
  • Design an image carousel that supports forward/backward cycling and autoplay with a configurable interval. Walk through the data structures, APIs, and time/space complexity.
  • Design a per-image comment thread with full create, read, edit, and delete support. What APIs do you expose, including pagination?
  • Support upvoting and downvoting on comments and return the top-k comments per image ordered by score, with ties broken by recency. Design the data structures for this at scale (up to 100k images and 1 million comments).
  • How do you prevent double-counting when a user rapidly toggles votes on a comment?

“The carousel mechanics themselves weren't the hard part.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026
Passed a DoorDash coding round for a software engineer role. One problem, but it had a twist that made it more interesting than the usual BFS grid question.
  • You're given a 2D grid where some cells are obstacles and others are destinations. Find the shortest distance from every cell to its nearest destination. The catch: obstacle cells still need a valid distance computed, not just skipped.

“The base BFS from all destination cells at once is pretty standard, but the obstacle wrinkle tripped me up initially.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026
DoorDash SWE coding screen, pretty standard setup except the question wasn't what I'd prepped for at all. Felt the time pressure hard by the end.
  • Design a cart validation function that checks item quantity availability and enforces minimum/maximum purchase limits.

“I'd drilled the dasher payment and bootstrap problems so much that seeing this felt like a gut punch.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview at DoorDash, one question about post-booking experience prioritization. Pretty open-ended and I wasn't totally sure what angle they wanted me to take.
  • How would you prioritize fixing the worst part of the post-booking experience on a platform like TaskRabbit?

“I went straight into listing pain points, which in retrospect was the wrong move.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at DoorDash for a software engineer role. The question was pretty focused on a food rating and comment system, with a lot of emphasis on schema design and preventing duplicate actions like double-tipping.
  • Design a food rating system that supports average ratings, user comments, and upvotes/downvotes on comments. If a comment gets enough upvotes, the system should automatically tip the comment author. How do you design the database schema, enforce that a user can only upvote or tip once, and handle eventual consistency?

“The idempotency part is where I got stuck.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

May 2026
DoorDash data science interview focused entirely on Dasher supply-side economics. Three meaty questions back to back covering program evaluation, experiment design, and compensation model tradeoffs. Felt more like a product analytics case study than a traditional DS interview.
  • How would you assess whether the Top-Dasher prioritization program should be launched?
  • For an extra-pay incentive aimed at improving Dasher engagement: what primary success metrics would you track, and how would you design an A/B test for it including treatment, control, experiment length, sample size, and guardrail metrics?
  • What are the key tradeoffs between paying Dashers per order versus per unit of time, and how would you run an experiment to determine which model is better for marketplace health?

“This one tripped me up more than I expected.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026
DoorDash SWE interview centered on a fairly well-known earnings computation problem with a bunch of follow-ups layered on top. The focus on Java-specific performance details was a bit unexpected and pushed me to think about I/O and memory more carefully than a typical coding round.
  • Given a high-volume stream of delivery records containing driver ID, base pay, tips, promotional adjustments, and timestamps, implement a system that computes total earnings per driver according to a defined set of pay rules.
  • How would you extend the pay computation logic to handle rule changes like new bonus tiers, refund events, and time-bounded promotional windows?
  • In Java, how would you optimize this solution for very high input throughput, specifically around I/O handling and data structure choices?

“This is the core of the whole interview.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

May 2026
DoorDash data science interview with a meaty experiment design question around delivery fee rollouts for unprofitable restaurant locations. One question, but it had a lot of surface area to cover.
  • A product team wants to add a $1 delivery surcharge to orders from the least profitable (~10%) of restaurant locations. Design an experiment to measure the effect on restaurant profitability, order volume, and customer satisfaction. How would you increase the statistical power of this experiment?

“I got through the basic A/B setup fine but fumbled when they pushed on variance reduction.”

View Post

DoorDash·Software Engineer·Onsite - Behavioral / Leadership

May 2026
DoorDash EM behavioral loop, five questions all circling the same theme: failure. By question three I realized they were going deep on this on purpose, not just checking a box.
  • Tell me about a project that failed. What went wrong and what did you do about it?
  • Describe a significant mistake you made. How did you find out about it, how did you communicate it, and how did you recover?
  • What is the most painful piece of feedback you have received, and what did you actually do with it?
  • Walk me through something you tried that did not work out as expected. What did you take away from it?
  • How do you apply lessons from past failures to your current work?

“I had a story ready but I think I over-explained the context and rushed the part they actually cared about, which was what I personally did after things fell apart.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026
DoorDash technical screen for a software engineer role, heavy on behavioral questions delivered rapid-fire style. You basically cycle through a bunch of situation-based prompts back to back, so it feels less like a conversation and more like a sprint.
  • What's the most impactful piece of work you've done recently?
  • Tell me about a time you had a conflict with a peer and how you handled it.
  • Describe a situation where you resolved a conflict that crossed team boundaries.
  • Give me an example of a time you influenced a decision or a group without having direct authority over them.
  • Tell me about a time you disagreed with your manager. What did you do?
  • Describe a time you had to prioritize under serious time pressure or when deadlines were competing.
  • Walk me through a situation where requirements were unclear and how you delivered despite that ambiguity.
  • Tell me about a failure and what you took away from it.
  • Give an example of a time you mentored or helped a teammate grow.

“This one sets the tone so you want a tight answer with a real number attached.”

View Post