First Round Technical Phone Interview: This was a technical phone round that was overall positive. The problem was a LeetCode medium, and the expectation was to understand my thought process. I did well, had a working solution, and also explained how I would optimize it.
Virtual Onsite: This consisted of four rounds. Here is my experience:
Coding Round 1: A LeetCode hard problem, which was one page long. It took me about 15 minutes just to read and understand the problem, leaving me with only 25-30 minutes to solve it. There were no hints or guidance. It felt like a one-way interview designed to make me fail, and I did fail, but I never stopped trying.
Coding Round 2: A LeetCode medium problem. The interviewer explained the problem, and the data was formatted in tables. I had to extract the data into a format that would help me solve the problem, and I had flexibility in doing so. I came up with the input and was able to solve the problem, but I ran into some syntax issues due to casting. Since the platform used was HackerRank, I could not debug effectively within the given time. I did, however, go back to see the LeetCode solution and know that my solution would have worked. I also explained its optimization.
Manager Round: This is subjective. I think the conversation was really good, and I enjoyed talking to the Hiring Manager.
System Design: This is also subjective to what the interviewers perceive. Overall, I think this went well, and the solution I provided was definitely solving the problem at hand.
I was overall disappointed with the coding rounds and do not understand what I was being tested for. It was definitely not coding skills, as the problem was not fair enough to solve in 45 minutes. I am pretty confident even the interviewer would not be able to solve it in 45 minutes.
Coding Round 1 A LeetCode hard problem, which was one page long. It took me about 15 minutes to just read and understand the problem, leaving me with only another 25-30 minutes to solve it. There were no hints or guidance. It felt like a one-way interview, particularly set up to fail, and I failed but never stopped trying.
Coding Round 2 A LeetCode medium problem where the interviewer explained the problem. The data was formatted in tables, so I had to extract it into a format that would help me solve the problem, and I had flexibility on that. I came up with the input and was able to solve the problem but was running into some syntax issues due to casting. Since the platform used was HackerRank, I could not debug through it in the given time. However, I did go back to see the LeetCode solution and know that the solution would have worked. I also explained the optimization of the same.
The following metrics were computed from 179 interview experiences for the DoorDash Software Engineer role in United States.
DoorDash's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for DoorDash's Software Engineer interview process in United States.