The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment (CodeSignal) | ~70-90 min | Timed algorithmic filter |
| Technical Phone Screen | ~60 min | Live coding with an Uber SWE |
| Onsite Coding Rounds | ~60 min each | Core + specialization coding |
| System Design | ~60 min | Real-time, high-throughput architecture |
| Collaboration/Leadership + Bar Raiser | ~60-75 min | Behavioral depth and bar-raising judgment |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment (CodeSignal)
~70-90 minA timed CodeSignal assessment with roughly four problems ranging from easy/medium arrays and strings to harder graph or DP questions. Speed and correctness both count.
- Array/string transformation under time pressure
- Graph traversal or shortest path
- Dynamic programming medium
- Simulation or matrix problem
- Hash-map frequency logic
- Do timed CodeSignal-style sets to build speed
- Master graph and DP mediums (NeetCode, free)
- Practice finishing easy problems fast to bank time
- Handle edge cases before moving on
- Spending too long on one hard problem
- Leaving easy points on the table
- Unhandled edge cases failing hidden tests
- High score with efficient time use
- Correct handling across difficulty tiers
- Clean, working submissions
Technical Phone Screen
~60 minA live coding question, typically on CodeSignal/CoderPad, at medium to medium-plus difficulty. You're expected to produce runnable, tested code and explain your reasoning.
- Graph BFS/DFS on a grid or network
- Heap-based top-K or scheduling
- Sliding-window on a stream
- Tree problem with follow-up
- Interval/merge logic
- Practice writing runnable code (Uber dislikes pseudocode)
- Drill graphs, heaps, sliding window specifically
- Rehearse testing your solution with cases
- Do mock live-coding sessions
- Leaving code that won't compile/run
- Not testing before declaring done
- Poor communication of approach
- Runnable, tested code within time
- Clear reasoning and complexity
- Good pattern recognition
Onsite Coding Rounds
~60 min eachTwo coding rounds, one general and one leaning toward your specialization. Medium-plus problems expected as runnable, edge-case-tested code, often within tight time (~35 min of actual coding).
- Graph problem framed as trip/network routing
- Heap or priority-queue scheduling
- Sliding window / two pointers on streaming data
- Tree/DAG dependency problem
- Design a small in-memory component
- Focus prep on graphs, trees, heaps, sliding window
- Practice speed: get to working code in ~30 min
- Prepare to test and handle edge cases quickly
- Study specialization-relevant patterns
- Too slow to a working solution
- Skipping edge-case testing under time pressure
- Not adapting to specialization framing
- Fast, correct, runnable solutions
- Strong graph/heap fluency
- Depth in your specialization
System Design
~60 minRequired for mid-level and above (sometimes two rounds for senior). Focuses on Uber-scale real-time systems: dispatch, location tracking, payments. You scope, architect, and reason about consistency and scale.
- Design a rider-driver matching/dispatch system
- Real-time location tracking at scale
- Payment processing with consistency guarantees
- Surge pricing / event pipeline
- Geospatial indexing and querying
- Study geospatial indexing (quadtree, geohash)
- Learn message queues, streaming, and consistency models
- Practice dispatch/tracking designs (Hello Interview, free videos)
- Estimate QPS/storage back-of-envelope
- Ignoring real-time latency requirements
- No geospatial or partitioning strategy
- Skipping capacity estimation
- Real-time and geospatial awareness
- Sound consistency/scale trade-offs
- Structured, estimate-driven design
Collaboration/Leadership + Bar Raiser
~60-75 minA collaboration/leadership round on how you work with others plus a bar raiser (often cross-org) who calibrates whether you clear Uber's hiring bar across technical and behavioral dimensions.
- Driving a project through cross-team friction
- Mentoring or influencing without authority
- A high-stakes decision under ambiguity
- Handling failure and recovery
- Why Uber
- Prepare 5-6 STAR stories on leadership and conflict
- Have a strong project deep-dive ready
- Practice concise, metric-backed answers
- Research Uber's business and prepare questions
- Vague, outcome-free stories
- No cross-team or influence examples
- Underestimating the bar raiser round
- Clear leadership and collaboration
- High signal, specific stories
- Consistency across the loop
What to master
- Graphs (BFS/DFS, shortest path)
- Trees and DAGs
- Heaps and priority queues
- Sliding window and two pointers
- Dynamic programming
- Real-time/geospatial system design
- Consistency, queues, and streaming
- Leadership STAR stories
Eligibility
New grad through senior/staff. New grads face two coding rounds plus lighter design; mid/senior add full system design (sometimes two) and cross-org bar-raiser scrutiny.
Uber SWE salary & compensation (2026)
Strong post-IPO comp; RSU-heavy with annual refreshers; India tech hubs large.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| L3 (SWE I) | 0–2 yrs | ₹28–45 LPA | $160K–210K | base + RSUs + ~10% bonus |
| L4 (SWE II) | 2–5 yrs | ₹45–80 LPA | $220K–310K | stock weighting grows |
| L5 (Senior SWE) | 5–9 yrs | ₹80–140 LPA | $330K–470K | RSUs typically > base |
| L6 (Staff SWE) | 9–13 yrs | ₹140–240 LPA | $500K–720K | equity-heavy; large refreshers |
| L7 (Senior Staff) | 13+ yrs | ₹240–380 LPA | $720K–1M+ | top band |
How the package is structured
- US split ~ base 45–55%, RSUs 35–50%, bonus 10–15%
- Annual RSU refreshers; vest 4-yr; bonus tied to company performance
- India comp ~ 45–55% of US; Bengaluru/Hyderabad engineering hubs
- L5 Senior is common terminal; L6 Staff is a large step
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1-3: Graphs, trees, heaps drills, timed
- Days 4-5: Sliding window + DP mediums
- Days 6-8: Speed practice to runnable code in 30 min
- Days 9-11: Real-time/geospatial system design + mocks
- Days 12-13: Leadership STAR stories + project deep-dive
- Day 14: Full mock loop including bar-raiser style
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
Does Uber accept pseudocode?
No. They expect runnable, edge-case-tested code, so practice writing complete, testable solutions quickly.
What coding topics are most tested?
Graphs, trees, heaps, and sliding window recur heavily. Build fluency and speed in these.
What does the bar raiser do?
A calibrated interviewer (often from another org) assesses whether you clear Uber's overall bar; treat it as seriously as any technical round.
What kind of system design comes up?
Real-time, high-throughput systems like dispatch, location tracking, and payments. Know geospatial indexing and consistency trade-offs.
How fast do I need to code?
Aim to reach working, tested code in around 30-35 minutes so there's room for follow-ups.
How long is the process?
Usually about 2-6 weeks across 4-5 rounds.