DoorDash Interview Questions — Page 16

DoorDash·Software Engineer·Technical Phone Screen

May 2026

Technical phone screen for a software engineer role at DoorDash. One coding problem, grid-based BFS stuff, felt pretty standard but there were enough wrinkles to trip you up if you weren't thinking carefully about the approach from the start.

Given a 2D grid with source cells and target cells (and possibly impassable walls), return a matrix where each cell contains the shortest 4-directional distance to the nearest source, or -1 if unreachable.

“My first instinct was to BFS from each source separately and merge results, which works but is painfully slow if there are many sources.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026

DoorDash software engineer interview with a tree problem that had a tricky follow-up, plus a design question thrown in. Pretty standard coding round but the follow-up on the tree problem is where things got interesting.

Given a binary tree, find the maximum distance between two 'alive' nodes, where alive nodes are initially defined as the leaves. Follow-up: generalize so that the set of alive nodes can be any arbitrary subset.
Design a file system that supports creating paths and associating values with them.

“The base version is basically a diameter-of-tree problem restricted to leaves, which I'd seen before so I got through it okay.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

DoorDash system design round focused entirely on the infrastructure side of a recommendation system, no ML modeling involved. Pretty deep dive, they wanted specifics on caching layers, feature stores, and rollout strategies, not just hand-wavy architecture diagrams.

How would you design the candidate retrieval and ranking pipelines for a large-scale recommendation system?
Walk me through how you'd implement multi-tier caching for a recommendation system, covering user features, item features, and final results.
How would you design a feature store to support both online serving and offline model training for a recommendation system?
How do you handle traffic scaling and high QPS for a recommendation serving system, and what are your latency budgets at each layer?
How would you manage fan-out in a recommendation system where a single request triggers many downstream lookups?
How do you roll out a new recommendation model version without disrupting live serving?

“I started with a two-stage setup, approximate nearest neighbor search for retrieval then a lighter ranker before the heavy model.”

View Post

DoorDash·Data Scientist·Onsite - Behavioral / Leadership

May 2026

Behavioral round at DoorDash for a data scientist role, focused heavily on how you work with non-technical people and how you decide what to work on when everything feels urgent. Pretty standard stuff but the prioritization angle had some teeth to it.

Tell me about a time you got a non-technical stakeholder to actually act on your recommendation. What did you do to bring them along?
When you have multiple data science projects or requests competing for your time, how do you decide what gets done first?

“I went with a story about convincing a product manager to delay a launch based on some retention modeling I'd done.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at DoorDash focused on payment infrastructure, specifically a deep dive into storage layer decisions. The question was deceptively broad and I felt like I was playing catch-up the whole time trying to cover enough ground without going too shallow on any one piece.

You're designing a payment system. For each component, which database would you choose and why? Walk through the trade-offs across relational stores, caches, document stores, wide-column databases, and append-only ledgers.

“This felt like five questions duct-taped together.”

View Post

DoorDash·Software Engineer·Onsite - Behavioral / Leadership

May 2026

DoorDash software engineer interview with a mix of behavioral and product thinking. Two questions that seem simple on the surface but both have some depth to them if you're not prepared.

Tell me about a significant mistake you made as a software engineer and how you handled it.
A customer places a food order and then the restaurant says one of the items is out of stock. Walk me through how you'd handle that situation.

“They want the full arc here: what happened, who got hit by it, what you actually did in the moment, and what changed after.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

May 2026

DoorDash system design round, one big question that sprawled into like six different topics. Felt manageable at first and then the scope just kept expanding.

Design an HTTP aggregator service that fans out requests to three downstream services in parallel and returns a single merged JSON response. Cover the request/response schema, status codes, timeout strategy, error handling with retries and circuit breaking, partial failure fallbacks, concurrency model, observability, and how you'd test it.

“This is the whole interview in one question.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM interview at DoorDash, product sense round focused on membership and subscription experience. Single question but it had some real depth to it once I started pulling on the thread.

You're the PM for a rideshare app's membership program. How would you identify the most negative member experiences?

“I went straight to data signals, cancellation rates, support tickets, that kind of thing.”

View Post

DoorDash·Frontend Engineer·Online Assessment (OA)

May 2026

DoorDash frontend coding round on HackerRank. You get a mock API with product data and have to render it in a flexbox grid that matches a mockup exactly. Most of the CSS is handed to you, so the real work is in the details.

Fetch product data from a mock API and render it in a flexbox grid layout that matches a provided mockup, including correct price formatting with currency symbol, decimal places, and thousands separators.

“The CSS being mostly provided felt like a gift until I realized the actual gotcha was the JSON shape.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

May 2026

DoorDash software engineer interview with a deep-dive project presentation round. You pick one project you're proud of and basically defend every decision you made for however long they want to go.

Pick a technically meaningful project from your background and walk through it in depth: the problem it solved, your specific role, the design decisions you made and what you considered instead, the trade-offs involved, technical challenges you hit and how you resolved them, measurable impact, and what you'd change looking back.

“This is the whole interview basically.”

View Post