DoorDash Interview Questions — Page 20

DoorDash·Product Manager·Onsite - Behavioral / Leadership

May 2026

DoorDash behavioral round where they walked me through a resume project and kept poking at whether I actually did anything meaningful. Felt like an interrogation more than a conversation, but I think that was the point.

Walk me through a project from your resume in detail. Be ready for the interviewer to push back and suggest your contribution was smaller than you're making it sound.

“The tricky part wasn't describing the project, it was staying calm when they kept reframing my work as minor.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at DoorDash for a software engineer role. The whole thing was basically one giant question about building a donation platform end to end, and they kept pulling the thread on every answer I gave.

Design an end-to-end architecture and data model for a three-day online donation campaign platform where users submit personal info, select donation amounts across multiple organizations, and your service handles charging users and depositing funds into a company account.
Compare synchronous versus asynchronous payment flows and justify when you would choose async for a use case like this.
Walk through the full async payment workflow including the API layer, idempotency keys, queue, worker processing, retry logic with backoff, and dead-letter queue handling.
How do you guarantee idempotent charges when the same request might be retried multiple times due to network failures?
How would you handle failure scenarios, reconciliation, and reporting for a campaign like this?
How do you prevent duplicate donation submissions and handle the security and compliance requirements around PII and payment data?
What's your strategy for rate limiting, observability, and scaling the system to handle bursty traffic during a short campaign window?
How do you handle partial failures and eventual consistency when a single user's donation spans multiple organizations?

“I started with the data model because I figured that would anchor everything else, which worked okay but I skipped over some API contract stuff early that came back to bite me.”

View Post

DoorDash·Software Engineer·Onsite - Coding / Algorithms

May 2026

DoorDash software engineer coding round, one meaty algorithm question that spiraled into a bunch of follow-ups I was not fully prepared for. The core problem seemed familiar but the depth they wanted was something else.

Given an integer array that may contain negatives and duplicates, modify it in place to produce the next lexicographically greater arrangement. If no greater arrangement exists, wrap around to the smallest (ascending) order. Target O(n) time and O(1) space.
Prove why this algorithm produces exactly the next arrangement without skipping any. Why does swapping the pivot with the correct neighbor and reversing the suffix guarantee correctness?
How does your solution handle edge cases: duplicate values in the array, arrays already in descending order, single-element arrays, and empty arrays?
Does the algorithm change at all when the array contains negative numbers?
Generalize the solution so that 'next arrangement' is defined by a custom comparator rather than natural integer ordering. How would you adapt the algorithm?
For very large arrays, what are the practical performance considerations around memory access patterns? And walk me through a test suite you'd write for this.

“I knew the general shape of the algorithm going in, find the rightmost dip, swap with the next bigger element to the right, reverse the suffix.”

View Post

DoorDash·Software Engineer·Onsite - Behavioral / Leadership

May 2026

Behavioral round at DoorDash for a software engineer role. Three questions, all pretty meaty, the kind where you need a real story and not just a vague answer about teamwork.

Walk me through a challenging project you led. What made it hard, how did you handle trade-offs, and what was the actual impact?
Tell me about a time you dealt with a major product issue. How did you detect it, triage it, find the root cause, communicate with stakeholders, and prevent it from happening again?
Describe a situation where you gave or received constructive feedback. How did you prepare, what happened in the conversation, and what changed afterward?

“The trade-offs part is where I think I underdelivered.”

View Post

DoorDash·Machine Learning Engineer·Technical Phone Screen

May 2026

DoorDash MLE interview that went deep on experimentation theory. One long question that covered basically everything you'd ever need to know about A/B testing, and I mean everything. Felt like a stats oral exam more than a typical ML screen.

Walk me through A/B testing from start to finish: setting up hypotheses, picking metrics, calculating sample size and power, choosing the right statistical test, interpreting results, and then talk through the major pitfalls like peeking, multiple comparisons, novelty effects, network interference, Simpson's paradox, and sample ratio mismatch. Also briefly compare frequentist and Bayesian approaches.

“This was basically the whole interview in one question.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026

Analytics Engineer screen at DoorDash, basically one meaty SQL question the whole time. The problem was well-scoped but had enough layers to trip you up if you weren't careful about UTC handling and window functions.

Given a users table and an app_events table for a fitness app, write SQL to return one row per UTC calendar day for the last 30 days, showing the count of distinct non-test users with at least one event (DAU), plus a 7-day rolling average of that DAU ordered by date.

“The join and filter parts were fine, excluding test users is just a WHERE clause.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026

DoorDash software engineering interview with a meaty algorithmic design problem centered on courier pay calculation. Three layers of complexity, each building on the last, and they expected you to drive the structure yourself rather than just code to a spec.

Design a function that calculates total courier pay across a set of delivery orders, where each active minute pays rate multiplied by the square of how many orders overlap in that minute.
Extend your solution so that store-wait time (the interval between a courier arriving at and picking up from a store) is paid at a flat per-minute rate for that order only, without affecting or being affected by the overlap multiplier for other orders.
How would you efficiently support configurable peak-hour windows where the per-minute rate is doubled?

“The quadratic pay rule tripped me up at first.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

May 2026

DoorDash data science interview with a product analytics case centered on a real operational problem. The question was meaty and covered a lot of ground, which I wasn't fully prepared for.

DoorDash is seeing a surge in complaints about food arriving cold. How would you diagnose the root cause, what metrics would you track, and how would you design an A/B test to validate a fix?

“This question is three questions stitched together and I didn't realize that until I was halfway through the diagnosis part.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

DoorDash system design round that was heavier than I expected. Two big questions back to back: a classic distributed notification system design and then a full walkthrough of my own past project architecture with follow-ups that got pretty deep.

Design a scalable notification system that handles real-time and scheduled messages across email, push, and SMS. Walk through the components, data flow, storage layer, how you handle failures, and your scaling approach.
Draw and explain the end-to-end architecture of a past project you worked on. Cover the services involved, databases, how components communicate, and be ready for detailed follow-up questions on domain-specific decisions.

“This felt manageable at first but the failure handling part is where I started rambling.”

View Post

DoorDash·Product Manager·Hiring Manager Screen

May 2026

Interviewed for a PM role at DoorDash and got hit with a classic resourcing prioritization question. Short and to the point, not a lot of fluff in the process.

How do you decide what to prioritize when you don't have enough resources to do everything?

“I rambled a bit about tradeoffs and impact vs effort before finding my footing.”

View Post