Engineering Manager interview
at Uber.

Tell-me-about-a-time stories on ownership, conflict, and impact — scored against this company's real values.

1. 01 Describe your management philosophy and a time it was tested when you had to lead a team through a high-pressure marketplace incident.
2. 02 Tell me about a time you had to compete with other teams for limited resources and how you advocated for your team's roadmap.
3. 03 Give an example of how you handled a sustained low performer while still getting the best out of your high performers.
4. 04 Tell me about a time you drove a bold, ambiguous technical bet across a cross-functional org and how you aligned stakeholders.

The hard screen for the craft itself — talked through out loud, not whiteboarded in your head.

1. 01 Walk me through the architecture of a system you owned that ran at high scale and the toughest reliability trade-off you made.
2. 02 How would you guide a team through designing a geo-partitioned dispatch service, and where would you push back on their initial design?
3. 03 How do you set and enforce technical standards like code readability and on-call quality across a team that ships fast?
4. 04 How would you architect the migration of a monolithic trip service to microservices without disrupting live rides?

Open-ended design of the systems this company actually runs, with the interviewer probing your tradeoffs.

1. 01 Design Uber's driver-rider matching and dispatch system and explain how you'd staff and sequence the team building it.
2. 02 Design a real-time ETA computation system and describe how you'd divide ownership and on-call across your engineers.
3. 03 Design a high-throughput streaming pipeline for driver location updates and the operational guardrails you'd put in place.
4. 04 Design a surge pricing platform and walk through how you'd phase rollout, monitoring, and incident response across markets.