DoorDash Interview Questions — Page 33

DoorDash·Software Engineer·Technical Phone Screen

Jun 2026

DoorDash coding screen, one question the whole time. Pretty focused session, nothing too wild, but the problem had a small wrinkle that tripped me up for a minute before I got back on track.

Given two equal-length strings and an integer k, determine if you can make the first string an anagram of the second by changing at most k characters.

“I knew frequency counting was the right move but fumbled the aggregation step.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

Jun 2026

DoorDash DS interview focused entirely on marketplace analytics, specifically how merchant variety affects consumer behavior and platform health. Pretty deep case with three connected parts that built on each other. The experimentation piece at the end was where things got real.

How would you define merchant variety or selection in a way that's actually measurable and operationally useful?
What metrics would you track to measure success of a merchant variety change, covering both the consumer side and the merchant side, along with any guardrail metrics?
Walk through how you'd design an experiment to test the impact of a change to merchant variety, including what unit you'd randomize on and how you'd analyze the results.

“This tripped me up more than it should have.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Jun 2026

DoorDash software engineer interview with a string manipulation problem. Pretty standard coding round, nothing too wild, but the problem has some edge cases that can trip you up if you're not careful.

Given a target string and a list of strings, return all entries from the list that could match the target string by swapping exactly one pair of characters.

“The base case where both strings are already equal tripped me up a bit.”

View Post

DoorDash·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

PM product sense round at DoorDash, just the one question but they really wanted you to dig into it.

You're a PM at Lyft. How would you go about improving ride quality?

“Scope is everything here and I didn't nail it fast enough.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at DoorDash for a software engineering role. The whole thing was one big question about designing a distributed cron job scheduler, and they wanted serious depth across basically every dimension of the system. Brutal but fair.

Design a distributed cron job scheduler that supports cron expressions, time zones including DST, high availability, horizontal scalability to millions of jobs, and exactly-once or at-least-once execution semantics.
How would you handle leader election and failover to ensure high availability in the scheduler?
Walk through how you'd implement idempotency and deduplication for job execution in this system.
How would you handle misfire scenarios, where a job misses its scheduled execution time, and what catch-up policies would you support?
Describe how you'd design retry logic with backoff for failed job executions.
How would you support job dependencies, where one job should only run after another has completed successfully?
How would you implement multi-tenant isolation and quota enforcement in this scheduler?
What failure modes would you plan for, specifically around clock skew, network partitions, and worker crashes, and how does your design address them?
How would you approach observability for this system, including metrics, logs, distributed traces, and alerting?

“This is the kind of question where you think you know where to start and then realize five minutes in that you've already painted yourself into a corner.”

View Post

DoorDash·Software Engineer·Onsite - System Design / Architecture

Jun 2026

DoorDash system design round, went pretty deep on a donation/charity campaign platform. The scope was bigger than I expected and I spent too long on the happy path before they pushed me on failure modes.

Design a time-bounded donation drive system that accepts donations from many concurrent users, tracks running campaign totals, and triggers matching or bonus rules when thresholds are hit.
How do you handle idempotency and exactly-once semantics for payment processing when users might retry a failed donation?
Walk through your approach to handling high availability and traffic spikes during a viral campaign moment.
How would you design the async messaging and fan-out for notifications like donor receipts, charity updates, and matching alerts?
How do you ensure correctness in money math across the system, and what does your reconciliation process look like?

“I started with the campaign lifecycle (create, start, end, payout) which felt natural, but I glossed over the matching rules too fast.”

View Post

DoorDash·Software Engineer·Hiring Manager Screen

Jun 2026

DoorDash hiring manager screen for a software engineering role, basically a deep technical project walkthrough that kept going way longer than I expected. They really do drill into every layer if you give them an opening.

Walk me through a technically complex project from your background, including why the problem was hard, what you personally contributed, the architectural decisions you made and what you ruled out, the trickiest parts you had to solve, the measurable impact, and what you'd change looking back.

“This is the whole interview, basically.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Jun 2026

DoorDash SWE phone screen focused on a pay calculation problem built around a sequence of delivery events. The interviewer skipped the basic part and went straight to a trickier interval-splitting variant. Pretty domain-specific but not unreasonable once you understood the schema.

Given a chronologically ordered list of delivery events for a single driver's day (each with a start time, end time, and type), compute the corrected total daily pay where any active delivery interval that overlaps a peak-hour window gets 2x pay for the overlapping portion. How do you split intervals at peak boundaries and handle edge cases like multiple peak windows or gaps?

“The schema clarification part took longer than I expected.”

View Post

DoorDash·Data Scientist·Technical Phone Screen

Jun 2026

DoorDash data science interview focused almost entirely on a deep experiment design case for the notifications team. It was one of the more technically demanding sessions I've had, covering everything from randomization strategy to long-term holdout design in a single extended problem.

How would you design an experiment to measure the incremental impact of increasing push notification frequency and/or using smarter send timing for order-related notifications? Walk through your randomization unit, exposure caps, time-of-day stratification, and how you'd control for interference from other channels like email and SMS.
What are your primary success metrics and guardrails for this notification experiment, and how do you aggregate them across both per-user and per-notification dimensions?
How would you measure the long-term effects of increased notification frequency, including novelty effects, user fatigue, and whether any lift you see in the first couple weeks actually persists?
Users in this experiment receive multiple notifications over the study period. How do you handle the repeated exposure problem and model diminishing returns or saturation effects in your analysis?
Walk through your power and MDE assumptions for this experiment, your stopping rules, and how you'd build a decision framework that weighs short-term conversion lift against potential long-term retention damage. What's your concrete rollback criterion?

“This is where I spent most of my time.”

View Post

DoorDash·Software Engineer·Technical Phone Screen

Jun 2026

DoorDash software engineer round focused on a spatial lookup problem that sounds straightforward until you actually have to nail the preprocessing and complexity analysis on the spot.

Given N cities with unique names and (x, y) coordinates, design a system that preprocesses the data so that for any query city, you can efficiently find the nearest city sharing the same x or y coordinate. Distance is the absolute difference along the non-shared axis, with ties broken by lexicographically smaller city name. Walk through your data structures, algorithms, and the time and space complexity for both preprocessing and each query.

“I started with the brute force and they let me finish before asking about efficiency, which felt generous.”

View Post