Don't waste your valuable time interviewing with this company.
I got a call from a recruiter after applying online.
1st Phone Interview: This was an easy LeetCode question with a simple object-oriented design question and a SQL query. I aced this interview and was expecting an on-site interview.
But...
2nd Phone Interview: I think because I'm from the East Coast, they wanted to make sure I knew my stuff.
There was one algorithm question, which I'd say was medium-level LeetCode. It wasn't tough, but my solution had to have the best complexity. It was about sorting an array. I won't reveal the exact question, but you should be able to figure out "sorting with best complexity." Then, there was an easy-level object design question.
I went for the on-site interview after a week.
1st Round - Algorithm: This was medium-hard. The interviewer was super knowledgeable and made sure I understood the question. I did very well with the best solution possible.
2nd Round - Engineering Values: General behavioral questions.
3rd Round - PM Interview: The PM was super nice and explained the team really well, making sure I was interested in working with them.
4th Round - Previous Projects: I would suggest being careful with this round. Do not throw in any buzzwords if you haven't worked on them. Luckily, I was involved in a lot of architectural meetings in my previous companies, so I knew our system inside and out. I did pretty well.
5th Round - System Design: This was an easy-medium level question. The interviewer was awesome; he was super chill. I think I aced this interview as well.
6th Round - "The Fun Part": The interviewer was super disinterested. He came into the interview room, copy-pasted a code on an online editor (designing a game I'd never played), and didn't explain what to do, just said, "Read it and do it." I was like, "Okay." I had a hard time figuring out what the game did, then implemented the first task in the code. He tested running the code with different inputs, and luckily, all worked. I was already losing interest because he wasn't saying a word and was doing his own work on his laptop. What's the point of him being in the interview room when all he has to do is run test cases and not say a word? Then, time ended.
I kept pinging the recruiter for two days with no response. I don't blame them; it usually takes a week for a decision. On the third day after the interview, I got a call from the recruiter saying I was rejected because of the last round. Do they not care about the other five on-site and two phone interviews? They just rejected me based on some vague reason that I took extra space while solving the problem. If that last interviewer had spoken a word about space, I would have fixed it in a second. I was more concerned about best time complexity than best space complexity.
Anyway, please don't waste candidates' time when all it takes is one disinterested interviewer's opinion to reject a candidate. Luckily, I have offers from Big 4 and a few other companies. I was really planning to leave those offers just for DoorDash and a few people I met during the interview.
I would suggest to others, if you are short on time like I was, don't bother applying here because it's a waste of your time.
LeetCode Medium
The following metrics were computed from 43 interview experiences for the DoorDash Software Engineer role in San Francisco, California.
DoorDash's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having good feelings for DoorDash's Software Engineer interview process in San Francisco, California.