J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez DoorDash en oct. 2022
Entretien
1st Round TPI: Had a technical phone round which overall was positive and the problem was a leetcode medium but the expectation was to understand my thought process. I did well here and had a working solution and also explained how I would go about optimizing the same. Virtual Onsite: This was a total of four rounds and below is my experience- 1. Coding Round 1 - A LC hard problem which was one page long, it took me about 15 minutes to just read and understand the problem and was left with just another 25-30 to solve the problem. There were no hints no guidance, it felt like a one way interview which was particularly setup to fail and I failed but never stopped trying. 2. Coding Round 2 - A LC medium problem where the interviewer explained the problem and the data was formatted in tables so I had to extract the data into a format that would help me solve the problem and I had the 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 and since the platform used is hackerrank I could not debug through in the given time but I did go back to see the LC solution and know that the solution would have worked, also explained the optimization of the same. 3. Manger Round - This is subjective and I think the conversation here was really good and I enjoyed talking to the HM. 4. System Design - This is also subjective to what the interviewers perceive but overall think this went well and the solution I had 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 definitely not coding skills as the problem was just not fair enough for solving in 45 minutes. I am pretty confident even the interviewer would not be able to solve it in 45 mins.
Questions d'entretien [1]
Question 1
1. Coding Round 1 - A LC hard problem which was one page long, it took me about 15 minutes to just read and understand the problem and was left with just another 25-30 to solve the problem. There were no hints no guidance, it felt like a one way interview which was particularly setup to fail and I failed but never stopped trying. 2. Coding Round 2 - A LC medium problem where the interviewer explained the problem and the data was formatted in tables so I had to extract the data into a format that would help me solve the problem and I had the 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 and since the platform used is hackerrank I could not debug through in the given time but I did go back to see the LC solution and know that the solution would have worked, also explained the optimization of the same.
coding online assesment virtual onsite. interviewers were professional and helpful. asked to deep dive on project. recruiter was responsive and could align with offer deadlines. was helpful with negotiations. coding problems were average difficulty.
Walking into the coding interview, I was taken aback when they asked about finding the K nearest restaurants based on coordinates. Just days before, I had stumbled on a mock on prachub.com that mirrored this question almost exactly. The interview felt straightforward, but I struggled with some behavioral questions. Overall, the experience was underwhelming; I expected more technical depth. After several rounds, they decided to go in another direction, which was disappointing given my prep efforts.
Questions d'entretien [1]
Question 1
Given a list of restaurants with their coordinates and a user's location, find the K nearest restaurants
J'ai passé un entretien chez DoorDash (Londres, Angleterre)
Entretien
it was very easy, they ask basic programming questions, can be solved with minimal prep, however they ask a lot about why u want to work here, be prepared to talk for a long time