real interview stories, told over a cup of tea ♡
DoorDash Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
45 results
- Dasher Pay Phone Screen with a Surprise Sweep Line and Peak Windows Follow-upDoorDash · Software Engineer · Technical Screen · Oct 2026
This was the dasher pay question from the interview reports on the forum. I spent a good chunk of time up front discussing the requirements and the data shape. I wanted to get part 1 done with a simple algorithm first and worry about the rest later, and I had already finished writing it, but the interviewer was clearly unhappy and hinted that I should use a sweep line. Changing the code took quit…
- Food Review System Design That Was All DB Schema, Then a Debug Round, RejectedDoorDash · Software Engineer · Onsite · Oct 2026Rejected
I was rejected a few weeks ago, so I'm posting this now. The phone screen was nothing special, the classic payment question, and the interviewer was very helpful. Onsite: Hiring manager round. Nothing much, it's basically just BQ, and they all came out about the same. System design, the classic food review. The interviewer barely discussed anything with me the whole time. Basically I was the one…
- An AI-Coding Onsite Round, Rejected After System DesignDoorDash · Software Engineer · Onsite · Sep 2026Rejected
Screen interview: Code Craft: Dasher Pay. Didn't feel too hard — just make sure to talk through your approach with the interviewer before you start coding. It's a high-frequency question from the forum. Onsite Round 1: Debugging: Round Robin Load Balancer. Also a forum question. Onsite Round 2: AI Coding. They had me set up a microservice locally on my own machine, specifically to handle abnormal…
- Bootstrap Phone Screen, Consistent Hashing Debug Round, AI Coding DAG, RejectedDoorDash · Software Engineer · Onsite · Sep 2026Rejected
Phone screen: it was the classic bootstrap question, same as most of the interview reports out there. The hard part of the question is adding the HTTP response status handling on top. I strongly recommend the public EngineBogie write-up of this one ("Implement a BootstrapService to aggregate data from multiple services"). Onsite: Debug: the question was the same round robin one. It's actually not…
- Five Onsite Rounds Including a Live AI Coding ChallengeDoorDash · Software Engineer · Onsite · Sep 2026
Round 1 — Code Craft: Bootstrap / Aggregator API Problem You are tasked with implementing an API that exposes the required information and is as resilient to failures as possible in order to ensure a good user experience. Implement a Bootstrap API that takes a user_id, pulls information from three existing upstream services — Consumer, Payment, and Address — and combines it into a single response…
- Four-Round VO, Menu Review Design Stuck in Schema Details Until Minute 45, RejectedDoorDash · Software Engineer · Senior+ · Onsite · Sep 2026Rejected
The phone screen was coding plus a project deep dive. The coding was that Dasher Pay question. The interviewer was really nice: right after I finished writing the code, they just told me not to worry, they were passing me. For the project deep dive, the interviewer listened really carefully and asked a lot of questions. The VO was four rounds. Round 1 was AI coding. I think they have two coding q…
- Resilience, Payments, and Concurrent DispatchDoorDash · Software Engineer · Onsite · Sep 2026Rejected
The author describes an unsuccessful DoorDash interview process beginning with a coding screen about coordinating calls to downstream services. Follow-up discussion addressed failure handling, retries, and when requests should be allowed through or blocked during faults. The final interviews included a donation-service design covering payment processing, failures, lost connections, and duplicate…
- Four-Round Onsite With an AI-Assisted Coding RoundDoorDash · Software Engineer · Onsite · Aug 2026Rejected
First I got a reach-out from a recruiter, and we set up a quick call to go over the basics and the interview process. Then they scheduled the first technical round. After that round, the process got handed off to another recruiter, who also set up a quick call to go over some basic info, and at the same time scheduled the onsite. The first round was a Code Craft round, 1 hour. The second round wa…
- Recruiter Call to a Four-Round Virtual Onsite, No OfferDoorDash · Software Engineer · Onsite · Aug 2026Rejected
Recruiter call: overall this was standard - basic info questions, no BQ really came up in this round. I recall being asked why DoorDash. Passed in a day or two, then got scheduled for the next round quickly - pretty efficient. Code Craft: a simplified version of Dasher Pay, simplified in that there was no coding extension like a double pay rate window. Instead, after finishing the basic coding, t…
- DoorDash Data Scientist Interview Experience: SQL, cases, and virtual onsiteDoorDash · Data Scientist · Jul 2026
An HR-style call covered the role, compensation and benefits, and the hiring flow. The technical screen began with four medium SQL questions in a HackerRank-style format. I barely had time for the last one and got the impression they did not expect a full solution. A case study followed, where I explained how I would approach an open-ended business problem. After passing, I had a virtual onsite w…
- DoorDash Data Scientist interview: SQL and ambiguous casesDoorDash · Data Scientist · Technical Screen · Jul 2026
The first round combined a 30-minute SQL assessment and a case study. SQL felt very easy, while the case portion was more difficult: two prompts were straightforward and one was genuinely ambiguous. The next round included three case studies and an interview with a cross-functional partner. The interviewers were kind, but I still had to keep structure and clarity across the scenarios. I did not r…
- DoorDash Data Scientist interview: SQL and case rounds with one missed conceptDoorDash · Data Scientist · HR Screen · Jul 2026
After a recruiter screen, I had two screening rounds involving SQL and a case study, followed by more case-study rounds. The onsite-style loop also included a meeting with a cross-functional partner, and I later spoke with a hiring manager. The setup was professional and moved quickly. The data-science questions were not easy. I had done well on the early screens and one case, but a later case br…
- DoorDash Data Scientist interview: SQL round and case study before a quick rejectionDoorDash · Data Scientist · Technical Screen · Jul 2026Rejected
The loop felt almost entirely about training the interviewers. There was no separate recruiter screening call. It began with a SQL round, then a case study. The recruiter mostly gave a brief introduction, while the two technical sessions carried the process. I finished the SQL questions and explained my thinking to the recruiter as things moved along. The case study also went well, and it felt li…
- DoorDash Data Scientist interview: take-home after manager screenDoorDash · Data Scientist · HR Screen · Jul 2026Rejected
I had a quick phone screen and then a Zoom meeting with the hiring manager that lasted about 30 minutes. After that, I completed a take-home assignment and submitted it within 72 hours. That was the end of the process for me. My submission did not move forward, and I did not get another live round. The path looked straightforward on paper, but it was still frustrating because all of my momentum r…
- DoorDash Software Engineer interview: bilingual 30-minute recruiter callDoorDash · Software Engineer · HR Screen · Jul 2026
After the recruiter contacted me, I had an initial conversation of about 30 minutes. The call began in Portuguese and then continued in English. It stayed general: we discussed my previous experience and what I was seeking in compensation, including salary and benefits. It did not advance to the technical part at that stage, so this was the only impression I had of the process. Location: São Paul…
- DoorDash Software Engineer interview: durable refund DAG system designDoorDash · Software Engineer · Technical Screen · Jul 2026Offer
The process was demanding from the start. After several rounds, I handled behavioral questions that, interestingly, matched my real experiences well. The technical work carried the most weight, especially a system-design challenge about building a durable DAG flow for order refunds. I was overwhelmed at first, but my earlier system-design interview study helped me organize the approach and unlock…
- DoorDash Software Engineer interview: internal electric-motor design screeningDoorDash · Software Engineer · HR Screen · Jul 2026
It began with a phone call with the recruiter. She was specific about the kind of person she was looking for, then asked technical questions focused on internal electric-motor design knowledge. The material was more targeted than I expected, and it was clear that the screen was trying to establish an exact fit with that technical background. Location: San Francisco, CA. Overall feedback: neutral.…
- Four-Round Virtual Onsite, Rejected in Three DaysDoorDash · Software Engineer · Onsite · Jul 2026Rejected
Interview timeline: 6/15/2026 – DoorDash HR reached out on LinkedIn asking about my availability for an interview. 6/23/2026 – DoorDash first VO round, CodeCraft interview. The question was Dasher Pay — there are already write-ups about this problem, both here and elsewhere. There was a follow-up asking how to handle the double pay rate for dashers during peak hours. After I finished the code, th…
- Great Feedback, Then the Role Vanished in a Re-orgDoorDash · Software Engineer · Onsite · May 2026
Hey everyone, I went through the DoorDash loop around two months ago. It ended up bittersweet, but I still count it as a win for me. Application A referral got me in for the Software Engineer, Product role (E4), and the recruiter got back to me about what came next. Technical screen The opening round was what they call a code craft round. They hand you a practical problem and you solve it with al…
- Onsite With Three Coding Rounds Dressed Up as Delivery ProblemsDoorDash · Software Engineer · Onsite · May 2026
Posting my DoorDash interview experience. My overall impression is that this company's questions are very tied to the business — almost every question comes wrapped in a food-delivery scenario, even when the core is just a template problem. The upside is it's not boring to talk through; the downside is you have to unwrap the packaging first and figure out what the core problem actually is — get t…
- System Design, a Dasher Debugging Round, and an AI Pair-Programming RoundDoorDash · Software Engineer · Onsite · Apr 2026
SD round - from the prep notes, a food review system. Debug round - also from the prep notes. The question was about adding a dasher and randomly picking a dasher. The bugs included, roughly: A boundary issue when the map is empty A logic issue: when you delete a randomly-selected key from the map, you need to move the last element into the deleted slot and update the index. If you don't handle t…
- Building a Dasher Payout APIDoorDash · Software Engineer · Technical Screen · Mar 2026
I received the Code Craft task as a Dasher payout calculation API problem. Dasher Payout Calculation API Overview The prompt said that, as part of a migration from a monolith to a microservice architecture, the team was building a new Payments Service. My task was to implement the Dasher payout logic, which required calling an upstream dependency to retrieve the relevant data. Goal Create this en…
- Rejected After a Dasher Pay Coding Screen With No Starter CodeDoorDash · Software Engineer · Technical Screen · Mar 2026Rejected
I got a question that's pretty common on the forum, a combination of a Bootstrap-style problem and DoorDash Pay. The interviewer didn't give me any starter code, just the description below. He said to assume I'm a downstream service and the data comes from upstream. The answer I wrote turned out to be correct, it's just that the data was test cases, not data mocked from an upstream interface. A f…
- Four Onsite Rounds, Rough Code CraftDoorDash · Software Engineer · Senior+ · Onsite · Feb 2026
Let me start with the technical screen: a fairly classic multi-source BFS problem — find the nearest source for every cell in a 2D grid. Medium difficulty, leaning toward the basic side. Next is the onsite, four rounds in total. Round 1 was system design. The first 15 minutes were spent talking about a recent project of yours, then it moved into the design question. The task was to design an app…
- Onsite ML System Design for the Home Feed RecommenderDoorDash · Data Scientist · Onsite · Feb 2026
Problem background: design a store recommendation system similar to the app's home page. Interview process & core follow-ups: Overall architecture and hard constraints The scenario given right away was home page recommendation. User input is extremely sparse — basically just the User ID and current location. The system has a couple of hard constraints: the stores surfaced must be within delivery…
- Three Case Rounds, No A/B Testing BackgroundDoorDash · Data Scientist · Onsite · Feb 2026
I'd seen a lot of phone screen reports for this role and passed it pretty easily, but the onsite was like the reports I'd read about — genuinely hard, and unlike anything I'd seen before. My background is as a DS who has always worked on modeling, with a little bit of product analytics experience mixed in. I don't have hands-on experience running A/B tests, so on the onsite, the experiment design…
- Full Onsite Loop, Then Grilled About Using AI MoreDoorDash · Software Engineer · Onsite · Jan 2026Rejected
DoorDash's full loop. I felt like their question bank isn't very big — pretty much everything is covered by write-ups here already. Specifically, the phone screen with the interviewer: dasher_pay. Same problem that's already been posted here, so pay attention to handling the input datetime. I used a few states to control the order's status. I forgot the follow-up, but again, the situations posted…
- Referral, Fast Loop, and a Painfully Slow Immigration Law FirmDoorDash · Software Engineer · Onsite · Jan 2026Offer
Backfilling my full February DoorDash interview. It was a friend's referral. The process moved really fast, probably because my previous team and this team were a very close match in terms of business. The guidance said the coding round would be "coding with AI", but in the actual interview there was no AI assistance and no AI round, and the interviewers said they had never heard that AI was allo…
- Recycled SQL Questions and a Biker-Project Case RoundDoorDash · Data Scientist · Technical Screen · Nov 2025
HR screen -> Round 1 30-min SQL round: 4 old/frequently-asked questions, with my basic approach: Q1. Percentage of high frequency customers (order>30) each month. Get cus_id, month, order_count. Group by month, cus; count(distinct case when oc> then cus end)/count(distinct cus) Q2. Customers who ordered the most, excluding high-frequency customers, each month (follow-up: the most frequent custome…
- SQL Round Ran Out of Time, Then a Bike Case StudyDoorDash · Data Scientist · Technical Screen · Nov 2025
This was the first interview of this hiring round for me, and I wasn't prepared — I underestimated how much time management the SQL portion would take, and I didn't finish it before time was cut off. The SQL question was a real, previously-reported one. It asked for: Users who spent more than $100 in a month The same as above but excluding the person with the highest spend each month Month-over-m…
