← Back to Directory

DoorDash interview notes, page 36 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·Technical Phone Screen

Jun 2026
DoorDash coding round centered on a deliberately broken round-robin load balancer. You had to find four specific bugs, then pivot to implementing consistent hashing with virtual nodes. Time pressure was real and they wanted actual code, not hand-waving.
  • You're given a buggy round-robin request distributor. Find and fix all the bugs in it.
  • Now extend your fixed round-robin to use consistent hashing. Implement a hash ring with virtual nodes and explain what happens to key assignments when a server is added or removed.

“There were four bugs total and I only spotted three on my own.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

Jun 2026
SQL-heavy technical screen for a DS role at DoorDash. Three questions all built on the same orders/delivery_requests schema, each one layering more complexity than the last. The kind of round where you think you're done and then they add a follow-up column to the output spec.
  • Given a parameterized time window and a late_threshold_minutes parameter, write SQL to find what percentage of completed orders were delivered late, where late means delivery time exceeded the threshold past order creation.
  • Write SQL to calculate what percentage of completed orders had at least request_threshold delivery requests, and also return the average number of requests per completed order. Orders with zero delivery requests must still appear in the denominator.
  • For completed orders, calculate the percentage that had at least one offer increase across sequential delivery requests, and compute the average percentage increase across all positive increase events. An offer increase is when a request's offer amount is higher than the immediately preceding request for the same order, ordered by time then request_id.

“Pretty approachable as a warmup.”

View Post

DoorDash·Frontend Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at DoorDash for a frontend role. Two topics, pretty focused: how you use AI tools in your actual work, and what you've done for your team beyond just shipping your own stuff.
  • Walk me through how you use AI tools or coding assistants in your day-to-day engineering work. Which tools, for what kinds of tasks, how did you measure whether they were actually helping, and how did you deal with risks like hallucinations or leaning on them too much?
  • Beyond your own individual deliverables, what specific contributions have you made to your team? Things like mentoring, improving processes, unblocking other teams, or helping with hiring and onboarding.

“This one has more layers than it looks.”

View Post

DoorDash·Software Engineer·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a bizops role at DoorDash and got a strategy question about where to put more money to grow the business. Pretty open-ended, which I wasn't fully prepared for.
  • If DoorDash had extra budget to allocate, where would you invest it to drive the most growth?

“I went straight to merchant acquisition and kind of talked in circles for a bit before landing on something more coherent about expanding into underpenetrated suburban markets.”

View Post

DoorDash·Machine Learning Engineer·Technical Phone Screen

Jun 2026
DoorDash MLE interview with a meaty operational scenario about wrong-order incidents on a food delivery platform. The question covered a lot of ground and felt more like a product case than a pure ML problem, which I wasn't fully expecting.
  • You work on a food delivery platform where customers sometimes receive wrong items. How would you maximize the reduction of wrong-order incidents, covering root cause diagnosis, process and technical changes, success metrics, trade-offs, and safe rollout?

“This question is wide.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at DoorDash with a product sense question about improving engagement on a real estate platform. Pretty standard format, one question, no major surprises.
  • How would you improve user engagement for a real estate app like Redfin or Zillow?

“Spent the first minute just trying to nail down what 'engagement' even means for a real estate app because it's not like social media where you want daily active users obsessively refreshing.”

View Post

DoorDash·Data Scientist·Take-home Assignment

Jun 2026
DoorDash data science take-home that was way heavier on SQL than I expected. Four problems, all PostgreSQL, all requiring CTEs and window functions, and the schema was deceptively simple but the logic got gnarly fast.
  • Given an exposures table and an orders table, compute the percentage of orders in a 7-day window that satisfy a compound filter (biker courier, cold temp category, subtotal at least 2000 cents) under two denominator definitions: one counting only orders tied to treatment-exposed units on that day, and one counting all orders regardless of exposure status.
  • Define a 'power day' for each unit-date as: at least 2 biker-cold orders in the trailing 7 days AND average subtotal on those orders is at least 2000 cents. What percentage of unit-days are power days under the same two denominator conventions?
  • Build a complete unit-day grid (including days with zero orders) for a 7-day window. For each unit and date, compute daily order count, cumulative orders, a 7-day rolling sum, day-over-day percent change, and a non-overlapping 7-day percent change using specific window frame definitions.
  • For each unit, identify dates where a boolean flag (whether a qualifying high-value biker-cold order exists that day) flips value. For each flip, return the unit, the date, the direction of change, the difference in 7-day rolling order counts before and after the flip, and the percent rank of that delta across all flip events.

“The two-denominator thing tripped me up more than I want to admit.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Jun 2026
DoorDash coding round for a software engineer role. The problem was a dasher pay calculator with a bunch of edge cases baked in. More involved than it looks on the surface.
  • Given a list of delivery events (dasher ID, pickup time, dropoff time, distance, tip, optional bonuses) and a configurable set of pay rules (base pay per order, per-distance rate, per-minute rate, tips, bonuses), write a program that calculates each dasher's total pay for a shift. You need to define and validate the input schema, handle overlapping deliveries and missing fields, round correctly to cents, group results by day and dasher sorted by ID, and write tests covering at least three different pay configurations.

“This one took me a while to fully parse.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

Jun 2026
A data science case interview at DoorDash focused entirely on one deep, open-ended question about diagnosing a drop in completed delivery orders in LA. It was the kind of question that sounds manageable until you're twenty minutes in and realize you've only covered half of what they wanted.
  • Completed delivery orders in Los Angeles have dropped noticeably over the past two weeks compared to historical trends and similar cities. Walk me through how you'd investigate this end-to-end, from confirming the drop is real all the way to proposing an experiment to test a fix.

“This one ate up the whole session.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

Jun 2026
DoorDash system design round, one big question about building a cashback system for reviewers. Dense problem with a lot of moving parts and I don't think I covered everything they wanted.
  • Design a cashback system that rewards users for writing reviews based on how many upvotes those reviews receive. Cover the data schema, idempotency for vote events, fraud prevention, eligibility rules, async processing pipeline, and reporting.

“This one sprawled fast.”

View Post