Senior Software Engineer Interview Prep
Prep for Uber's senior IC loop - distributed systems depth, location-aware design, and cultural emphasis on ownership and impact.
About this loop
Uber's engineering culture is shaped by what they build: a globally-distributed real-time marketplace that coordinates riders, drivers, restaurants, couriers, and dispatchers across millions of concurrent events. The interview loop reflects this with strong emphasis on distributed systems, location-aware design, and high-throughput backend architecture. Senior IC candidates face two coding rounds (Medium-to-Hard with pace expected), two system design rounds (one product-flavored, often dispatch or marketplace; one infra-flavored, often payments, fraud, or logging at scale), and a behavioral round. The culture has changed significantly under Dara Khosrowshahi - the previous 'always be hustling' aggression has been replaced with more sustainable collaboration norms, but the technical bar remains high and ownership is heavily valued. Uber's tech stack is polyglot (Go, Java, Python, Node) and engineers are expected to navigate multiple codebases. Behavioral signal probes how you handle ambiguity, drive technical decisions, and ship in a marketplace where the failure modes affect real-world transactions.
The interview loop
- 1Recruiter screen30 minutes. Background, level calibration (L4 vs L5 vs L6), team interest. Uber recruits across rides, eats, freight, payments, infrastructure, and ML platforms.
- 2Technical phone screen60 minutes. One coding problem at Medium-to-Hard. Algorithms or data structures with attention to edge cases and complexity.
- 3Onsite: Coding round 160 minutes. Algorithmic problem, often with a real-world flavor (matching, scheduling, geographic queries). Pace and clean implementation matter.
- 4Onsite: Coding round 260 minutes. Second coding round with a different interviewer. Often more applied or systems-flavored.
- 5Onsite: Product system design60 minutes. Marketplace and location-aware designs are most common: ride dispatch, surge pricing, restaurant search and ordering, courier assignment. Drive the conversation, defend tradeoffs explicitly.
- 6Onsite: Infrastructure system design60 minutes. Lower-level: distributed payment processing, fraud detection pipelines, log aggregation at scale, distributed rate limiting, geosharding.
- 7Onsite: Behavioral / hiring manager45-60 minutes. Senior IC behavioral signal - driving technical decisions, navigating ambiguity, mentoring, working across teams in a marketplace where failures have real-world consequences.
What Uber actually evaluates
- →Distributed systems depth - sharding, replication, consistency, fault tolerance, geosharding
- →Driving system design without prompting - silence is a downlevel signal at L5
- →Real-world thinking - marketplace failures affect riders, drivers, restaurants - design with operational impact in mind
- →Pragmatism over theoretical purity - 'good enough at 99.9% with simple recovery' beats 'perfect at 99.999%'
- →Senior behavioral signal - mentoring, technical influence, ambiguity navigation
- →Polyglot fluency - comfort moving across Go, Java, Python codebases
Topics tested
System Design
Two design rounds at L5. Marketplace and location-aware designs dominate the product round (dispatch, surge, search, courier matching). Infra round leans toward payments, fraud, logging, distributed rate limiting.
Algorithms
Medium-to-Hard across two coding rounds. Real-world flavored problems are common - matching, scheduling, geographic queries, interval problems.
Data Structures
Hash maps, heaps, graphs, geohashes, R-trees. Uber's geographic problems favor structures that index spatial data efficiently.
Databases
Comes up in system design at depth. Sharding strategies, hot partition handling for geographic data, multi-region replication, transactional patterns for payment systems.
Behavioral
Senior IC signal. Stories about technical influence, mentoring, navigating marketplace tradeoffs, recovering from production incidents.
Networking
Surfaces in distributed systems design - service mesh patterns, retries, timeouts, idempotency. Useful background.
System design topics tested in this loop
Curated walkthroughs for the bounded designs that show up in Uber's system design rounds. Capacity estimation, architecture, deep-dives, and trade-offs.
Ride-Share Dispatch
HardGeo-indexing, real-time matching, ETA prediction, and surge. The canonical geo-spatial design problem with hard real-time constraints.
Rate Limiter
MediumFive algorithms, three sharding strategies, one fail-open vs fail-closed decision. The bounded design that surfaces in every backend interview loop.
Distributed Cache
HardConsistent hashing, eviction, replication, and what really happens when a single hot key takes down the cluster.
News Feed
HardThe classic write-vs-read amplification trade-off. Push, pull, or hybrid fanout - and how to handle the celebrity user with 100M followers.
URL Shortener
MediumThe canonical bounded system design problem. Read-heavy, hot-key prone, and a great vehicle for hashing, caching, and capacity estimation.
Behavioral themes tested in this loop
Sample STAR answers, common prompts, pitfalls, and follow-up strategies for the behavioral themes that decide Uber's loop.
Ownership
Amazon LPTested at every level, scored harder at senior. Did you take responsibility for outcomes - or just for tasks?
Bias for Action
Amazon LPSpeed matters. But the principle is reversible-vs-irreversible reasoning, not 'I work fast.' Get this distinction wrong and the answer reads as reckless.
Ambiguity
GeneralTested at Google, Anthropic, OpenAI, and any senior+ loop. Strong candidates show how they get curious; weak candidates show how they get anxious.
Conflict
GeneralThe most universal behavioral question. Tested everywhere. The signal is in how you investigate the disagreement, not in how you 'won.'
Learning from Failure
MicrosoftMicrosoft's Growth Mindset core. Also tested at Google, Anthropic, and any company that screens for self-awareness. The signal is whether you actually changed.
Curated practice questions
349 MCQs and 100 coding challenges, grouped by topic. Free preview shows question titles - premium unlocks full content.
System Design · 68 MCQs
Browse all in System Design →Algorithms · 77 MCQs
Browse all in Algorithms →Data Structures · 44 MCQs
Browse all in Data Structures →Databases · 49 MCQs
Browse all in Databases →Behavioral · 63 MCQs
Browse all in Behavioral →Networking · 48 MCQs
Browse all in Networking →Algorithms - Coding challenges · 71 challenges
Browse all coding challenges →Data Structures - Coding challenges · 29 challenges
Browse all coding challenges →Practice in mock interview format
Behavioral and system design rounds reward practice with a live AI interviewer that probes follow-ups, not silent reading.
Start an AI mock interview →Frequently asked questions
How much do I need to know about ride dispatch and marketplace design?
A lot. Uber's product system design rounds frequently center on dispatch, surge pricing, search and ordering, courier matching, and similar marketplace problems. Knowing geosharding, location-aware indexing (geohash, S2, H3), real-time matching algorithms, and surge pricing tradeoffs gives you concrete vocabulary that other candidates won't have. Uber publishes engineering blog posts about these systems - reading them is legitimate study material.
What's the difference between L4, L5, and L6 at Uber?
L4 is mid-level (3-5 YOE) - one system design round, mid-level behavioral signal. L5 is senior (5-8 YOE) - two design rounds, senior behavioral expected. L6 is staff (8+ YOE) - similar structure to L5 but with explicit technical leadership signal expected (driving cross-team decisions, mentoring multiple engineers, owning a system area).
How is Uber's culture different post-Khosrowshahi?
More sustainable, less 'always be hustling.' The previous era's aggression and ethical lapses have been replaced with stronger collaboration norms, real performance management, and more conventional FAANG-style work expectations. The technical bar remains high; the cultural friction has dropped significantly. Recruiters will discuss the cultural shift candidly if asked.
What is Uber's tech stack like?
Polyglot. Go is dominant for backend services (Uber is one of the largest Go shops), Java is heavily used in older systems and data infrastructure, Python is common for ML and data, Node for some web stacks. Mobile is iOS/Swift and Android/Kotlin. Engineers are expected to navigate multiple codebases - rigid 'I only do X language' candidates are downleveled or rejected.
How does Uber compare to DoorDash, Lyft, or Instacart as an interview target?
Uber is the largest and most operationally complex of the marketplace companies. DoorDash is the closest analog (logistics marketplace with similar dispatch and matching problems) and shares many design patterns. Lyft is smaller and faces some similar problems but at lower scale. Instacart and similar grocery marketplaces face the inventory and substitution complexity that pure ride-share doesn't have. The interview structures are broadly similar across these companies.
How long is the Uber loop end-to-end?
Recruiter screen to offer typically 6-10 weeks. Onsite is usually compressed to one or two days. Hiring committee review takes 1-2 weeks. Team matching can add 2-4 weeks but is often done up front (you interview for a specific team). Plan for 8-12 weeks total.