DoorDash Interview Questions — Page 10

DoorDash·Software Engineer·Onsite - Behavioral / Leadership

May 2026

Behavioral round at DoorDash for a software engineering role. Two heavy questions back to back, both requiring pretty specific stories about conflict and failure. Not a lot of small talk, they got right into it.

Tell me about a time you disagreed with a teammate or stakeholder. What caused the disagreement, what options were on the table, how did you get to alignment, and what happened in the end?
Describe a significant mistake you made. What led to it, how did you fix it, and what did you actually change about your behavior or process afterward? What shows you've grown since?

“This one's deceptively layered.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026

DoorDash system design round for a software engineer role, focused on extending an existing pay calculation system. Two parts: adding peak-hour bonus logic, then handling bad input. Pretty involved for a single session.

You have a Dasher pay calculator. Extend it to apply a peak-hour bonus when a delivery falls within a configured time window. How do you handle multiple overlapping windows, and what rule governs which bonus applies?
How would you handle invalid or malformed input in the pay calculator? Think missing fields, bad timestamps, negative values, and currency mismatches. What's your policy: reject, fall back, or compute partial pay?

“I went with highest-bonus wins and documented it as the policy, which felt cleaner than first-match since first-match is basically arbitrary depending on list order.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM interview at DoorDash with a product sense question about handling bad user experiences on a third-party platform. Short and focused, not much else to go on.

How would you mitigate negative experiences on OpenTable?

“I spent the first minute just trying to figure out what angle they wanted.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026

DoorDash AI coding round for a software engineer role. You write code live using an AI assistant on a shared screen, which sounds easy until you realize the whole point is how you manage the AI, not whether the code compiles.

Given a skeleton implementation of a DAG-based processing system, implement the order timeout refund flow where the next node depends on whether a timeout occurred.
Extend the node-based system to support additional flow types such as partial refund, cancellation, and others.

“The setup was a shared screen with a HackerRank-style environment.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM interview at DoorDash with a product strategy question about growing engagement on a music platform. Pretty short interaction, not much context given about the round or outcome.

If you were the PM for Spotify, how would you go about increasing user engagement?

“Weird question to get at DoorDash but whatever.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

May 2026

DoorDash data science interview with a pretty intense stats-heavy question on experiment design. One question, lots of moving parts, felt like a take-home problem crammed into a live setting.

You have a baseline cold-food complaint rate of 3.50%, and all such orders currently get full refunds. A thermal-bag pilot is expected to cut that rate by 10% relatively (down to 3.15%). Using a two-sided z-test for two proportions at 95% confidence and 80% power: calculate the minimum sample size per arm for equal allocation, estimate the minimum test duration if only 60% of 200k daily orders are eligible and traffic is split evenly, and then redo the sample size calculation for a 6% relative reduction target instead. State your assumptions and round to the nearest 100 orders and 0.5 day.

“This one had three sub-parts and I think I handled (a) okay but fumbled the transition to (b).”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026

DoorDash software engineer interview with a tree diffing problem that sounds deceptively manageable until you actually try to nail down all four change conditions cleanly. The parent-tracking piece is what trips people up.

Given two N-ary trees representing old and new versions of some structure, where each node has a string key, integer value, and list of children, write an algorithm to count how many nodes are considered 'changed'. A node is changed if it was deleted, added, has a different value for the same key, or has the same key and value but a different parent than before. Discuss time and space complexity.

“The deleted/added/value-changed cases came to me pretty fast.”

View Post

DoorDash·Software Engineer·Onsite - Behavioral / Leadership

May 2026

Behavioral round at DoorDash for a software engineering role. Pretty much the whole thing was project and teamwork stories, back to back, with follow-ups that pushed for specifics whenever my answers got vague.

Walk me through a recent project you led or made a major contribution to. What were the goals, what was your role, and what did it actually move?
Tell me about a time your team wasn't aligned or there was real conflict. How did you handle it?
Describe a situation where you had to collaborate with people outside engineering, like product or QA or SRE, and had to make trade-offs to get something shipped.
Tell me about a failure or significant setback. What happened, what did you take from it, and what changed in how you work?
What's a piece of constructive feedback you've received that stuck with you, and how did you actually change because of it?

“I had a solid story prepped but fumbled the measurable impact part.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

May 2026

DoorDash DS interview with a single very deep open-ended case question about measuring and forecasting the price gap between their platform and in-store menus. No behavioral rounds mentioned, just this beast of a problem. Left the room feeling like I'd only scratched the surface.

Design an end-to-end analysis to measure and forecast the gap between DoorDash platform menu prices and the same items' in-store prices. Cover how you'd collect and clean the data, build a price index, match identical items across sources, quantify uncertainty without an A/B test, forecast the gap using exogenous drivers like CPI and fuel costs, and size the study including minimum detectable effect under clustering and autocorrelation.

“This question is five questions duct-taped together and they want you to treat it like one coherent story.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

May 2026

DoorDash data science interview focused entirely on experiment design and metrics for three Dasher compensation and engagement initiatives. Pretty dense case-style questions, less coding, more product analytics and stats. Felt like a product sense round dressed up as a DS interview.

How would you design an experiment to evaluate a Top Dasher program that routes better orders to high-performing couriers? What metrics and success criteria would you use?
How would you precisely define Dasher response rate, what factors could move it, and how would you structure and analyze an A/B test for an extra pay incentive?
Compare a per-order versus per-time compensation model for Dashers. What are the trade-offs and how would you run an empirical test to decide between them?

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

View Post