READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 56 of 153
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — Onsite ML System Design for the Home Feed Recommender
Problem background: design a store recommendation system similar to the app's home page. Interview process & core follow-ups: Overall architecture and hard constraints The scenario given right away was home page recommendation. User input is extremely sparse — basically just the User ID and current location. The system has a couple of hard constraints: the stores surfaced must be within delivery…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — Recycled SQL Questions and a Biker-Project Case Round
HR screen -> Round 1 30-min SQL round: 4 old/frequently-asked questions, with my basic approach: Q1. Percentage of high frequency customers (order>30) each month. Get cus_id, month, order_count. Group by month, cus; count(distinct case when oc> then cus end)/count(distinct cus) Q2. Customers who ordered the most, excluding high-frequency customers, each month (follow-up: the most frequent custome…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience: SQL, cases, and virtual onsite
An HR-style call covered the role, compensation and benefits, and the hiring flow. The technical screen began with four medium SQL questions in a HackerRank-style format. I barely had time for the last one and got the impression they did not expect a full solution. A case study followed, where I explained how I would approach an open-ended business problem. After passing, I had a virtual onsite w…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — SQL Round Ran Out of Time, Then a Bike Case Study
This was the first interview of this hiring round for me, and I wasn't prepared — I underestimated how much time management the SQL portion would take, and I didn't finish it before time was cut off. The SQL question was a real, previously-reported one. It asked for: Users who spent more than $100 in a month The same as above but excluding the person with the highest spend each month Month-over-m…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Data Scientist Interview Experience — Three Case Rounds, No A/B Testing Background
I'd seen a lot of phone screen reports for this role and passed it pretty easily, but the onsite was like the reports I'd read about — genuinely hard, and unlike anything I'd seen before. My background is as a DS who has always worked on modeling, with a little bit of product analytics experience mixed in. I don't have hands-on experience running A/B tests, so on the onsite, the experiment design…
Interview experiences · DoorDash
DoorDash Data Scientist interview: SQL and ambiguous cases
The first round combined a 30-minute SQL assessment and a case study. SQL felt very easy, while the case portion was more difficult: two prompts were straightforward and one was genuinely ambiguous. The next round included three case studies and an interview with a cross-functional partner. The interviewers were kind, but I still had to keep structure and clarity across the scenarios. I did not r…
Interview experiences · DoorDash
DoorDash Data Scientist interview: SQL and case rounds with one missed concept
After a recruiter screen, I had two screening rounds involving SQL and a case study, followed by more case-study rounds. The onsite-style loop also included a meeting with a cross-functional partner, and I later spoke with a hiring manager. The setup was professional and moved quickly. The data-science questions were not easy. I had done well on the early screens and one case, but a later case br…
Interview experiences · DoorDash
DoorDash Data Scientist interview: SQL round and case study before a quick rejection
The loop felt almost entirely about training the interviewers. There was no separate recruiter screening call. It began with a SQL round, then a case study. The recruiter mostly gave a brief introduction, while the two technical sessions carried the process. I finished the SQL questions and explained my thinking to the recruiter as things moved along. The case study also went well, and it felt li…
Interview experiences · DoorDash
DoorDash Data Scientist interview: take-home after manager screen
I had a quick phone screen and then a Zoom meeting with the hiring manager that lasted about 30 minutes. After that, I completed a take-home assignment and submitted it within 72 hours. That was the end of the process for me. My submission did not move forward, and I did not get another live round. The path looked straightforward on paper, but it was still frustrating because all of my momentum r…
Interview experiences · DoorDash
DoorDash Senior Software Engineer Interview Experience — Four Onsite Rounds, Rough Code Craft
Let me start with the technical screen: a fairly classic multi-source BFS problem — find the nearest source for every cell in a 2D grid. Medium difficulty, leaning toward the basic side. Next is the onsite, four rounds in total. Round 1 was system design. The first 15 minutes were spent talking about a recent project of yours, then it moved into the design question. The task was to design an app…
Interview experiences · DoorDash
DoorDash Senior Software Engineer Interview Experience — Four-Round VO, Menu Review Design Stuck in Schema Details Until Minute 45, Rejected
The phone screen was coding plus a project deep dive. The coding was that Dasher Pay question. The interviewer was really nice: right after I finished writing the code, they just told me not to worry, they were passing me. For the project deep dive, the interviewer listened really carefully and asked a lot of questions. The VO was four rounds. Round 1 was AI coding. I think they have two coding q…
Interview experiences · DoorDash
DoorDash Senior+ Software Engineer Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Senior+ Software Engineer Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Software Engineer interview: bilingual 30-minute recruiter call
After the recruiter contacted me, I had an initial conversation of about 30 minutes. The call began in Portuguese and then continued in English. It stayed general: we discussed my previous experience and what I was seeking in compensation, including salary and benefits. It did not advance to the technical part at that stage, so this was the only impression I had of the process. Location: São Paul…
Interview experiences · DoorDash
DoorDash Software Engineer interview: durable refund DAG system design
The process was demanding from the start. After several rounds, I handled behavioral questions that, interestingly, matched my real experiences well. The technical work carried the most weight, especially a system-design challenge about building a durable DAG flow for order refunds. I was overwhelmed at first, but my earlier system-design interview study helped me organize the approach and unlock…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — 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…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — An AI-Coding Onsite Round, Rejected After System Design
Screen interview: Code Craft: Dasher Pay. Didn't feel too hard — just make sure to talk through your approach with the interviewer before you start coding. It's a high-frequency question from the forum. Onsite Round 1: Debugging: Round Robin Load Balancer. Also a forum question. Onsite Round 2: AI Coding. They had me set up a microservice locally on my own machine, specifically to handle abnormal…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Bootstrap Phone Screen, Consistent Hashing Debug Round, AI Coding DAG, Rejected
Phone screen: it was the classic bootstrap question, same as most of the interview reports out there. The hard part of the question is adding the HTTP response status handling on top. I strongly recommend the public EngineBogie write-up of this one ("Implement a BootstrapService to aggregate data from multiple services"). Onsite: Debug: the question was the same round robin one. It's actually not…