DoorDash · Phone screen → Onsite
In process2026 DoorDash Experienced SWE (E4) and Data Analyst Loops: 2 Experiences
Coverage: Two candidates changing jobs, in full-time loops for two different DoorDash roles. One is a software engineer at E4 who was referred and passed. The other is a data analyst on the store team who applied online and didn't. The engineer's onsite was in October 2026, and the analyst's interviews are listed under July–September 2026. The reports went up on November 4 and November 5, 2026.
The two roles had different loops, so each has its own section below:
- Software engineer (E4): an HR call, a Code Craft phone screen, then system design, debugging, AI coding and hiring manager rounds.
- Data analyst: an HR call, a SQL and A/B testing round, then three final interviews built around product cases.
Software engineer (E4)
What came up
The engineer says most of the onsite matched questions from earlier reports: a round-robin debugging exercise that moved on to consistent hashing, and an AI coding task about getting several services running. The system design was a job scheduler, which they say isn't one of the common ones.
Questions we found
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| A job scheduler, after a deep dive into one of the candidate's projects (Design a Scheduled Job Execution System) | 1 report | Report: 2026-11-04 (onsite October 2026) |
Debugging
| Question | Frequency | All last seen dates |
|---|---|---|
| Find the bugs in round-robin code wrapped in object-oriented classes, then write consistent hashing (the candidate wrote pseudocode only) (Fix a Traffic Router and Add Consistent Hashing) | 1 report | Report: 2026-11-04 (onsite October 2026) |
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| A known task centered on getting several services running quickly (not described further) | 1 report | Report: 2026-11-04 (onsite October 2026) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Walking through an incident, alongside routine behavioral questions | 1 report | Report: 2026-11-04 (onsite October 2026) |
1 detailed candidate timeline
01: A passing E4 loop where AI coding felt built for speed
Interview dates: September–October 2026 · Report date: November 4, 2026 · Role: Software engineer, E4, full-time · Degree listed: Master's · Channel: Referral · Candidate's rating: Positive, average difficulty · Result: Passed, then team matching
The timeline gives days and months without a year; the report files it under 2026.
September 10: HR call
September 18: Code Craft phone screen
The report names the round and nothing else about it.
October 7–8: Virtual onsite
The hiring manager round was split off and rescheduled several times, landing on October 20. The candidate says it took a week just to get it booked.
- System design. A deep dive into one of the candidate's projects, then a job scheduler. FastPrep has this design as Design a Scheduled Job Execution System. The report gives the topic only, so the practice version's requirements are its own.
- Debugging. The round-robin question, with the code wrapped in object-oriented classes. The candidate's tip is to dry-run the logic by hand to find the bugs. Afterward the interviewer asked for consistent hashing, which they wrote only as pseudocode. FastPrep has this exercise as Fix a Traffic Router and Add Consistent Hashing. This report lists no code or bugs; the practice version takes its class names from other reports of the same round, and most of its planted bugs are FastPrep's own.
- AI coding. Another question that had appeared in earlier reports, where the point was to get several services up and running fast. Their read is that DoorDash cares more about quick iteration than about carefully reviewing every line the AI writes. This was the round they enjoyed most, and the pressure was fairly low.
- Hiring manager. Routine behavioral questions plus a walk-through of an incident.
Overall the candidate felt good about the loop. A few interviewers seemed tired, but the AI coding and hiring manager conversations went very well.
Afterward
The follow-up came a week after the interviews: they'd passed. They still needed to match with a different team, and they found one without much trouble.
Data analyst
What came up
Product cases ran through the whole loop: an A/B testing case about bikes, a metrics and dashboard case for one of the team's features, and a database design round that turned into defining a feature. The candidate thinks the database design round is where it went wrong.
Questions we found
Product and Analytics Cases
| Question | Frequency | All last seen dates |
|---|---|---|
| SQL plus a bike-themed case about running an A/B test (no SQL task or case details given) | 1 report | Report: 2026-11-05 (interview 2026 Q3) |
| The manager names one team feature: which numbers would track it, and what dashboard each stakeholder group would need | 1 report | Report: 2026-11-05 (interview 2026 Q3) |
| A database design question that became a long discussion of how to define a feature (no schema or feature given) | 1 report | Report: 2026-11-05 (interview 2026 Q3) |
| Investigating a metric that has fallen | 1 report | Report: 2026-11-05 (interview 2026 Q3) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| The candidate's background | 1 report | Report: 2026-11-05 (interview 2026 Q3) |
| The candidate's use of AI tools | 1 report | Report: 2026-11-05 (interview 2026 Q3) |
| Handling conflict | 1 report | Report: 2026-11-05 (interview 2026 Q3) |
1 detailed candidate timeline
02: Store-team cases and a design round that ran out of time
Interview period: 2026 Q3 · Report date: November 5, 2026 · Role: Data analyst (store team), full-time · Degree listed: Master's · Channel: Applied online · Candidate's rating: Neutral, average difficulty · Result: Rejected
Round 1: HR call
Round 2: Technical, SQL and a case
The candidate's case was about bikes and centered on how an A/B test should be run. They think analysts get the same question set as data scientists here. The report doesn't describe the SQL part.
Final round: three interviews
- Hiring manager. Mostly case work on a single feature the manager chose: deciding which metrics would show how it's doing, and sketching the dashboards that different stakeholder groups would want.
- Database design, with an analyst from the team. The round carried a database-design label, yet the bulk of it went to settling how a feature ought to be defined. With more ground than the slot could hold, the SQL review that was meant to close it was dropped, and the candidate suspects this is the round that sank the loop. Their overall impression of it: fairly confusing.
- Behavioral, with a VP. Basic questions covering their background, conflicts, how they use AI, and how they'd dig into a metric that has dropped.
What the candidate took from it
Because the job sits on the store team, each question was built around that team's new features, and the candidate expects a different team's final round to look quite different. Their wider impression is that DoorDash hires few data analysts.
Comments
0No comments yet — be the first to share what you know.