Doordash Backend Interview Experience | Reject

Result
Rejected
Posted
18 Sept 2025
481 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.

How it went

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.

Questions asked (2)

  1. 01

    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.

  2. 02

    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.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at DoorDash recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!