DoorDash Software Engineer Phone Screen Questions
84+ questions from real DoorDash Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the DoorDash Phone Screen round test?
The DoorDash phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
DoorDash Software Engineer Phone Screen Questions
Doordash phone screen
// # A DashMart is a warehouse run by DoorDash that houses items found in convenience stores, grocery stores, and restaurants. We have a city with open roads, blocked-off roads,...
Doordash phone screen
We want to implement an in-memory tree key value store for Doordash Restaurant Menus. Definitions: - path is a / separate string describing the node. Example /Tres Potrillos/tacos/al_pastor - Values are all strings API...
Doordash Phone Screen
You are given a list of locations connected by roads, each with a designated beauty value and travel time. Starting at location 0 (the source), your goal is to traverse...
DoorDash Phone Interview
Got to interview at doordash, I would say the interview didnt explain this very well and there was some accent barrier so I had a hard time understanding what exactly...
DoorDash Phone Interview
First question : Validate order list : P1, P2, D2,D1 Pick are ascending order and delivery can be any order Solved it completely and correctly Second Question : Given number of order return all...
Doordash Phone Screen
I got following sum for my phone interview. https://leetcode.com/discuss/interview-question/1367130/Doordash-Phone-Interview I asked following clarifying questions would the keys repeat? what is the input? would the input root node in the new tree...
The question concerned payer salaries, primarily requiring the ability to test the final result and the use of a good OOP pattern. While writing my answer, I felt all the assumptions I made to the exa
DoorDash Onsite
Coding Round 1: Two Variations of https://leetcode.com/problems/count-all-valid-pickup-and-delivery-options/ 1. Given array of pick up and delivery options, make sure that the array is valid. Example 1: Input: [\'P1\', \'D1\'] Output: True Explanation: P1 comes...
DoorDash Onsite
Phone Screen: https://leetcode.com/problems/employee-free-time/ Onsite: First coding round: https://leetcode.com/problems/valid-sudoku, and https://leetcode.com/problems/sudoku-solver/ Second coding round: https://leetcode.com/problems/analyze-user-website-visit-pattern/ Follow up: If you cannot store that data on a single machine, and you have very large data - how...
Doordash phone screen yay or nay ?
I recently had a phone screen - codecraft with doordash. While I took time to do data modelling and also get the class structure in place, I couldn't implement everything. I had to implement 6 classes
Doordash Machine Learning Engineer Internship Tech Phone Screen Interview Experience
There were two rounds in total. The first round involved detailed explanations of past projects, including behavioral questions (presenting a challenging but unsuccessful project and a challenging but
Fresh interview experience, posted right after the interview! I've also included my solutions, the interviewer's test cases, and a runnable setup. Please share other interview experiences, thank you!
The first round phone interview lasted one hour. The interviewer was an enthusiastic young white man. A quick check on LinkedIn revealed a strong background and academic record. The question and solut
DoorDash chances based on performance on Phone Screen?
Just had the phone screen. It was a LC hard on Doordash tagged on LC, but the follow up wasn't tagged. I got the initial part perfectly - great communication, testing, time and space, etc - and was cl
DoorDash Fulltime SDE Tech Phone Screen Experience
I got a referral from someone online, and I'm very grateful to him. I was rejected immediately after applying before, but this referral led to an interview. Timeline: September 17th referral, Septembe
DoorDash | SE2 | India | Rejected
Hi Folks, I recently had the opportunity to interview for the Software Engineer 2 role at DoorDash for their Pune location in India. I\'m sharing this experience to give back to...
Doordash - E4 Phone screen [Reject]
Giving back to the community: Had my doordash phone screen on Feb 04th Location - Toronto, ON Interviewer was from USA Q1 - https://leetcode.com/problems/koko-eating-bananas Q2 - https://leetcode.com/problems/minimum-size-subarray-sum Solved Q1 with optimal apprach, Q2 explained the optimal...
DoorDash Virtual Onsite and Phone Screen Interview Experience 2025
Phone Screen Question that would make us build the adjacency map for a Tree and then return the time to flood the Tree. # Onsite **Code Craft:** Question regarding dasher pay and how we structure th
DoorDash E5 Phone Screening - USA (Passed)
1h interview I was asked: https://leetcode.com/problems/basic-calculator-ii/ with a followup - https://leetcode.com/problems/basic-calculator-iii I did the first problem quickly but messed up the if statement, so it took me 15min to figure out my mistake... Was...
Doordash Phone screen
https://leetcode.com/problems/count-sub-islands/description/ Exact same question with different names of grid1 and grid2 obviously Just this one cuz I wasted too much time thinking about grid1. I realized at the end of the...
What to Expect in the DoorDash Phone Screen Round
The DoorDash Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 84+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at DoorDash show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at DoorDash typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at DoorDash Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 84 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access