DoorDash Interview Questions — Page 5

DoorDash·Data Scientist·Technical Phone Screen

Apr 2026

DoorDash data scientist interview with a product analytics case focused on mobile web users who never convert to the native app. The question was meaty and required thinking through funnel measurement, experiment design, and incentive structures all at once.

A large portion of users place orders through mobile web but never install the app. How would you evaluate the current funnel from web order to app install, and what experiments would you design to improve that conversion rate?

“I started with cohort definitions which felt right, but I got a bit tangled trying to scope the baseline metrics while simultaneously pitching experiment ideas.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

Apr 2026

DoorDash data science interview that went deep on ML system design for delivery prediction. The whole thing was basically one long case study and it covered way more ground than I expected, from feature engineering to deployment guardrails.

How would you define the target variable for a late delivery prediction model, and how would you structure a time-based train/validation/test split to avoid leakage?
What are at least 10 production-safe features you would engineer at order-creation time for this late delivery model?
Identify at least five leakage hazards in this dataset and explain how you would eliminate each one.
Which evaluation metrics would you use for both ranking and calibration, and how would you build a cost matrix to justify operational thresholds?
Walk through how you would ramp this model to production: shadow mode, treatment gating, A/B testing with guardrails, drift monitoring, and recalibration strategy.
How would you handle cold-start problems for new restaurants or new cities, and how would you account for seasonality in the model?

“The target definition sounds obvious until you realize there are edge cases.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

Apr 2026

System design round at DoorDash for a software engineer role. The whole thing was one big scenario about building a charity donation backend, and it went pretty deep into payment flows, data modeling, and operational edge cases. More breadth than I expected for a single question.

Design the backend for a 3-day charity donation event supporting millions of donations, ~$100M total volume, 10 charities, and a single third-party payment API. All funds go into one company account and the CFO manually writes checks to charities afterward.
How would you handle traffic spikes during the final hours of the event, and what does your architecture need to support that?
Walk through how you'd reconcile your internal donation records against what the payment provider actually processed.
How would you model failed charges and refunds in your data schema?
What does the audit trail look like for the manual step where the CFO issues checks to charities after the event?
How would you generate per-charity reporting throughout and after the event?

“This felt manageable at first and then the follow-ups kept coming.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Apr 2026

A case-style technical screen for an Analytics Engineer role at DoorDash. The whole thing was one big open-ended problem about building a fair compensation model for support agents, which sounds straightforward until you actually try to work through the fairness and incentive pieces under pressure.

You're a data scientist embedded in a customer support team with access to all operational data. Design a methodology to allocate salary or a bonus component to each support agent based on the volume and quality of complaint tickets they resolved. Cover which metrics you'd use beyond raw ticket count, how you'd control for assignment bias and ticket difficulty, how you'd combine everything into a single score, and how you'd validate the system is fair and actually incentivizes the right behavior.

“This one took me a minute to even figure out where to start.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

Apr 2026

System design round at DoorDash for a software engineering role. The whole session was built around one big, layered problem: designing a review and voting system for an e-commerce platform, with rewards tied to upvote counts. A lot of ground to cover in one question.

Design a scalable review system for an e-commerce platform where users can post reviews, upvote or downvote them, and authors earn rewards based on upvote counts. Cover the APIs, data schema, counter architecture, ranking, abuse prevention, and reliability.

“This one sprawls.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

Apr 2026

DoorDash DS interview, one meaty case question that sprawled across cost decomposition, experiment design, and a ship/no-ship tradeoff. Felt like three interviews squeezed into one prompt. The depth they expected was a lot.

Break down the operational cost per order for a food delivery platform using a driver tree, and define cost per order and contribution margins across different city, restaurant, and time-of-day segments.
Identify the top three levers to reduce costs in high-cost markets without hurting conversion rates or on-time delivery, and quantify the expected impact using historical data or past experiments.
Design an experiment to test a cost-reduction intervention (such as dynamic batching thresholds or adjusted courier incentives). Include randomization unit, stratification, statistical power, guardrail metrics, and how you'd prevent supply-side contamination.
What does your monitoring plan look like for catching unintended side effects after launching a cost-reduction change, and what would trigger a rollback?
If a tested change saves $0.35 per order but causes a 0.6 percentage point increase in late deliveries, how do you decide whether to ship it, iterate, or kill it?

“I started rattling off cost buckets which felt fine until I realized I hadn't actually structured it as a tree.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Apr 2026

DoorDash SWE interview focused on a tree diameter variant that kept evolving into harder and harder follow-ups. The core problem was manageable but the online update extension pushed things into territory I wasn't fully prepared for.

Given a binary tree where the alive nodes are defined as the leaves, write an O(n) time and O(h) space algorithm to find the maximum number of edges between any two alive nodes.
Now each node has an arbitrary boolean alive flag instead of just leaves being alive. Compute the maximum distance between any two alive nodes, where intermediate nodes along the path can be anything.
Support online updates where a node's alive flag can be toggled at any time, and after each update you need to return the current maximum distance between alive nodes.

“This is basically tree diameter and I'd seen it before, so the DFS approach came pretty naturally.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

Apr 2026

DoorDash DS interview with a meaty marketplace diagnostics question. The whole session was basically one long case study broken into four parts, and it went deeper than I expected for a single question.

DoorDash sees a 10% week-over-week drop in completed deliveries in Los Angeles. How would you identify, attribute, and quantify the key drivers behind this decline? Walk through potential root causes across supply, demand, merchant, product, external, and measurement dimensions, then outline how you'd test each hypothesis, decompose the drop quantitatively, and handle causal inference when A/B testing isn't an option.

“This one sprawled in ways I didn't anticipate.”

View Post

DoorDash·Data Scientist·Onsite - Cross-functional / Panel

Apr 2026

DoorDash data science onsite with a heavy operations and strategy flavor. The whole thing was basically one long case about resource constraints, stakeholder politics, and what happens when something breaks mid-sprint. More PM-adjacent than I expected for a DS role.

You're the only data lead supporting three concurrent initiatives with fixed engineering capacity and a mandatory compliance lead time. How do you prioritize and sequence the work? Walk through your framework, assumptions, and decision rule.
For each of the three initiatives, what's the minimal viable scope that still preserves the expected business impact given the time and resource constraints? Where would you cut and why?
Draft a stakeholder communication plan covering what you commit to each leader, what slips, and how you handle tradeoffs. Include a sample status update and a script for telling someone their initiative is being deprioritized.
A critical data quality incident hits on Oct 25 and costs half an engineering week to fix. How do you update your plan, renegotiate deadlines, and keep stakeholder trust intact?
How would you define success criteria for your own performance in this role? What leading indicators, risks, and contingencies would you track?

“This is where I spent most of my energy and still feel like I fumbled the landing.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

Apr 2026

DoorDash PM interview with a cross-company product sense question, asking me to step into an OpenTable PM's shoes and think through post-reservation pain points. Pretty classic product sense setup but the specificity of the scenario kept it from feeling totally routine.

You're a PM at OpenTable. How would you go about prioritizing improvements to the worst experiences users have after they've already made a reservation?

“The post-reservation framing is what makes this interesting.”

View Post