READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 57 of 153
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Building a Dasher Payout API
I received the Code Craft task as a Dasher payout calculation API problem. Dasher Payout Calculation API Overview The prompt said that, as part of a migration from a monolith to a microservice architecture, the team was building a new Payments Service. My task was to implement the Dasher payout logic, which required calling an upstream dependency to retrieve the relevant data. Goal Create this en…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Dasher Pay Phone Screen with a Surprise Sweep Line and Peak Windows Follow-up
This was the dasher pay question from the interview reports on the forum. I spent a good chunk of time up front discussing the requirements and the data shape. I wanted to get part 1 done with a simple algorithm first and worry about the rest later, and I had already finished writing it, but the interviewer was clearly unhappy and hinted that I should use a sweep line. Changing the code took quit…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Five Onsite Rounds Including a Live AI Coding Challenge
Round 1 — Code Craft: Bootstrap / Aggregator API Problem You are tasked with implementing an API that exposes the required information and is as resilient to failures as possible in order to ensure a good user experience. Implement a Bootstrap API that takes a user_id, pulls information from three existing upstream services — Consumer, Payment, and Address — and combines it into a single response…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Four Onsite Rounds, HM Chat Was the Roughest
System Design: Three-day donations. Specifically, you build a donation entry point for users, where the user submits their personal info plus how much money they want to donate to different organizations, and the problem gives you the assumption that you're only responsible for sending the money to the company's account. During the discussion the interviewer strongly suggested making it async, bu…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Four Onsite Rounds, Rejected Three Days Later
The phone screen was two months ago. The question then was [LeetCode] Koko Eating Bananas. I dragged it out for two months before I finally did the onsite. Four rounds. Round 1 was system design. The question was a three-day donation system. This round was 75 minutes long, but the interviewer and I ended up deep-diving into my project until the 45-minute mark before he even got into the design pa…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Four Onsite Rounds, Same Image Carousel Coding Problem
The onsite question had already been posted before — it's the same old image carousel problem. Four rounds onsite: Coding, 75 min: still the same old question — continuing to build comment and upvote features on top of the carousel. HM behavioral, 45 min: asked some standard behavioral questions, I talked about a project conflict / mistake, and they asked one that doesn't come up often — how do y…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Four-Round Onsite With an AI-Assisted Coding Round
First I got a reach-out from a recruiter, and we set up a quick call to go over the basics and the interview process. Then they scheduled the first technical round. After that round, the process got handed off to another recruiter, who also set up a quick call to go over some basic info, and at the same time scheduled the onsite. The first round was a Code Craft round, 1 hour. The second round wa…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Four-Round Virtual Onsite, Rejected in Three Days
Interview timeline: 6/15/2026 – DoorDash HR reached out on LinkedIn asking about my availability for an interview. 6/23/2026 – DoorDash first VO round, CodeCraft interview. The question was Dasher Pay — there are already write-ups about this problem, both here and elsewhere. There was a follow-up asking how to handle the double pay rate for dashers during peak hours. After I finished the code, th…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Full Onsite Loop, Then Grilled About Using AI More
DoorDash's full loop. I felt like their question bank isn't very big — pretty much everything is covered by write-ups here already. Specifically, the phone screen with the interviewer: dasher_pay. Same problem that's already been posted here, so pay attention to handling the input datetime. I used a few states to control the order's status. I forgot the follow-up, but again, the situations posted…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Loop Went Well, Then Rejected Over a Seniority Mismatch
LinkedIn HR reached out and said my background was a good fit; after an HR call, I moved into the interview process. The Phone Screen was an Easy coding question plus 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 work and my own experience. After that, HR reached out to schedule the Loop Interview. T…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — OA, System Design, Debug, and Craft Rounds
OA: Not LeetCode. You're given an actual scenario and you live-code a Service class on HackerRank right there — the logic is fairly simple, basically a bunch of if-else checks just to see whether your logic is clear, not really algorithm-based at all. But there were three parts. My advice: once you've nailed down the requirements, write fast, otherwise you definitely won't have time left to write…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Onsite With Three Coding Rounds Dressed Up as Delivery Problems
Posting my DoorDash interview experience. My overall impression is that this company's questions are very tied to the business — almost every question comes wrapped in a food-delivery scenario, even when the core is just a template problem. The upside is it's not boring to talk through; the downside is you have to unwrap the packaging first and figure out what the core problem actually is — get t…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Recruiter Call to a Four-Round Virtual Onsite, No Offer
Recruiter call: overall this was standard - basic info questions, no BQ really came up in this round. I recall being asked why DoorDash. Passed in a day or two, then got scheduled for the next round quickly - pretty efficient. Code Craft: a simplified version of Dasher Pay, simplified in that there was no coding extension like a double pay rate window. Instead, after finishing the basic coding, t…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Referral, Fast Loop, and a Painfully Slow Immigration Law Firm
Backfilling my full February DoorDash interview. It was a friend's referral. The process moved really fast, probably because my previous team and this team were a very close match in terms of business. The guidance said the coding round would be "coding with AI", but in the actual interview there was no AI assistance and no AI round, and the interviewers said they had never heard that AI was allo…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Rejected After a Dasher Pay Coding Screen With No Starter Code
I got a question that's pretty common on the forum, a combination of a Bootstrap-style problem and DoorDash Pay. The interviewer didn't give me any starter code, just the description below. He said to assume I'm a downstream service and the data comes from upstream. The answer I wrote turned out to be correct, it's just that the data was test cases, not data mocked from an upstream interface. A f…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — Resilience, Payments, and Concurrent Dispatch
The author describes an unsuccessful DoorDash interview process beginning with a coding screen about coordinating calls to downstream services. Follow-up discussion addressed failure handling, retries, and when requests should be allowed through or blocked during faults. The final interviews included a donation-service design covering payment processing, failures, lost connections, and duplicate…
Interview experiences · DoorDash
DoorDash Software Engineer Interview Experience — System Design, a Dasher Debugging Round, and an AI Pair-Programming Round
SD round - from the prep notes, a food review system. Debug round - also from the prep notes. The question was about adding a dasher and randomly picking a dasher. The bugs included, roughly: A boundary issue when the map is empty A logic issue: when you delete a randomly-selected key from the map, you need to move the last element into the deleted slot and update the index. If you don't handle t…
Interview experiences · DoorDash
DoorDash Software Engineer interview: internal electric-motor design screening
It began with a phone call with the recruiter. She was specific about the kind of person she was looking for, then asked technical questions focused on internal electric-motor design knowledge. The material was more targeted than I expected, and it was clear that the screen was trying to establish an exact fit with that technical background. Location: San Francisco, CA. Overall feedback: neutral.…
Interview experiences · Dropbox
Dropbox Product Manager interview: offer withdrawn after VP round
My loop started with a long setup: a recruiter call, followed by Zoom conversations that combined case-study work with situational questions. I spoke with a hiring manager and then had a more technical conversation with an engineering manager. After that came a presentation-focused stretch. I met with several product managers to present a case study and also had a culture discussion with product…
Interview experiences · Dropbox
Dropbox Product Manager take-home case and presentation
After a recruiter screen, I moved into a sequence that increasingly felt like a full product loop. It included a hiring manager conversation, several meetings with product and other stakeholders, a take-home product case study, and a final presentation. The process took about a month. I was told it would be fast, but scheduling became stop-and-start, with meetings being moved on short notice. The…
Interview experiences · Dropbox
Dropbox Software Engineer interview after the CodeSignal assessment
I applied for the SWE Summer 2026 internship in Canada and was sent an online assessment through CodeSignal. After completing it, the only clear next step listed was to wait for a recruiter call. That was essentially the whole process I experienced: I passed the assessment, received an email saying I had moved forward, and then waited to see whether a recruiter would contact me. There wasn’t much…
Interview experiences · Dropbox
Dropbox Software Engineer interview: CodeSignal assessment followed by rejection without a conversation
My Dropbox process felt unusually automated and cold. I applied online, got an invite link to complete a CodeSignal assessment shortly after, and then received a rejection without ever speaking to anyone at the company. No human conversation came between the assessment and the decision. Because I never had a chance to clarify anything or show context beyond the coding test, the outcome felt "not…
Interview experiences · Dropbox
Dropbox Software Engineer Interview Experience — A Hangman Variant and a Recursive Async Job Twist
The OA was a design question — you needed to implement a class that supports some basic operations, similar to a banking system. Next is the onsite, split into two stages total. This post mainly covers the first stage. Behavioral: This round mainly revolved around one of my bigger projects, and we went pretty deep into it. The interviewer was more like digging into specific points to discuss furt…
Interview experiences · Dropbox
Dropbox Software Engineer interview: OA, phone screen, and delayed feedback
The early stages of my Dropbox process were the most frustrating. I had an OA and then a phone screen where the HR contact didn’t really dig into my background or ask many questions about me. Most of the call was about next steps, and then the process went quiet. What threw me off was how poorly the later communication matched what I was being told. I was repeatedly led to believe things were goi…