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

DoorDashData Scientist
Oct 2025

New Case and SQL Questions on the Phone Screen

DoorDash Data Scientist phone screen — I got new questions on both the case study and the SQL sections. The case study asked what the impact would be if a delivery is late, and what the possible reasons are. Then, based on the reasons I gave, the interviewer asked what data we would look at, and how to decide which of my stated reasons was the most important one. They also brought up that we've n…

Technical Screen0
DoorDashData Scientist
Oct 2025

SQL Screen With Doubled Difficulty and Tight Time

Part 1 was product, and since I was well prepared it felt fine. Prepare a lot more for high-frequency Biker and Cold Food. Read the attached switchback experiment design, randomization, and analysis parts carefully. SQL was not the usual four questions (someone on the forum summarized them before, but the answers weren't quite right, so correct them yourself). I got new questions, and the difficu…

Technical Screen0
DoorDashData Scientist
Oct 2025

Four Onsite Rounds, No Self-Intros, and a Prickly HM

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

OnsiteXP0
DoorDashData Scientist
Oct 2025

Missed the Case Answer Until Five Minutes of Hints Got Me There

I had this interview not long ago. The SQL was the classic Delivery set — the overall question volume was pretty large, but not every question required you to actually write it out. Some of them asked how you'd turn an existing query into an aggregated version, and the interviewer just had me talk through how I'd change the query instead of writing the code, to save time. The case question was: c…

Technical Screen0
DoorDashAnalyst
Oct 2025

Seven Rounds Including a Take-home and Two SM Interviews

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

OnsiteXP0
DoorDashData Scientist
Oct 2025

Seven Rounds Including a Take-Home Prediction Task

The interview process was as follows: Round 1: HackerRank assessment — SQL plus some data analysis questions. Round 2: HR screen — talked about why I was interested in DoorDash, my project experience, and why I was looking to switch jobs. Round 3: Hiring manager interview — mostly about my project experience, plus a DoorDash case question. Round 4: Take-home — given a DoorDash dataset to build a…

Onsite0
DoorDashData Scientist
Oct 2025

A Seven-Round Loop with a Take-Home and Three Manager Interviews

The interview process went like this: Round 1: HackerRank assessment — SQL plus some data analysis questions. Round 2: HR screen — talked about why I was interested in DD, my project experience, and why I was looking to switch jobs. Round 3: Hiring manager interview — mainly talked about project experience, plus a DoorDash case Q&A. Round 4: Take-home — given a DoorDash dataset to build a predict…

Onsite0
DoorDashAnalytics Engineer
Oct 2025

Rejected After a Four-Round Virtual Onsite

I couldn't find a single interview review for the analytics engineering role on the forum, so I'm contributing one. Tech round: one LC medium question, not sure if it's an original/repeat question, pretty simple but exhausting — window sum, find the max sum. I'd seen it before in DoorDash's DE interview reviews. Then four SQL questions — he said getting three done was actually fine. I wrote the f…

RejectedOnsite0
DoorDashData Scientist
Sep 2025

Behavioral Round, Then a Case Study and SQL

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

Technical ScreenXP0
DoorDashSoftware Engineer
Sep 2025

A Two-Day Virtual Onsite After the DashMart Phone Screen

Vendor recruiter call After the referral, I got an email scheduling the vendor recruiter call and the phone screen separately. This round was just going over my resume and checking whether there was overlap with the target team. The whole thing was 10+ minutes, and the questions felt pretty targeted. Phone screen A senior manager, and I got the DashMart problem. I hadn't looked at any write-ups b…

Onsite0
DoorDashSoftware Engineer
Sep 2025

Four Onsite Rounds, Same Image Carousel Coding Problem

The onsite question had already been posted before — it's the same old image carousel problem. Four rounds onsite: Coding, 75 min: still the same old question — continuing to build comment and upvote features on top of the carousel. HM behavioral, 45 min: asked some standard behavioral questions, I talked about a project conflict / mistake, and they asked one that doesn't come up often — how do y…

Onsite0
DoorDashSoftware Engineer
Sep 2025

Four Onsite Rounds, HM Chat Was the Roughest

System Design: Three-day donations. Specifically, you build a donation entry point for users, where the user submits their personal info plus how much money they want to donate to different organizations, and the problem gives you the assumption that you're only responsible for sending the money to the company's account. During the discussion the interviewer strongly suggested making it async, bu…

Onsite0
DoorDashSoftware Engineer
Sep 2025

Loop Went Well, Then Rejected Over a Seniority Mismatch

LinkedIn HR reached out and said my background was a good fit; after an HR call, I moved into the interview process. The Phone Screen was an Easy coding question plus a follow-up — string matching. After passing the Phone Screen, I had a 30-minute informal chat with the Hiring Manager, mostly about the team's work and my own experience. After that, HR reached out to schedule the Loop Interview. T…

RejectedOnsite0
DoorDashSoftware Engineer
Aug 2025

Four Onsite Rounds, Rejected Three Days Later

The phone screen was two months ago. The question then was [LeetCode] Koko Eating Bananas. I dragged it out for two months before I finally did the onsite. Four rounds. Round 1 was system design. The question was a three-day donation system. This round was 75 minutes long, but the interviewer and I ended up deep-diving into my project until the 45-minute mark before he even got into the design pa…

RejectedOnsite0
DoorDashSoftware Engineer
Aug 2025

A Two-Day Virtual Onsite With Four Rounds

Outsourced recruiter call After the referral went through, I got emails to schedule both the recruiter call and the phone screen. This round was just going over my resume and checking whether there was overlap with the target team — the whole thing was 10+ minutes, but the questions were pretty targeted. Phone screen A senior manager. The problem was DashMart-style — I hadn't looked at any interv…

Onsite0
DoorDashSoftware EngineerSenior+
Jul 2025

Full Loop in a Week, Rejected Over a Level Mismatch

A recruiter reached out on LinkedIn saying my background was a good fit, and after an HR call I moved into the interview process. The Phone Screen was an Easy coding question with a follow-up — string matching. After passing the Phone Screen, I had a 30-minute informal chat with the Hiring Manager, mostly about the team's business and my own work experience. After that, HR reached out to schedule…

RejectedOnsite0
DoorDashSoftware EngineerSenior+
Jul 2025

Four-Round Virtual Onsite With an Incident Simulation

Virtual Onsite, four rounds total. First round simulated handling an Incident. Second round System Design, third round Coding, fourth round HM (Hiring Manager). Incident Assume we own a payment integration service. Internally, various services call us to make payments, and downstream from us is a financial institute. The current incident shows our service is abnormal, with high CPU and memory usa…

RejectedOnsite0
DoorDashSoftware Engineer
Jul 2025

OA, System Design, Debug, and Craft Rounds

OA: Not LeetCode. You're given an actual scenario and you live-code a Service class on HackerRank right there — the logic is fairly simple, basically a bunch of if-else checks just to see whether your logic is clear, not really algorithm-based at all. But there were three parts. My advice: once you've nailed down the requirements, write fast, otherwise you definitely won't have time left to write…

Onsite0
DoorDashData Scientist
Jul 2025

Five Onsite Rounds, Rejected After a Metrics-Heavy Loop

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

RejectedOnsiteXP0

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