DoorDash's engineering loop is structured around a small, well-known question bank and three onsite specialties: CodeCraft (production-style coding, sometimes AI-assisted), Debugging (fix a broken Dasher-adjacent service), and System Design paired with a Domain / Deep-Dive round. A tech screen (often a DoorDash-flavoured LeetCode-tagged question) gates the onsite. The onsite is typically CodeCraft + Debugging + System Design/Domain + Hiring-Manager or Values. As of 2026, DoorDash publicly announced it is replacing traditional algorithmic coding rounds with 60-minute AI-assisted engineering working sessions where candidates use Cursor/Copilot/Claude Code on realistic DoorDash-shaped tasks. Note: DoorDash's Dasher (delivery driver) sign-up is NOT a conventional interview - it is an app-based application, ID check, and background check with no interview round.
These 10 writeups cover software engineering, data engineering, ios engineering roles. All of them were posted under a forum handle, so we could not verify the authors’ identities.
1Phone screen (coding)Phone screenA variation of LeetCode's Binary Tree Maximum Path Sum, with the interviewer rewording nodes as domain concepts and asking for follow-ups on edge cases and complexity.Covered: Trees, Data structures & algorithms
2System Design + DomainSystem designDeep dive into the candidate's most challenging project and a specific hard problem, then a design of a Yelp-style reviews system with the usual functional/non-functional negotiation.Covered: System design, Past projects, API design
3CodeCraft (coding)TechnicalGiven a stream of Dasher pickup and dropoff events (timestamp, status), compute how much a Dasher should be paid, with a concurrency multiplier that increments as the Dasher takes on more concurrent orders and decrements as they drop them off. Extensive edge-case follow-ups.Covered: Low-level design, OOP, Domain knowledge
4DebuggingTechnicalFind and fix a bug in a Dasher-assignment class that is effectively a buggy insert/delete/getRandom in O(1) implementation - a random index is popped from a map, then the last entry is meant to be swapped in, but the length check happens after the pop and off-by-one corrupts the map.Covered: Debugging, Data structures & algorithms
Software Engineer 2, Backend (Pune)
Not selected
Experienced. 5 rounds. Shared by Anonymous on leetcode, 2025-01-31
1Technical ScreeningPhone screenA graph/DSU problem (Number of Provinces). The interviewer accepted a DFS solution and asked about time/space complexity of DFS vs DSU.Covered: Graphs, Data structures & algorithms
2Coding (DSA)TechnicalNext Greater Element III, with the expectation to first walk a brute-force recursive solution and then the optimal one, both implemented in the round.Covered: Arrays & strings, Data structures & algorithms
3System Design and Domain KnowledgeSystem designDiscussion of current project followed by designing a Review System. Clarified functional and non-functional requirements. The interviewer offered little guidance during the design walkthrough.Covered: System design, Past projects
4Coding (DSA)TechnicalSearch Suggestions System - proposed sorting plus binary search and a trie, compared complexities, implemented the trie version and walked edge cases.Covered: Trees, Data structures & algorithms
5ValuesBehavioralIntroductions, discussion of current project, and standard behavioural questions.Covered: Behavioral, Past projects
Backend SDE-2 equivalent (India)
Not selected
Experienced. 4 rounds. Shared by Anonymous on leetcode, 2026-05-23
1Recruiter callHiring managerZoom call with the recruiter walking through the JD and India teams, background chat about experience and interest.Covered: Behavioral
2Tech screenPhone screenCoding problem involving 2D coordinates, solved with a hash map and binary search to find the nearest coordinate.Covered: Arrays & strings, Data structures & algorithms
3Bug Bash (Debugging)TechnicalSmall codebase provided in C++ (Java/Python/Go were the offered languages. JavaScript was not). Read the code, run it, spot and fix bugs, then a high-level discussion of scaling and multithreading options.Covered: Debugging, Concurrency
4System Design and DomainSystem designAfter a most-challenging-problem deep dive, designed a Job Scheduler. The interviewer pushed for the main design early, then repeatedly probed on missing tables, indexes and partition keys.Covered: System design, DBMS, API design
Software Engineer, Onsite (USA)
Outcome not shared
Experienced. 1 round. Shared by Anonymous on leetcode, 2025-12-08
1AI CodeCraftTechnical60-minute AI-assisted coding session using a local IDE with Copilot/Cursor/Claude Code. Task: extend a workflow-engine skeleton that automates DoorDash self-help tickets (e.g. late order, missing item). Given dataclasses for OrderModel, a MockDoorDashAPI, a Node/NodeType/Workflow DAG and a stubbed WorkflowEngine. Implement the stubs to pass provided tests, then add partial-refund logic when the order is only slightly late, then investigate and improve a slow 10-20s execution path. The panel explicitly evaluates prompt-engineering ability and rewards using AI as an assistant rather than as a crutch.Covered: Low-level design, API design, Debugging, OOP
Software Engineer, Onsite System Design (USA)
Outcome not shared
Experienced. 1 round. Shared by Anonymous on leetcode, 2025-12-18
1System DesignSystem designOne-hour design of a charity-donation app: 10 charities, a 3-day event, ~10M donations and ~$100M expected. Frontends already exist. Integrate the Braintree Payments REST API, handle a spike load, notify users on successful donation, and reason through failure modes and retry/idempotency. Disbursement is out of scope (CFO cuts a manual check afterwards).Covered: System design, API design, Scalability
Software Engineer, Onsite Debugging (USA)
Outcome not shared
Experienced. 1 round. Shared by Anonymous on leetcode, 2025-12-05
1Debugging (Dasher Assignment Service)TechnicalA single-file mock Dasher-assignment service with classes for User, Dasher, a stubbed RemoteDeliveryRecordingService, and a DeliveryAssignmentService with addDasher, pickKey (random index), adjustMap and pickDasher already implemented. Read the business spec, find the small but important logic bugs, and improve the code. Follow-ups on additional test cases and a cleaner implementation. No AI allowed for this round.Covered: Debugging, OOP, Testing
Senior Software Engineer (offer, ~7 YOE)
Received an offer
Experienced. 3 rounds. Shared by Anonymous on leetcode, 2026-02-06
1Company-specific coding prepTechnicalAuthor reports DoorDash uses a very small CodeCraft question bank (roughly two or three questions), so targeted practice from recent interview writeups is more efficient than volume LeetCode.Covered: Data structures & algorithms, Low-level design
2System DesignSystem designPractised against the company's recently asked SD questions and rehearsed the interview flow with an AI stand-in interviewer.Covered: System design, Domain knowledge
3BehavioralBehavioralRead DoorDash's core values and prepared STAR-style stories mapped to each.Covered: Behavioral, STAR stories
What DoorDash is hiring for now
439 open roles in our index. Advertised pay floors run $59k to $160k (median $105k, from 426 postings that state pay).
DoorDash's engineering loop is structured around a small, well-known question bank and three onsite specialties: CodeCraft (production-style coding, sometimes AI-assisted), Debugging (fix a broken Dasher-adjacent service), and System Design paired with a Domain / Deep-Dive round. A tech screen (often a DoorDash-flavoured LeetCode-tagged question) gates the onsite. The onsite is typically CodeCraft + Debugging + System Design/Domain + Hiring-Manager or Values. As of 2026, DoorDash publicly announced it is replacing traditional algorithmic coding rounds with 60-minute AI-assisted engineering working sessions where candidates use Cursor/Copilot/Claude Code on realistic DoorDash-shaped tasks. Note: DoorDash's Dasher (delivery driver) sign-up is NOT a conventional interview - it is an app-based application, ID check, and background check with no interview round.
What topics does DoorDash test in interviews?
Commonly reported topics include Team roadmap, System design, Debugging, Trees, Graphs, Dynamic programming.
These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.