Applied through LinkedIn and had an initial chat interview with the engineering manager the next day. All interviews were conducted remotely, mainly with engineers located at their San Francisco office.

I was given a take-home challenge to complete within an estimated 5 hours, which wasn't strictly timed.

After submitting the take-home challenge, I was asked to explain my logic and architectural decisions with an engineer in a follow-up technical screen. I really enjoyed this as the engineer I was paired with liked my implementation and asked insightful questions.

I made it to the final round, which involved four interviews in a day, each lasting about 1 to 1.5 hours.

• Engineering manager interview regarding leadership principles
• Knowledge domain interview (surrounding frontend/backend/DevOps principles)
• Technical interview involving an extension of the take-home project
• System design interview involving a practical implementation of a DoorDash feature (I enjoyed this interview and thought I performed best during this round as it was actually applicable and not as open-ended as other system design interviews I've experienced).

Overall, the process was really enjoyable, and I truly appreciated how the questions were more practical rather than traditional FAANG interviews that involve LeetCode-style questions.

I genuinely thought I did very well and enjoyed all the interviews. However, I was surprised by the rejection and that I was simply ghosted. The recruiter and engineering manager offered to provide feedback in their rejection email. Why ask the candidate if they have any questions after a rejection, then just ghost candidates?

Give an example of a time when you and a co-worker had a conflict.

Design an application according to these defined specs with a provided API.

What would you change/refactor/add to your app to make it production-ready?