Doordash

For doordash, the code craft interview is a bit tricky and different. But luckily it has a small question bank and I think only 2 questions so I was able to practice both of those questions on a website. That helped a lot.

I interviewed for a Senior Engineer role at DoorDash, covering Coding, Code Craft, System Design, and Behavioral rounds. I performed well in Coding and Code Craft, but my System Design round was mixed, and the Behavioral round went smoothly.

I had a virtual onsite interview with DoorDash where the difficulty level was average. The interview process included a branding round, system design, and debugging questions. I managed to write a solution for the Trie tree implementation but faced challenges with the codebase and follow-up questions.

I recently went through the phone screen and virtual onsite interview process at Doordash for a position in 2025. The interviews covered a range of topics including data structures and algorithms, system design, coding craft, debugging, and behavioral questions.

I had an onsite debugging interview at DoorDash, where I focused on identifying and fixing logic bugs within a mock Dasher Assignment Service, followed by discussions on test cases and optimization.

I successfully navigated the Code Craft round for a Midlevel SWE role at DoorDash, which focused on a collaborative problem to design and implement Dasher payout logic within a new Payments Service microservice. The experience was positive, and I passed the round.

I recently had a system design interview with Doordash, where I was tasked with designing a system for customer reviews and rewards based on review quality.

I was presented with a challenging algorithmic problem during my Doordash interview that involved navigating a city grid to calculate distances to the nearest DashMart and then identifying the DashMart serving the most customers.

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.

This post describes a Doordash phone interview experience, detailing a specific algorithmic problem called 'Closest DashMart' which involves finding the distance to the nearest DashMart in a grid.

I had a phone screen with Doordash for an E4 role in USA and was rejected. The interview included a problem focused on maximizing calories given a budget constraint on dollar amounts.

I had a phone screen with Doordash for a Software Engineer role where I was asked a modified version of 'Binary Tree Maximum Path Sum'. Despite solving most of it, I missed a corner case and was ultimately rejected.

I had a phone screen for an E4 role at Doordash in the USA. I was rejected after the interview, which focused on a modification of the LRU cache problem.

I interviewed with DoorDash for a Staff Software Engineer role in February 2024, completing a phone screen and four virtual onsite rounds covering data structures, algorithms, system design, and behavioral questions. Despite largely performing well, I was ultimately rejected due to failing to solve a specific follow-up question, which left me feeling incredibly disheartened.