DoorDash · Software engineer · E3-E6
Behavioral & Values (Hiring Manager)
~45-60 minutes with a hiring manager or senior engineer
What they actually ask
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
- “Tell me about a project you're most proud of, then walk me through your specific role.”
- “Tell me about a time you took ownership and drove something end-to-end without being asked.”
- “Tell me about a time you had to move fast under ambiguity or urgency.”
- “Tell me about a time you used data to make or defend a decision.”
- “Describe a conflict or disagreement with a teammate or stakeholder and how you resolved it.”
- “Tell me about a failure or mistake and what you learned from it.”
- “Describe a decision with a tradeoff between different stakeholders, how did you weigh them?”
What this round is judged on
- Ownership · drove something end-to-end without being told
- Bias to action · moved fast and shipped under ambiguity
- Data-driven reasoning · used data to make or defend decisions
- Marketplace thinking · weighs consumers, merchants, and Dashers together rather than optimizing one side
- Learning / humility · owns mistakes and what changed after
Where this round sits
DoorDash’s published process. Lime marks the stage this round runs.
- 01Application / referral
- 02Recruiter phone screen (~30 min)
- 03Technical phone screen (~60 min)
- 04Virtual onsite (3-4 sessions, ~60 min each)this round
- 05Debrief / decision
What happens in each stage›
- Application / referral
- Careers portal or referral. Recruiter confirms the specific loop, which varies by team and level.
- Recruiter phone screen (~30 min)
- Spoken background, motivation (why DoorDash), and level/comp fit. No technical content.
- Technical phone screen (~60 min)
- One practical coding problem in a shared editor (CoderPad / HackerRank CodePair). No AI unless invited.
- Virtual onsite (3-4 sessions, ~60 min each)
- Typically 1-2 coding rounds (one may be debugging/extend-existing-code), a system design round (lighter or skipped for new grad/E3), and a behavioral/hiring-manager values round. Newest loops replace or augment one coding slot with an AI-assisted working session where using your own AI tools is expected.
- Debrief / decision
- Hiring committee reviews interviewer scorecards against DoorDash values; recruiter delivers outcome and offer. Roughly 2-5 weeks first contact to offer.
Sources
Built from what DoorDash publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.
- companyDoorDash, Why DoorDash is rebuilding its engineering interviews around AIcareersatdoordash.com
The 2025 shift to an AI-assisted working session; AI expected in that round and not in others unless invited.
Official reconciliation of when AI is allowed vs prohibited across the loop.
Official description of engineering interview rounds, coding, system design, and behavioral expectations.
DoorDash SWE leveling ladder (E3-E7) and compensation by level.
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
Other DoorDash rounds
- Recruiter Phone Screen
Warm, conversational, ~30 minutes
- Technical Phone Screen (Practical Coding)
~60 minutes in a shared editor
- System Design
~60 minutes, open-ended, spoken with a diagram
- Onsite Coding (Practical / Debugging)
~60 minutes, harder than the phone screen
- AI-Assisted Working Session
~60 minutes on your own IDE, using your own AI coding tools; full tool use encouraged