J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez DoorDash en nov. 2023
Entretien
I spoke with a recruiter for 30 minutes about my past job experience. Then about a week or two later I had a 60 minute technical phone screening with an engineer at the company. It was a pretty standard shared code environment. I didn't make it farther.
Questions d'entretien [1]
Question 1
I got asked a variation of the Design A File System question on Leetcode. I thought the interviewer was really good. He started out with a very simple version of the problem and built it up as we went. I made a simple mistake and the interviewer pointed it out.
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