- Published on
Doordash onsite | SDE2 Backend | Reject
- Author
- Shared Anonymously
My onsite consisted of 4 rounds
Round 1: Hiring manager
Q1: There's an increasing number of wrong/incorrect orders and deliveries. Tell me how would you approach solving this problem.
Q2: Tell me about a time when you got critical feedback and how you reacted/responded to it.
I think there were a couple more "tell me about a time when" questions but I forgot.
Round2: System design
Q1: Walked through a project that I think was most challenging. Described non-tech and tech challenges
Q2: System design: design review and rating system for food items of restaurants.
Round 3: Code craft
Ok no, it's not leetcode.
Implement an API that has several dependency API calls to downstream services. I am given templates/abstraction of those dependency API calls.
Things I addressed:
- 4xx/5xx error handling
- Parallelizing API calls
- Retries
- Some refactoring so that won't repeat too much code for repeated API calls
Round 4: Debugging
Someone has mentioned it in some other post. It's round robin algorithm. I'm given the implementation and unit tests. The bugs are in both the implementation and the tests. The end goal is when hit "Run" all tests should pass.