Uber hub
Uber Online Assessment
Overview
Uber online assessment (OA) is the first hard filter for most fresher, campus, and off-campus SDE-style drives. This page covers the Uber OA format, what happens after you clear it, sample Uber OA questions with approaches, an 8-week prep plan, and mistakes that sink otherwise-strong candidates.
Patterns below are from student reports for 2025-2026. Platforms and section names can change by drive. Always confirm the college placement email for your window.
Uber hiring flow after the OA
| Stage | What candidates report | What you must show |
|---|---|---|
| 1. Online assessment | Timed coding OA (often 2 problems, medium-hard) on HackerRank / CodeSignal-style platforms | Correctness + reasonable complexity under time |
| 2. Technical interviews | DSA-heavy interviews; some design discussion for higher levels | Explain approach, edge cases, complexity |
| 3. Later rounds | Behavioral / collaboration; HR logistics | Depth beyond the OA pattern |
| 4. HR / offer | Role, location, CTC discussion | Consistency with resume |
Uber Online Assessment format
Test structure
| Component | From student reports details |
|---|---|
| Platform | HackerRank, CodeSignal, or similar |
| Duration | Often 60-90+ minutes |
| Question mix | 2 coding problems typical; follow invite |
| Languages | C++, Java, Python |
| Scoring | Full test-case pass expected; complexity matters |
| Advance rate | Selective product-company bar |
What makes Uber OA feel distinct
- Problems may resemble routing, matching, and real-time updates but reduce to standard DSA
- Code quality and edge cases are scrutinized in interviews after OA
- Difficulty comparable to other top product OAs
- Less MCQ aptitude than service hiring tests
Question types you should expect
Core DSA
- Graphs / BFS / shortest paths
- Heaps and interval problems
- Hash maps for sessions and IDs
- Union-Find in connectivity variants
- DP on paths/sequences
Secondary / role-dependent
- Debugging / incomplete function implementation in some platforms
- Light behavioral form questions outside coding time
What usually does not appear in the OA
- Full marketplace system design (later)
- Driver operations case interviews for pure SWE coding OA
- Long verbal essays
Sample Uber Online Assessment questions
Question 1: shortest path for a rider
Q: Grid with road/blocker cells; minimum steps from start to end.
BFS on unweighted grid. Dijkstra if weights differ.
Question 2: meeting point / minimize travel
Q: Given points on a line or grid, pick a meeting point minimizing total distance.
Median for L1 on a line. Know the geometric median discussion for interviews even if OA is simpler.
Question 3: active trip intervals
Q: Max overlapping trips given start/end times.
Sweep line. O(n log n).
Question 4: rate limit API calls
Q: Allow at most N calls per sliding window of T seconds.
Queue of timestamps; reject when size reaches N before eviction.
Question 5: union of rider zones
Q: Merge overlapping service zones represented as intervals.
Sort and merge. Same family as merge intervals.
Question 6: top-k busiest cells
Q: From a stream of pickup cells, return k busiest.
Hash counts + heap of size k.
How to prepare for Uber OA (8-week plan)
| Weeks | Focus | Exit criteria |
|---|---|---|
| 1-2 | Arrays, hashing, two pointers, sliding window | 40+ easy/medium solved cleanly |
| 3-4 | Trees, graphs (BFS/DFS), heaps | Can code BFS/DFS without notes |
| 5-6 | DP + greedy patterns (graph + heap emphasis) | 25+ medium DP/greedy with recursion to bottom-up |
| 7 | Timed full mocks matching Often 60-90+ minutes | Finish both problems green with explained complexity with passing tests |
| 8 | Weak-topic repair + complexity review | Re-solve every miss within 48 hours |
Daily loop
- One timed medium problem (45-60 min hard cap)
- Write complexity and 3 edge cases before coding
- If stuck past 20 minutes, peek pattern name only, then re-solve tomorrow cold
- Log misses by topic on a simple sheet
Company pages on this site
- Uber coding questions
- Uber aptitude / mock quiz
- Uber interview experience
- Uber preparation guide
- Practice PDF: Uber Placement Papers PDF (2026)
Common mistakes on Uber OA
- Not clarifying distance metrics (city block vs Euclidean)
- Mutable shared state bugs in simulation problems
- Skipping brute force when n is small enough to pass
- Poor naming / unreadable code that you cannot defend later
- No behavioral stories for collaboration rounds after OA
Day-of checklist
- Stable internet, charged laptop, quiet room
- Confirm language template compiles on the platform before starting hard problems
- Skim all problems for 3-4 minutes, order by familiarity
- Submit a correct brute force early if constraints allow, then optimize
- Leave 8-10 minutes for edge-case tests you invent yourself