Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

59 stories

Likes earn the author +10 XP for the first 3 likes each day

DoorDashSoftware Engineer
Reported May 2026

Great Feedback, Then the Role Vanished in a Re-org

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…

Onsite0
DoorDashSoftware Engineer
Apr 2026

Rejected After Arguing Math With the Interviewer

Locked — open it to unlock the full story with XP.

RejectedTechnical ScreenXP0
DoorDashSoftware Engineer
Apr 2026

Passed Coding, Failed the Project Deep-Dive

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
DoorDashSoftware Engineer
Apr 2026

System Design, a Dasher Debugging Round, and an AI Pair-Programming Round

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…

Onsite0
DoorDashSoftware Engineer
Mar 2026

Building a Dasher Payout API

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…

Technical Screen0
DoorDashData Scientist
Mar 2026

System Design for the Home-Page Recommendation Feed

Locked — open it to unlock the full story with XP.

OnsiteXP0
DoorDashData Scientist
Mar 2026

Three Onsite Cases All About A/B Testing I Wasn't Ready For

Locked — open it to unlock the full story with XP.

OnsiteXP0
DoorDashSoftware Engineer
Mar 2026

Rejected After a Dasher Pay Coding Screen With No Starter Code

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…

RejectedTechnical Screen0
DoorDashData Scientist
Feb 2026

Three A/B Testing Cases That Exposed My Blind Spot

Locked — open it to unlock the full story with XP.

OnsiteXP0
DoorDashData Scientist
Feb 2026

Three Case Rounds, No A/B Testing Background

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…

Onsite0
DoorDashData Scientist
Feb 2026

Onsite ML System Design for the Home Feed Recommender

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…

Onsite0
DoorDashData Scientist
Feb 2026

Three Onsite Case Rounds on A/B Testing and Promotions After an Easy Phone Screen

Locked — open it to unlock the full story with XP.

OnsiteXP0
DoorDashMachine Learning Engineer InternIntern
Feb 2026

LLM Research Questions, Then Ghosted

Locked — open it to unlock the full story with XP.

No responseTechnical ScreenXP0
DoorDashSoftware EngineerSenior+
Feb 2026

Four Onsite Rounds, Rough Code Craft

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…

Onsite0
DoorDashSoftware Engineer
Jan 2026

Referral, Fast Loop, and a Painfully Slow Immigration Law Firm

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…

OfferOnsite0
DoorDashSoftware Engineer
Jan 2026

Full Onsite Loop, Then Grilled About Using AI More

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…

RejectedOnsite0
DoorDashData Scientist
Jan 2026

System Design for the Home Feed Recommendation Engine

Locked — open it to unlock the full story with XP.

OnsiteXP0
DoorDashData Scientist
Nov 2025

Recycled SQL Questions and a Biker-Project Case Round

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…

Technical Screen0
DoorDashData Scientist
Nov 2025

SQL Round Ran Out of Time, Then a Bike Case Study

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…

Technical Screen0
DoorDashData Scientist
Oct 2025

Biker Feature Case Study Plus a Four-Question SQL Round

Locked — open it to unlock the full story with XP.

RejectedTechnical ScreenXP0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP