After an initial recruiter call to go over how the process would run, I moved into a live coding interview that felt brutally time-pressured. It was a mix of SQL and Python: I had four SQL prompts and one Python problem, and the last SQL questions got especially complex. While I was trying to work through my reasoning out loud, the interviewer kept interrupting and effectively derailing my train of thought, which made the already tight timeline feel impossible.
The Python part itself was fine, but the testing was where I got thrown off—there were edge cases that weren’t clearly signaled in the prompt. Even when my approach and syntax were correct for the SQL environment I understood, the evaluation ended up being picky about implementation details. I worked hard to adjust and still ran into time loss chasing the version that would pass their tests, and that experience left me with a very negative feeling about the process overall. I never got an offer, and the lack of helpful guidance during the coding portion made it hard to trust the outcome.
6 months ago
Difficult Neutral United States
My process started with a technical screening, then it quickly expanded into a longer loop with multiple rounds combining technical work and business/product-style prompts. Across the interviews, I was asked to work through things like product analytics, SQL and Python, and a system-design-style discussion. There were also business questions that didn’t feel like pure engineering trivia—one of the themes was building out a fitness-related application, which then led into dimensional modeling where I had to think in terms of facts and dimensions.
Overall it landed as difficult and fairly comprehensive: the bar wasn’t just writing code, it was stitching together analytics thinking, data modeling, and higher-level communication. I didn’t end up with an offer, and the experience felt demanding in a way that went beyond a straightforward coding test.
6 months ago
Average Positive United States
I went through a four-round loop that started with a technical section focused on SQL and Python. The coding level matched what I’d seen in LeetCode-s…
> 1 year
Difficult Positive São Paulo, São Paulo
I applied through the portal and ended up going through a fairly long sequence of interviews, about four to five rounds. The whole journey was centere…
> 1 year
Difficult Negative United States
My interview felt hostile from the start. The interviewer spent a chunk of time on the introduction and then immediately selected a tough, complex Pyt…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Screening
The interview process typically begins with a technical screening that includes live coding sessions focused on SQL and Python, often with tight time constraints and a mix of problem types. Candidates should prepare for both straightforward coding challenges and more complex SQL queries, including window functions.
SQLPythonLive Coding
Data Modeling & System Design
Candidates can expect to engage in discussions around data modeling and system design, often framed within case studies relevant to DoorDash's products. This requires a solid understanding of dimensional modeling and the ability to communicate design trade-offs effectively.
Data ModelingSystem DesignCase Studies
Behavioral Interviews
Behavioral interviews are a significant part of the process, focusing on candidates' past experiences with technical challenges and teamwork. Expect to answer questions using the STAR method to illustrate problem-solving and communication skills.
BehavioralSTARCommunication
Interview Environment & Difficulty
The overall difficulty of the interviews is reported as high, with some candidates experiencing a stressful or unprofessional interview environment. It's important to remain calm and focused, as the pressure can be intense during coding and technical discussions.
DifficultyStressful EnvironmentPressure
Loop Structure & Timeline
The interview loop typically consists of four to five rounds, combining technical and behavioral assessments, often in quick succession. Candidates should be prepared for a comprehensive evaluation that assesses both technical execution and analytical thinking.
Interview LoopTimelineComprehensive Evaluation
Preparation for Edge Cases
Candidates should prepare for potential edge cases in coding problems, as some interviewers may focus on implementation details and testing rigorously. Practicing a variety of scenarios, especially in SQL and Python, can help mitigate unexpected challenges during the interview.