2022–2025 DoorDash Machine Learning Engineer & ML Scientist Interviews, Hiring Level Not Reported: 13 Experiences
- Company
- DoorDash
- Reports
- 13 interview reports
- Level
- Unknown
- Stages
- Phone screen → Onsite
None of these thirteen reports says whether the candidate was an intern, a new grad or an experienced hire (four name a full-time role but say nothing about work history), so they're kept out of the intern and experienced-hire counts. Most are short, but together they show how often a talk about past projects sat next to the coding round.
Coverage: DoorDash ML interviews with the hiring level not reported, in two roles kept apart: Machine Learning Engineer (12 reports, Oct 2022 to Jul 2025, four of them for full-time roles, United States where stated) and Machine Learning Scientist (1 report, Dec 2023). Stages: recruiter and HR contact, technical screens, project deep dives, hiring manager conversations, and one onsite.
The other cohorts have their own articles: DoorDash Machine Learning Engineer intern interviews and DoorDash ML interviews for experienced hires.
Roles in this article
- Machine Learning Engineer: 12 reports, Oct 2022 to Jul 2025.
- Machine Learning Scientist: 1 report, Dec 2023.
Machine Learning Engineer (12 reports)
What came up
Nine of the twelve reports included talk about the candidate's past projects, from a full deep dive to a basic discussion with a hiring manager, and eight had a coding question. Two screens from 2023 asked for k-means written from scratch. Only one report, a four-round onsite, mentions design work.
| Topic | Reports | Most recent report |
|---|---|---|
| Past-project discussion or deep dive | 9 of 12 | Apr–Jun 2025 (interview) |
| Coding (data structures and algorithms) | 8 of 12 | May 13, 2025 (report date) |
| Behavioral questions | 2 of 12 | Mar 20, 2025 (report date) |
| Implementing k-means from scratch | 2 of 12 | Oct–Dec 2023 (interview) |
Single reports covered a chatbot design, intent detection and entity extraction for a chatbot, an interval question, and a topological sort. A report can appear in more than one row.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Return all palindromic substrings of a string (practice) | 1 report | Mar 20, 2025 (report date) |
| Find the maximum value over a set of (interval, value) pairs (practice) | 1 report | Reports: Feb 19, 2025 (report date); Additional FastPrep history: Feb 3, 2024 |
| A topological sort problem; the candidate no longer remembered the details | 1 report | Mar 1, 2024 (report date) |
Implement k-means clustering from scratch, including fit and predict (practice) |
2 reports | Reports: Oct–Dec 2023 (interview; reported Dec 8, 2023); Jul–Sep 2023 (interview; reported Sep 22, 2023); Additional FastPrep history: Dec 30, 2023; Oct 24, 2023; Oct 1, 2023; Mar 8, 2023 |
ML System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Design a customer chatbot | 1 report | Mar 20, 2025 (report date) |
ML Problem Solving
| Question | Frequency | All last seen dates |
|---|---|---|
| Design a chatbot from an intent classifier plus named-entity recognition (practice) | 1 report | Reports: Mar 20, 2025 (report date); Additional FastPrep history: Oct 24, 2023 |
Project Deep Dive
| Question | Frequency | All last seen dates |
|---|---|---|
| For one past project: what was the problem, how did you design and choose a solution, what was the outcome, and what did you learn? | 1 report | Feb 1, 2025 (report date) |
| Describe a project you've worked on | 1 report | Apr 3, 2024 (report date) |
| The technical trade-offs in one of your ML projects | 1 report | Mar 21, 2024 (report date) |
| Why this metric and not another one? | 1 report | Feb 1, 2024 (report date) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| A challenging project and how you overcame it (practice) | 1 report | Reports: Feb 19, 2025 (report date); Additional FastPrep history: Apr 1, 2026; Sep 28, 2025 |
12 detailed candidate timelines, loops, and screens
01: The whole screen was one project, presented to a hiring manager
Report date: Jul 31, 2025 (interview Apr–Jun 2025) · Role: Machine Learning Engineer, full-time · Background: PhD; applied online · Result: Rejected
Technical screen: project deep dive with a hiring manager
- The hiring manager's team works on fulfillment. The project the candidate chose to present came from ads.
The candidate called the experience positive and the difficulty average, and still didn't move forward.
02: One hour, two delivery-themed coding problems, then silence
Report date: May 13, 2025 · Role: Machine Learning Engineer · Location: United States · Result: No offer; no reply after the interview
HR contact
- HR got in touch to set up the interview.
Technical interview with an engineer (about 1 hour)
- Two medium-to-hard algorithm problems, both framed as delivery scenarios. Neither is named.
The system message said to expect a result within three weeks at most. Nothing came, and neither HR nor the interviewer answered the candidate's emails.
03: Four-round onsite built around a chatbot
Report date: Mar 20, 2025 · Role: Machine Learning Engineer
Coding
- Return all palindromic substrings of a given string. No constraints or examples were reported. Practice: All Distinct Palindromic Substrings.
ML system design
- Design a customer chatbot. No further scope was given.
ML problem solving
- Design a chatbot that combines an intent classifier with named-entity recognition (NER, which pulls items such as names or order details out of the text). Practice: Detect Intent and Order Details in Help Chats.
Hiring manager
- A basic discussion of past projects, plus behavioral questions.
04: Back-to-back technical and coding hours
Report date: Feb 19, 2025 · Role: Machine Learning Engineer · Location: United States · Result: No offer
Technical interview (1 hour, one interviewer)
- A challenging project and how the candidate got past it. Practice: Tell me about a challenging project that succeeded.
Coding interview (1 hour, one interviewer)
- A single easy problem: given pairs of (interval, value), find the maximum value. Practice: Maximum Coupon Credit and Its Time Windows.
05: A 45-minute project dive
Report date: Feb 1, 2025 · Role: Machine Learning Engineer · Location: United States · Result: No offer
Project dive (about 45 minutes)
- Pick one project you've already done. The interviewer asked for a lot of detail: the problem, how you designed solutions, how you chose between them, the outcome, and what you took away.
06: Emailed questionnaire, two-part technical interview, then no reply
Report date: Apr 3, 2024 · Role: Machine Learning Engineer · Location: United States · Result: No offer; no reply after the interview
Written questionnaire instead of an HR call
- About 15 open-ended questions to answer by email. The recruiter replied roughly two weeks after the candidate sent them back.
Technical interview, part 1: project deep dive
- Describe a project you've worked on. The candidate suspects this part didn't go well.
Technical interview, part 2: coding
- The problem isn't given. The candidate finished early, so the remaining time went into improving the solution together with the interviewer.
After the interviews the candidate followed up twice by email and never heard back.
07: LeetCode medium plus a 45-minute ML project discussion
Report date: Mar 21, 2024 · Role: ML Engineer · Location: United States · Result: No offer
Coding (60 minutes)
- One LeetCode question of medium difficulty; 45 of the 60 minutes were for getting the code to compile and run.
Project deep dive (45 minutes)
- A 45-minute discussion of one of the candidate's ML projects, including its technical trade-offs.
08: A half-remembered topological sort
Report date: Mar 1, 2024 · Role: Machine Learning Engineer · Location: United States · Result: No offer
Coding
- A topological sort problem in the LeetCode style; the candidate no longer remembered the details. They felt underprepared for coding.
Project deep dive
- Questions on past projects. The candidate enjoyed talking with the interviewers.
09: Project deep dive with a document to fill in first
Report date: Feb 1, 2024 · Role: Machine Learning Engineer · Location: United States · Result: No offer
Project deep dive
- Beforehand, DoorDash shared a document of questions about the candidate's background. The candidate says filling it in ahead of time helped.
- Questions in the round were along the lines of why a particular metric was used rather than others.
10: A k-means screen that ended without working code
Report date: Dec 8, 2023 (interview Oct–Dec 2023) · Role: Machine Learning Engineer, full-time · Background: Master's; came through a recruiter · Result: Did not pass
Rounds
- A phone screen in two parts: coding, then a project deep dive.
Questions
- Coding: write k-means by hand. Hints came, but the code still wasn't runnable by the end of the round. Practice: K-Means Delivery Zones.
- Project deep dive: questions on the candidate's past projects; no specific prompts are listed.
Result
- The candidate didn't move past the screen.
11: k-means fit and predict in a first DoorDash screen
Report date: Sep 22, 2023 (interview Jul–Sep 2023) · Role: Machine Learning Engineer, full-time · Background: PhD; a recruiter reached out first · Result: Did not pass
This was the candidate's first interview with DoorDash, and they rated it hard.
Screen, round 1: coding
- Write the
fitandpredictfunctions for k-means. Practice: K-Means Delivery Zones.
Screen, round 2: hiring manager
- A conversation with the hiring manager. No topics were given.
The candidate thinks coding was most likely what sank it.
12: A screen that moved twice, then a no from HR
Report date: Oct 20, 2022 · Role: Machine Learning Engineer, full-time · Background: Master's; applied online · Result: Rejected
Rounds
- One phone screen. DoorDash first set it up as coding, then changed it to a project deep dive at a new time. Minutes before that slot the interviewer pulled out, so it was booked a third time.
Questions
- Project deep dive on the candidate's past work; no specific prompts are listed. The candidate thought it went well.
Result
- HR declined to move forward a day later with no concrete reason, which left the candidate puzzled.
Patterns across the MLE reports
-
Coding and project talk in the same loop. Five reports pair a coding question with questions on past projects (03, 06, 07, 08, 10): a deep dive in 06, 07, 08 and 10, and a basic project discussion with the hiring manager in 03. Four reports describe only a project deep dive (01, 05, 09, 12); in 01 that deep dive was the whole screen, and in 12 it replaced a planned coding screen. A few accounts are thin, so some may describe the same candidate.
-
k-means from scratch in 2023 screens. Two candidates had to implement k-means in the opening coding round of a two-round screen (10, 11). Report 11 names the
fitandpredictfunctions; in 10 the code wasn't runnable by the end, despite hints. Neither candidate passed the screen. -
Going quiet after the interview. Two candidates heard nothing back after their technical rounds despite following up (02, 06).
Machine Learning Scientist (1 report)
What came up
This single report covers a recruiter round and a technical round whose one listed question was to implement k-means by hand.
Questions we found
Algorithms / ML Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Implement k-means clustering from scratch (practice) | 1 report | Reports: Dec 30, 2023 (report date); Additional FastPrep history: Dec 8, 2023; Oct 24, 2023; Oct 1, 2023; Sep 22, 2023; Mar 8, 2023 |
1 detailed candidate timeline
13: k-means from scratch with a distracted interviewer
Report date: Dec 30, 2023 · Role: Machine Learning Scientist · Location: United States · Result: No offer
Recruiter round
- A first round with a recruiter; no details given.
Technical round with an ML Scientist
- Implement k-means clustering from scratch. Practice: K-Means Delivery Zones.
- By the candidate's account, the interviewer joined 8 minutes late and never really engaged: their attention looked to be elsewhere, and several of the candidate's questions didn't seem to register.
Keep practicing
- Coding: practice versions of reported questions: All Distinct Palindromic Substrings (report 03), Maximum Coupon Credit and Its Time Windows (report 04), and K-Means Delivery Zones (reports 10, 11 and 13). The DoorDash question bank has every DoorDash practice question; it needs sign-in.
- ML problem solving: Detect Intent and Order Details in Help Chats (report 03), with more cases in the DoorDash ML modeling bank.
- Behavioral: the DoorDash behavioral question bank, including the challenging-project prompt from report 04.
- Everything DoorDash: the DoorDash interview page and DoorDash hiring insights.
- More firsthand reports: the Experience feed.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.