DoorDash interview, from Code Craft to the AI-assisted working session.

DoorDash's loop runs from a recruiter call and a technical screen to an onsite of an AI-assisted working session, Code Craft, debugging, system design and a hiring manager round, as candidates from 2024 to 2026 consistently describe it. DoorDash publishes no list of stages, but its own posts describe the AI session and its rules on AI.

The DoorDash AI-assisted coding interview is a 60-minute working session where you extend a small real system on your own machine, with your own editor and an AI coding agent, while explaining your choices. DoorDash announced it in March 2026 as the replacement for its traditional coding rounds, and says free tiers of Cursor, Claude Code or Codex are enough. It scores how you get oriented, how you use AI and verify its output, how you debug, how you manage scope and how you communicate trade-offs. Here is what to prepare.

• Set up before the day: DoorDash sends a candidate guide, and says some candidates in its pilot arrived without a configured editor. Install your editor and AI agent, sign in, and run a small project end to end the day before. One candidate who used it in December 2025 put it plainly: a ChatGPT tab is not enough.
• The tasks: DoorDash names an order dispatch system, a smart menu composer and a support request resolution system. Candidates report a support or refund workflow built as a graph of steps. Expect a few small services, and spend the first minutes reading how they fit together.
• Run real services if they ask for them: One 2026 candidate built mocked classes when the interviewer wanted real services running locally on separate ports, and was turned down. Ask early whether the services should actually run and talk over HTTP.
• Use AI out loud: DoorDash allows one-shotting a problem, but scores whether you check what the agent wrote. Say what you asked it for, read the diff, run the tests, and take over when it goes wrong.
• Scope like a working engineer: DoorDash says finishing every task matters less than a tight loop and good judgement, though speed still counts. Get one path working, then extend it, and say what you would do next with more time.
• Explain trade-offs in DoorDash terms: Its post asks for trade-offs in terms of the impact on merchants, Dashers and consumers. When you choose, say who it helps and who it costs.

Candidates still report Code Craft and Debugging rounds after March 2026, so ask your recruiter which rounds your loop has. Outside this session, DoorDash's rule is no AI in live interviews unless the interviewer invites it.

Code Craft is DoorDash's practical coding round: an API-style problem from its own business, graded on code that is maintainable, testable and handles failure, which DoorDash's prep kit calls not a Leetcode-style interview. The debugging round hands you an existing service with bugs to find and fix. Both are reported from 2024 to 2026, and several 2026 candidates found Code Craft vague going in, so here is what they describe.

• The Code Craft problems: Dasher pay (a rate per minute, a higher rate with several active orders), a payments service for Dasher payouts, and spotting which items changed between two versions of a menu tree. One senior candidate in 2026 thought the question bank was small. Practise one of each in your interview language.
• What Code Craft grades: Structure you could hand to a teammate, tests for the edge cases, and handling a slow or failing service; one 2025 follow-up asked what happens if the upstream service has high latency. Write the tests, even briefly.
• The debugging round: A service such as Dasher assignment or a random Dasher picker, with bugs that show up under concurrency, and follow-ups on running it across machines. Reported as no-AI, on HackerRank, where one candidate found the output console cut off. Reproduce first, then fix.
• Languages: One 2026 candidate found JavaScript was not offered and interviewed in another language. Confirm the language list with your recruiter before you prepare.

DoorDash's older prep post (2021) still describes its rubric: fundamentals, coding and communication, with ambiguous questions on purpose and debugging valued highly.

DoorDash's own posts name what it scores, and the same things come up in what candidates report:

• Getting oriented fast in code you have never seen, and saying what you found
• Using AI with judgement: checking what it writes, and knowing when to take over
• Practical code that is maintainable, tested and handles failures
• Debugging from evidence: a minimal reproduction, the logs, then the fix
• Trade-offs in DoorDash's own terms, the impact on merchants, Dashers and consumers

DoorDash asks behavioural questions about decisions you made and why, and its practical problems keep coming back to Dashers, orders and menus. The questions here follow what candidates report and what DoorDash's posts say it scores.

Levels.fyi medians for DoorDash software engineers in the United States, from 1,249 submissions, read on 13 October 2026; packages reach about $909K at the top. Levels.fyi puts E3 at about 0 to 1 years of experience and E4 at about 4 to 5. Ask how the stock vests and whether there is a refresh; our big tech RSU guide covers what to ask.

1. Read the prep kit your recruiter sends and ask which rounds your loop has: the AI session, Code Craft, debugging, or a mix.
2. Set up your editor and an AI coding agent the day before and run a small multi-service project end to end.
3. Practise one Code Craft problem from DoorDash's world, such as Dasher pay, with tests and a slow upstream service.
4. Practise debugging a race condition in code you did not write: reproduce it first, then fix it.
5. Practise breadth-first search on a grid, such as the nearest Dasher, and say how it scales.
6. Prepare one system design in DoorDash's product, such as reviews or notifications, with the trade-offs for merchants, Dashers and consumers.
7. Prepare the reasons behind every decision in your two main project stories; the hiring manager will ask.

This guide covers DoorDash's software engineering hiring in the US. Wolt, which DoorDash owns, hires in Europe with its own process. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Netflix, Google Zurich or Meta London? Their guides follow the same format, from the first screen to the offer.

• 01DoorDash Careers, why DoorDash is rebuilding its engineering interviews around AI (19 March 2026)the 60-minute AI-assisted working session, own machine and AI agent, example tasks, scoring, pilot lessons, the candidate guide
• 02DoorDash Careers, our stance on AI and interviewing (9 October 2025)no AI in live interviews unless invited; misuse may disqualify
• 03DoorDash Careers, how to prepare for a technical interview (2021)the rubric: fundamentals, coding and communication; ambiguous questions on purpose; debugging valued
• 04DoorDash US job board461 roles, about 50 core software engineering and management, read 13 October 2026
• 05LeetCode Discuss, DoorDash Code Craft (17 November 2025)Dasher payout logic at $0.30 a minute and the slow upstream follow-up
• 06LeetCode Discuss, DoorDash debugging onsite (5 December 2025)debugging a Dasher assignment service, no AI allowed, HackerRank
• 07LeetCode Discuss, DoorDash AI Code Craft onsite (8 December 2025)a local editor with AI set up is required; a support workflow built as a graph
• 08LeetCode Discuss, DoorDash senior loop (2 February 2026)nearest Dasher, Dasher pay in Code Craft, review system with voting
• 09LeetCode Discuss, DoorDash menu question (24 November 2024)which items changed between two versions of a menu
• 10LeetCode Discuss, DoorDash backend onsite, India (23 May 2026)a two-day onsite with bug bash, system design, coding and leadership; JavaScript not offered
• 11Reddit r/leetcode, DoorDash prep kit (23 January 2026)practical API coding, not a Leetcode-style interview; maintainability, testability and failure handling
• 12Reddit r/leetcode, DoorDash drops LeetCode interviews (1 April 2026)candidates on two domain-heavy AI-assisted rounds and more subjective scoring
• 13Reddit r/leetcode, DoorDash E4 onsite (21 October 2024)a reviews system design, coding rounds and a hard hiring manager round
• 14Reddit r/OfferEngineering, DoorDash senior loop (16 August 2026)Code Craft screen, debugging with concurrency, alert notification design, and an AI round that needed real services on separate ports
• 15Levels.fyi, DoorDash software engineer pay, United Statesmedians by level, read 13 October 2026

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.