Software Engineer applicants have rated the interview process at DoorDash with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 35.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 24 days to get hired, when considering 184 user submitted interviews for this role. To compare, the hiring process at DoorDash overall takes an average of 24 days.
Common stages of the interview process at DoorDash as a Software Engineer according to 184 Glassdoor interviews include:
Phone interview: 36%
One on one interview: 21%
Skills test: 14%
Presentation: 9%
Group panel interview: 5%
IQ intelligence test: 3%
Personality test: 3%
Background check: 3%
Drug test: 3%
Other: 2%
Here are the most commonly searched roles for interview reports -
Hr phone call then coding session then virtual onsite. The coding questions are just leetcode style coding questions. System design is normal. ANd you will meet the HM in the end.
The phone screen was surprisingly quick, only 20 minutes, focused mostly on high-level design principles. I expected more coding questions but instead dived right into a system design topic. The main question was about creating a resilient API for a food delivery platform, which made me think on my feet. Funny enough, I had spent time on PracHub going over similar API design concepts, so I felt a bit prepared. The subsequent technical rounds were straightforward, and I ended up receiving an offer, though I decided to decline it.
Interview questions [1]
Question 1
Design a resilient bootstrap API for a food delivery platform that must handle order retries safely. Walk through idempotency guarantees, retry backoff strategy, and how you'd prevent duplicate charges when a client retries after a timeout.
coding online assesment virtual onsite. interviewers were professional and helpful. asked to deep dive on project. recruiter was responsive and could align with offer deadlines. was helpful with negotiations. coding problems were average difficulty.
Walking into the coding interview, I was taken aback when they asked about finding the K nearest restaurants based on coordinates. Just days before, I had stumbled on a mock on prachub.com that mirrored this question almost exactly. The interview felt straightforward, but I struggled with some behavioral questions. Overall, the experience was underwhelming; I expected more technical depth. After several rounds, they decided to go in another direction, which was disappointing given my prep efforts.
Interview questions [1]
Question 1
Given a list of restaurants with their coordinates and a user's location, find the K nearest restaurants