Talentee
Uberadvanced

Uber Software Engineer Interview Questions

Uber's interview is famous for deep distributed systems questions — real-world matching, geo-spatial, and real-time event processing. Technicals are rigorous; behavioral rounds focus on resilience and impact.

Process length
4-8 weeks
Rounds
7
Questions
8
Mid-level TC
$240k–$340k (L5)
Practice Uber questions with AI

The Uber Software Engineer interview process

What to expect, in order.

  1. 1Recruiter screen (30 min)
  2. 2Phone screen with engineer (60 min — 1-2 coding problems)
  3. 3Onsite — typically 4-5 rounds
  4. 4Coding round (60 min)
  5. 5System design (60 min — often distributed systems / matching / geo)
  6. 6Architecture deep-dive (60 min, for senior+ — past projects)
  7. 7Behavioral / values round (45 min)

What Uber actually evaluates

Uber's culture has evolved significantly from the early-Travis era. Post-Khosrowshahi, the emphasis is on customer + driver + eater experience. Behavioral rounds reflect this — they want engineers who care about the marketplace, not just the tech.

Customer obsession (riders + drivers + eaters)
Build with heart — execute with rigor
We are owners — long-term thinking
We celebrate differences
Trip obsessed — every trip matters

Process quirks worth knowing

Uber engineers think in marketplaces. System design rounds almost always touch on matching, surge pricing, real-time event processing, or geo-spatial. Practice these specific patterns.

8 questions Uber actually asks

Each question includes the tip for answering and what the interviewer is actually evaluating.

Q1design

Design Uber's driver matching system.

Why Uber asks: The most common Uber system design question. They want awareness of geo-spatial, real-time, and marketplace dynamics.
How to answer: Cover: geo-indexing (H3, Geohash, R-tree), driver location updates (frequency, batch), matching algorithm (nearest, ETA-based, fairness-aware), surge pricing impact. Discuss tradeoffs at scale.
What they evaluate: Geo-spatial knowledge, real-time systems, matching algorithm fluency
Q2technical

Implement an LRU cache.

How to answer: Doubly linked list + hash map. O(1) get + put. Discuss when LRU fails (LFU? FIFO?). Practice the full implementation.
What they evaluate: Standard pattern fluency, ability to discuss alternatives, clean implementation
Q3behavioral

Tell me about a time you owned a project end-to-end.

Why Uber asks: 'We are owners' value. Uber wants engineers who don't just write code — they ship outcomes.
How to answer: Pick a project where you owned more than coding (PM, design, stakeholder management). Show how you delivered, what tradeoffs you made, the outcome.
What they evaluate: End-to-end ownership, ability to operate beyond pure coding, measurable impact
Q4design

Design Uber Eats' restaurant search.

How to answer: Cover: search index (Elasticsearch / Solr), ranking (relevance + delivery time + ratings), personalization (past orders), geo-filtering. Discuss caching strategy + latency budget.
What they evaluate: Search system design, ranking signals, real-time personalization
Q5technical

Find the K closest points to origin.

How to answer: Min-heap of K points by distance. Iterate, push, pop if size > K. O(N log K). Discuss alternatives (sort = O(N log N), quickselect = O(N) average).
What they evaluate: Heap pattern recognition, algorithm choice, ability to compare alternatives
Q6behavioral

Tell me about a time you handled a major production incident.

How to answer: Pick a real incident. Show: detection, communication, mitigation, root cause, prevention. Uber values calm + structured incident response.
What they evaluate: Incident response skill, communication during crisis, systematic root cause analysis
Q7values

Why Uber over other tech companies?

How to answer: Specific Uber strengths: marketplace dynamics (riders + drivers + eaters), real-world operational scale, mission (transportation access). Show specific team / product interest.
What they evaluate: Marketplace thinking, specific Uber knowledge, multi-year intent
Q8design

How would you design a rate limiter for Uber's API?

How to answer: Token bucket (smooth) or sliding window (precise). Distributed: Redis or sharded local with periodic sync. Discuss tradeoffs (accuracy vs latency). Cover per-user + per-endpoint limits.
What they evaluate: Rate limiting algorithm knowledge, distributed systems thinking, real-world API design

Common ways candidates fail this interview

Specific to Uber, not generic interview advice.

  • ⚠️Generic system design without marketplace thinking — Uber is fundamentally a marketplace
  • ⚠️Weak geo-spatial knowledge — comes up in many design rounds
  • ⚠️Treating Uber like pre-Khosrowshahi era — culture has changed significantly
  • ⚠️Pure tech-focused 'why Uber' — they want marketplace + customer focus
  • ⚠️Skipping incident response prep — Uber is operationally intense

Uber Software Engineer compensation (2026)

Entry / Junior
$170k–$220k total comp (L4)
Mid-level
$240k–$340k total comp (L5)
Senior+
$380k–$550k total comp (L6)

Sources: levels.fyi, Glassdoor, public filings (US figures, total compensation including base + bonus + equity).

Practice these questions with a live AI interviewer

Nova is Talentee's voice AI interviewer. Speak your answer out loud, get scored on structure, clarity, and confidence, with a detailed PDF report.

Start Free PracticeAll Software Engineer questions