How to Answer: "Why Do You Want to Work at DoorDash?"

"Why do you want to work at DoorDash?" is asked at a company with an unusually concrete way of testing the answer: every DoorDash employee, engineers included, is asked to complete deliveries as a Dasher several times a year (the WeDash program), and interviewers respond to candidates who find that appealing rather than quaint. The question is really probing for operator mindset: DoorDash's culture descends from its founders doing deliveries themselves, and it hires people who want to understand the physical operation their code orchestrates.

The company also supplies rich technical material for your answer: a three-sided marketplace (consumers, Dashers, merchants) where every order is a real-time optimization problem, logistics at street-level granularity, and an expanding platform (grocery, retail, white-label logistics) built on the same rails.

What the Interviewer Is Listening For

1. Attraction to the three-sided marketplace. Naming the structural problem (every decision trades off consumer experience, Dasher earnings, and merchant success simultaneously) shows you understand what makes DoorDash engineering distinctive rather than generic delivery-app work.
2. Operator mindset. Curiosity about the physical operation: what actually happens when an order is placed, why assignments fail, what a Dasher's evening looks like. The WeDash program institutionalizes this; motivation compatible with it fits.
3. Appetite for pragmatic intensity. DoorDash's culture is famously operational: metrics-driven, bias-to-action, "one percent better every day." Evidence you enjoy shipping and iterating under real-world messiness beats polished-systems purism.
4. Product usage with observations. You have almost certainly used the product; the differentiator is having noticed things: assignment timing, substitution flows, Dasher communication, merchant-side pain.

A Three-Part Structure

Part 1: The marketplace hook (2 to 3 sentences). What genuinely pulls you: the three-sided optimization, the physical-world feedback loop, or the logistics platform ambition.

Part 2: Your evidence (3 to 4 sentences). Background that maps: marketplace or logistics systems, real-time infrastructure, growth under messy constraints, or operational ownership, with numbers.

Part 3: The direction (1 to 2 sentences). What you would build, tied to a real problem area.

Sample Answer

"What draws me to DoorDash is that the feedback loop runs through the physical world: when my current company's matching logic is suboptimal, a dashboard dips; when DoorDash's is suboptimal, someone's dinner is cold and someone's earnings drop. That reality check on engineering decisions is exactly what I want more of. The three-sided structure is the technical hook: I work on a two-sided marketplace now, where I rebuilt our matching system and learned how brutal the tradeoffs are: our relevance improvement lifted buyer conversion 12 percent but concentrated demand on top sellers, and designing the correction taught me that marketplace health is the real objective function, not any single side's metric. DoorDash runs that problem with a third side and a ten-minute physics constraint, which is the harder, more interesting version. And honestly, the WeDash policy sealed it for me: a company that makes its engineers feel the operation is a company that builds the right things. I would want to work on assignment and logistics optimization."

Marketplace fluency from adjacent experience, a number, the physical-feedback conviction, and WeDash engaged with genuine enthusiasm.

Mistakes That Sink This Answer

• Generic delivery-app framing. "I use it all the time and love the convenience" ignores everything that makes the engineering interesting. Name the marketplace.
• Rolling your eyes at WeDash. Interviewers reportedly notice candidates' reactions to the delivery policy. If it strikes you as beneath you, this culture is the wrong fit and the interview will surface that eventually anyway.
• Pure-systems motivation. Wanting to build elegant distributed systems is fine, but at DoorDash the systems serve street-level operations; motivation that never touches the physical product misses the identity.
• No opinion from usage. One delivery-tracking observation ("the ETA updates go quiet exactly when I care most") is worth a paragraph of enthusiasm.

Prepare the Rest of the Loop

This question opens a practical, ownership-heavy process. See What is the DoorDash interview process like? for the structure, Top DoorDash behavioral interview questions for the ownership probes, and Grokking Modern Behavioral Interview for the evidence-based answering method.