DoorDash Software Engineer Interview Experience — Four Rounds: Debugging, Food Review Design, AI Coding with a DAG, BQ

DoorDash·Software Engineer·Nov 2026
Onsitemedium

Round 1, debugging: it was about the dasher random pick problem. There are similar ones on the forum. I did this one badly and it took me way too long. The follow-ups were about what to watch out for when pushing changes to production, things like that. They didn't ask about consistent hashing.

Round 2, system design: the food review question.

Design Food Review
Reward System
"Design a system that allows DoorDash's consumers to add reviews on ordered food items. Consumers will earn rewards ($) based on the quality of the review."

Round 3, AI coding: a repeat from the forum, no starter code, and it involves a DAG.

At DoorDash, when something goes wrong with an order — delayed, lost, undelivered — support agents need to respond consistently. We want a system that can evaluate an order's current state and automatically decide what action to take: issue a refund, close the request, escalate, etc.
Our system would function by querying a real API that you build to represent order status, checking the order status, and following a rule set defined as a directed acyclic graph to make a decision.
An example DAG could look like this:

Start Node
│
▼
Check if the order is late?
├── Yes ──▶ Issue Refund ──▶ End
└── No  ──────────────────▶ End

Round 4, BQ: about the same as the DoorDash behavioral round questions listed on the forum.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
DoorDash
Role
Software Engineer
Rounds
Onsite
Difficulty
medium
Interview date
Nov 2026
Questions from this interview
2 questions

Related interview experiences

Explore more interview rounds, questions, and outcomes.

Browse interview experiences