The interview process was monotonous, with repetitive questions about basic concepts. The interviewer seemed disinterested, sticking rigidly to a script. There was no engaging discussion or challenging problems to solve, making the experience dull and unremarkable. It felt more like a checklist than a genuine assessment of skills.

I can tell for one, since I was able to copy-paste the exact question. This question was for a project and delivery execution round.

Uber has scaled from 1 million daily active users (DAU) to 10 million DAU. Now they want to rebuild some key pieces of their architecture for the next 3-4 years to support 50 million DAU. You are responsible for managing the driver tracking system and a ride allocation system. You have planned to rebuild a new system from the ground up and migrate the systems from a monolith to a microservices architecture.

Assume that other systems like User, Authentication, Notifications, Driver Profiles, etc., are already existing and accessible via some interface (REST API).

Plan the work. Some starter questions:

• Tech design (High-level system design only)
• What would be your milestones? Define MVP and subsequent iterations.
• What will be your execution plan? What do sprints 1, 2, 3, etc., look like?

Driver Tracking system features:

• Live tracking till trip ends
• ETAs (Use Google Maps)

Ride Allocation:

• Matching algorithms to find the most appropriate driver based on rules like driver earnings, ratings, ETA, etc.
• Allocating the driver to a trip.