← Back to Directory

DoorDash interview notes, page 7 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·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
DoorDash product sense interview focused entirely on the post-order delivery experience. Two questions, both connected, felt like one long case study that kept going deeper.
  • What are the biggest problems a customer might face in the delivery experience after placing an order?
  • How would you prioritize those problems, and what would your approach be to actually solving them?

“I went pretty broad at first, listing things like late deliveries, wrong items, no communication.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Apr 2026
DoorDash SWE interview with a simulated production incident scenario. The whole thing was basically a live debugging exercise built around a realistic microservices architecture, which I found more interesting than a typical system design prompt.
  • A payment card integration service is showing higher-than-expected memory utilization at 4:30pm Pacific. Walk through how you'd investigate, what signals you'd look at, what hypotheses you'd form, and how you'd mitigate while root-causing the issue.

“The architecture they gave you matters a lot here: dasher app hits a gateway service, which calls a payment card integration service, which talks to a third-party card provider and also reads/writes a Redis cache for card and account info.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at DoorDash with a product sense question about the post-order experience. Pretty open-ended and I wasn't totally sure how deep they wanted me to go.
  • After a customer places an order on a delivery platform, what problems or failure points do you anticipate could arise?

“I started rattling off things like late deliveries and out-of-stock items, which felt obvious the moment I said them.”

View Post

DoorDash·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Three behavioral questions for a Software Engineer role at DoorDash. Pretty standard stuff but the failure question caught me more off guard than I expected.
  • Walk me through a recent project you worked on. What were you trying to accomplish, what was your role, and how did it turn out?
  • Tell me about a time you made a mistake at work. What happened, what was the impact, and what did you take away from it?
  • Describe a project you consider outstanding. What made it stand out, whether that's the technical complexity, the business impact, or how you led it?

“I had a decent answer prepped for this but rambled a bit on the context before getting to my actual contribution.”

View Post

DoorDash·Software Engineer·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a bizops role at DoorDash, got hit with a classic market growth allocation case. Pretty open-ended, which I wasn't fully prepared for.
  • You have $1 million to spend on growing market share in a city. How would you allocate it?

“I went straight to supply-side (more drivers) without pausing to ask which city or what the current market position even was.”

View Post

DoorDash·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Got a coding question at DoorDash for an MLE role, basically a CPU task scheduling problem. Pretty algorithmic for an ML interview but not totally surprising for a bigger tech company.
  • You're given a list of tasks, each with an enqueue time and a processing time. A single-threaded CPU picks the available task with the shortest processing time at any given moment (ties broken by index). If nothing is available it just waits. Return the order in which tasks get processed.

“This is a heap problem and I knew it pretty fast, but getting the edge cases right took longer than I'd like to admit.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Apr 2026
DoorDash technical screen focused on a grid-based shortest-path problem with a multi-source BFS twist. Pretty algorithmic, not much fluff around it.
  • Given a 2D grid with obstacles and multiple DashMart locations, find the shortest distance from every customer cell to its nearest DashMart. Explain your approach and why you'd choose multi-source BFS over running a separate BFS from each source.

“I knew BFS for shortest path on a grid, but the multi-source angle threw me a bit at first.”

View Post

DoorDash·Data Scientist·Take-home Assignment

Apr 2026
DoorDash data science take-home with a pretty dense SQL prompt built around their core domain: orders, dashers, merchants, promos. Six sub-questions covering window functions, anomaly detection, uplift estimation, and even a bootstrap CI question at the end. Felt more like a mini-project than a screening filter.
  • Given a multi-table delivery schema, compute the daily on-time delivery rate per city over a rolling 7-day window. Define on-time as delivery within 45 minutes of order creation, treating null delivered_at as late and excluding canceled orders. Return city, date, on-time count, total eligible, and rate.
  • For a given month, rank the top 3 merchants per city by GMV, where GMV accounts for subtotal, delivery fee, tip, and any applied promo discount. Break ties by cancellation count ascending, then by merchant ID. Exclude canceled orders from GMV but still track cancellations per merchant.
  • Using an order events log table, identify orders that have a 'delivered' event but no 'picked_up' event that strictly precedes it in time. Return the order ID and a minimal event timeline showing the anomaly.
  • Calculate a weekly dasher acceptance rate: for orders created in a given ISO week and assigned to a dasher, what share had an accepted_at timestamp within 3 minutes of created_at? Exclude orders canceled before acceptance. Output dasher_id, ISO week start, assigned order count, accepted-within-3m count, and rate.
  • Find customers who have placed exactly two lifetime orders and both were canceled. Return the customer ID and both canceled_at timestamps in ascending order.
  • For each merchant in a given month, estimate the uplift in average order value when a promo is applied versus not. Output merchant ID, promo and non-promo order counts, both AOVs, and the difference. Then explain how you would compute a 95% confidence interval for that difference using either a SQL-based bootstrap or a Python snippet.

“The null delivered_at edge case is the part I almost missed.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Apr 2026
DoorDash coding screen for a software engineer role. One algorithmic problem, pretty focused, nothing else to report on the process side.
  • Given two strings of equal length, determine whether you can make them identical using at most 2 character swaps within the first string.

“My first instinct was to find all the positions where the two strings differ and then reason about how many swaps it would take to fix them.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Apr 2026
DoorDash analytics engineer interview, got a coding question that was pretty clearly a sliding window problem once I sat with it for a minute. Nothing crazy but you do need to actually know your O(n) approaches cold.
  • Given an integer array and an integer k, find the maximum sum of any contiguous subarray with exactly k elements. Values can be negative. Expected time complexity is O(n).

“My first instinct was brute force, which I'm pretty sure they clocked immediately.”

View Post