
DoorDash Data Scientist candidates commonly report a SQL-and-product-case screen, followed for some by several case interviews and a partner or behavioral conversation.
$180K
Avg. Base Comp
$245K
Avg. Total Comp
2-7 rounds
Typical Rounds
3-6 weeks
Process Length
DoorDash Data Scientist interviews reported by candidates center on two connected skills: practical SQL reasoning and structured product analytics. Initial screens pair SQL with a product, diagnostic, or experimentation case, although the order and format vary. Reported SQL topics include window functions, date calculations, and interpreting a pre-written query; one newer account characterized the SQL logic as basic. Expect to explain what a query does rather than treating the exercise as coding alone.
The case material is notably marketplace-specific. Candidates describe prompts about declining successful deliveries and evaluating a new feature. A clear diagnosis before a proposed test or solution is the recurring pattern: define the metric, break the problem into relevant marketplace factors, prioritize hypotheses, and then discuss how an experiment or operational response could evaluate a change. Experimentation discussions may also cover setup, guardrails, and undesirable outcomes.
Candidates who progressed further describe multiple product-case conversations, sometimes alongside a behavioral interview or a conversation with a product manager. Prepare concise examples of cross-functional work and impact, but keep the emphasis on communicating analytical judgment. Reports suggest that apparently simple cases can still produce detailed follow-up questions, so practice giving a crisp structure before adding detail. The exact sequence varies by candidate and progression stage.
Synthesized from 32 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Doordash process.
Did the SQL round. was super time crunch to solve all 4 questions. There were 3 questions to write codes involving Join and Window functions. Last question was to interpret and modify existing codes.
Questions asked: i was fairly confident with my answers. There 3 questions to write codes. 1. finding the high frequency customers (order > 30 deliveries per month). The interviewer gave me some hint as i was giving the output for counting the orders instead of customer_id. I corrected it on the spot and moved on. 2. top valued customers - i used rank () function as interviewer emphasised on there may be more than 1 customers with top order values 3. include joining 2 tables (restaurant and order table) and only filter one restaurant to find out their month-on-month sale change. I join table and use LAG to find out previous month sale then calculate percent change. For the last question, there was already codes written, i was asked to interpret what it means/output. It is to find out restaurants with bottom 25% (quartile) in 2021. i think i got that right and the interviewer asked me if instead of restaurants, and to find out customers with bottom 25% order value, can I adjust the codes. i tweaked the codes but there was only 2 minutes left so I didn't have time to review.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Doordash
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Monthly Customer Report | |
| Experiment Validity | |
| Month Over Month | |
| Button AB Test | |
| Average Order Value | |
| Over-Budget Projects | |
| Longest Streak Users | |
| Netflix Retention | |
| WAU vs Open Rates | |
| Network Experiment Design | |
| Daily Retention Summary | |
| Delivery Estimate Model | |
| Instagram TV Success | |
| Random Bucketing | |
| Group Success | |
| Post Composer Drop | |
| Christmas Dinner Ingredient Optimization | |
| Google Maps Improvement | |
| Comparing Search Engines | |
| Uber User Journey | |
| Marketing Channel Metrics | |
| Biggest Tip | |
| Valid Anagram | |
| Cancellation Fees | |
| Recruiting Leads | |
| Forecasting New Year Revenue | |
| Hurdles In Data Projects | |
| Sample Time Series | |
| Food Delivery Times |
Synthesized from candidate reports. Individual experiences may vary.
Candidates commonly report an initial screen split between SQL and a product or experimentation case. Several reports describe two 30-minute sections, although the order of those sections varies.
Candidates report delivery- or order-data questions involving joins, aggregations, date calculations, CTEs, ranking, and window functions. Some also describe explaining or modifying an existing query.
Candidates report cases about delivery performance, restaurant demand, or product changes. They describe being asked to diagnose the issue, choose metrics, form hypotheses, and discuss A/B-test design.
Candidates who advanced report several product-case discussions; some also report a business-partner, behavioral, hiring-manager, or other manager conversation. Follow-ups may test tradeoffs and communication.