The interview process began with an initial technical screen. During the phone screen, I was given a tricky Python question and expected to solve it, providing the output. While the question itself wasn't difficult, it did take some time to solve. The interviewer seemed inexperienced, as she didn't fully follow my logic during the explanation. When I wanted to print an intermediate step, we couldn't, and we spent five minutes just figuring that out. The interviewer never accounted for this time when I asked if we could revisit the code after my SQL questions. However, she stated she understood my process and that it was clear when I explained it (she was likely just trying to finish the interview). For the SQL questions, the emphasis was on trivial details like rounding numbers. I arrived at a solution which the interviewer acknowledged, and she was also confused why it wasn't showing the correct result. Later, after six minutes, we figured out that the rounding was applied before I performed the % calculation. Overall, the interviewer wasn't very experienced and focused more on trivial components rather than problem-solving.
Python Question:
Was asked about Friends and suggestions for restaurants. Mostly Dict and Lists related.
SQL:
Was a data model of DoorDash and questions around that.
The following metrics were computed from 1 interview experience for the DoorDash Senior Data Engineer role in Seattle, Washington.
DoorDash's interview process for their Senior Data Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for DoorDash's Senior Data Engineer interview process in Seattle, Washington.