
DoorDash Data Scientist Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 133 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at DoorDash.
Data Scientist
The tech round was pretty easy, covering SQL and a case study. The final round consisted of two case study rounds, one business partner behavioral round, and a final HM round that included both behavioral questions and a case study (so I had 3 case studies in total). I think I messed up in one of the case study rounds, so you should really prepare well for this. Make sure to have a clear structure for answering questions, research DD products and the customer funnel, and consider the impact on all parties involved (especially in a 3-sided marketplace). Also, be really good at A/B testing, including all the steps, interpreting results, and making tradeoffs.
- Could you describe the steps you would take to test feature x?
Data Scientist
The hiring journey kicks off with an HR screening, which involves a basic case study and an SQL test. After that, there are three more in-depth case study interviews. The whole process wraps up with a final chat with a Product Manager. Plan for this to take about two weeks.
- For the PM interview, make sure to have plenty of personal stories ready, especially for common behavioral questions like handling conflict.
- Regarding the case studies, they're quite challenging. Focus on thoroughly preparing metrics, promotion strategies, and the ins and outs of A/B testing, as this is crucial and will definitely be a part of your assessment.
Data Scientist
I had a technical screen that was split into two parts: 30 minutes for SQL and 30 minutes for a case study. The interviewer for the SQL part was quite unprofessional, not even offering a greeting before diving into the questions. She didn't type out the four SQL questions, expecting me to recall them, and wasn't very clear when stating them. When I asked her to repeat a question due to a poor internet connection, she stated she had already asked it. Most unusually, when I tried to use a table created in question 1 for question 2, she insisted I retype the entire query, and the same happened for questions 3 and 4. I ran out of time, which I feel could have been avoided with a more professional and reasonable interviewer. It was a very negative experience, and I'm glad I was rejected as it highlights potential issues with interviewer training and company culture.
- Some SQL questions
- A case study
DoorDash Data Scientist Interview Questions
Quoted word for word from DoorDash interview reports.
“Given that 3 individuals ordered food from 5 distinct restaurants, determine the third fastest delivery for each person.”
Read reports →“Given that deliveries in the LA area are experiencing a 10-day delay, what are the potential causes for this issue?”
Read reports →“Given a dataset with various delivery details and the actual delivery times, select and train a model using your choice of algorithm to predict delivery time.”
Read reports →“Could you write a Python program to parse dates and format them for food delivery cars?”
Read reports →“In the context of urban versus rural settings, how would you determine the minimum detectable effect?”
Read report →“What was the average order value for a specific item within a given time frame?”
Read report →“Could you determine the percentage of top customers within orders and how frequently they placed them using SQL?”
Read report →“If a sample size calculation indicates that 2 days are sufficient for an experiment, would you adhere strictly to that duration?”
Read report →“For each case study, how would you design an experiment to measure the impact of a 5% discount on delivery fees?”
Read report →Formats, difficulty and experience
Across all 133 DoorDash interview reports.