Doordash
More Experiences
Doordash Backend Interview Experience | Reject
September 18, 2025 • 13 reads
Summary
I recently interviewed at DoorDash for a backend position and was ultimately rejected. The process involved system design, hiring manager discussion, debugging, and a coding round, but I left unsatisfied due to perceived misalignments in expectations.
Full Experience
I recently went through the DoorDash interview process for a backend role and wanted to share my experience. Unfortunately, I was rejected after completing all rounds.
Round 1: System Design + Domain Knowledge
The problem I faced was centered around an Ads Click Aggregator. The interviewer was from the Data Engineering team. I found this conversation quite challenging, partly because the interviewer seemed relatively new to conducting such design interviews. The flow felt a bit off, and the discussion focused on areas I didn't feel were core to the problem, making it hard to properly showcase my system design skills.Round 2: Hiring Manager Discussion
This was a straightforward round, involving standard behavioral questions.Round 3: Debugging
In this round, I was given a piece of code that contained 3–4 bugs, which I successfully fixed. The interviewer then followed up with questions about optimizations, which I was also able to address.Round 4: Code Craft
I had anticipated this round would evaluate my understanding of OOP principles, class creation, and overall code structure. However, the interviewer seemed solely concerned with the problem-solving logic and getting a running code solution.Overall, I left feeling unsatisfied with the interview process, primarily due to a lack of alignment in expectations and how some of the interviews were conducted.
Interview Questions (2)
Q1
Ads Click Aggregator System Design
System Design
Design a system for an Ads Click Aggregator. This round involved discussions around system architecture, data processing, and handling scale for aggregating clicks on advertisements.
Q2
Code Debugging with Optimizations
Other
Given a piece of code containing 3-4 bugs, identify and fix them. Follow-up questions focused on optimizing the corrected code.