Uber Interview Questions
The coding and system-design questions asked in Uber interviews - with worked solutions, in-browser code execution, and active-recall review. 6 questions.
How Uber interviews software engineers
Uber's loop is structured and quick - often two to six weeks. It usually runs a recruiter screen, a CodeSignal online assessment, a technical phone screen, and an onsite of four to six rounds.
The onsite typically includes two coding rounds (one more specialization-focused), a system design round (required from mid-level up), a collaboration / leadership round, and a bar raiser. Most rounds run virtually even for onsite stages.
The interview loop
- 1Recruiter screen30-45 min on background, interest in Uber's domains, and comp; shapes the loop.
- 2Online assessment~70-90 min CodeSignal test, around four algorithmic problems from easy to hard.
- 3Technical phone screen~45 min live coding on real problems.
- 4Onsite loop4-6 rounds: two coding (one specialization), system design (60 min), a collaboration/leadership round, and a bar raiser.
What they look for
- Algorithmic coding speed plus depth in your specialization
- Scalable system design for real-time, high-throughput services
- Collaboration and leadership signal alongside the technical bar
How to prepare
- Prep the CodeSignal format - pacing across four problems matters.
- For design, study real-time and geo-distributed systems (dispatch, matching, surge).
- Have leadership and collaboration stories ready for the dedicated round and bar raiser.
Sources
- InterviewQuery - Uber software engineer guide - Process, coding questions, and prep.
- Exponent - Uber software engineer guide - Round breakdown with sample questions.
- Prepfully - Uber software engineer guide - Detailed onsite structure.
See every company's references on the interview-process sources page.
Practice questions
- Weather App
Design a forecast app like the Google or Apple weather app - one screen for the current location, a forecast that loads instantly from cache, an honest offline state, and a constrained background refresh.
Mobileeasy-1mo+2
- Messenger App(premium)
Design an Android messenger - a durable outbox so a tapped message survives a kill, a server-assigned per-chat seq so order is a property of the data, reconnect catch-up, and FCM wakeup for offline recipients.
Mobilehard-2mo+5
- Photo Gallery App(premium)
Design a Google Photos-style gallery - one timeline over the device and cloud libraries, background backup, full-resolution viewing, fresh-device restore.
Mobilehard-1mo+3
- Ride-Sharing App(premium)
Design an Uber / Lyft-lite Android rider app - a server-authoritative ride state machine, an idempotent ride request that survives a process kill, a 1-2 Hz driver-location stream interpolated to 60 FPS, FCM (Firebase Cloud Messaging) wakeup when the WebSocket is closed, and reconnect-and-reconcile under cellular drops.
Mobilehard-2mo+4
- Valid Parentheses
Stack-walk a bracket string to validate it, then localize the first error, then find the longest valid substring (LC 32).
Practicalmedium35m2mo+12
- Meeting Rooms(premium)
Given a list of half-open meeting intervals, find the minimum number of conference rooms; later phases assign specific room IDs and add capped capacity with priority eviction.
Practicalmedium35m2mo+9