Uber interview practice

Uber software engineer interview process and practice. Start with verified evidence.

Practice from 80 Uber-tagged public coding problems, organized only by the stage, topic, difficulty, and recency metadata FastPrep can verify. The broader public catalog also includes 5 system-design exercises, 2 low-level-design exercises.

Catalog
87 public practice assets (80 coding)
Start here
Use the stage named in your invitation
Evidence
OA · Phone · Onsite metadata, shown in context
Uber practice workspace
Stage-led · public FastPrep catalog

OA practice path

Online Assessment

Build a timed implementation rhythm from prompt to edge cases. Problems are ranked by repeated public catalog sightings.

Solve one end to end

60 Uber-tagged Online Assessment problems available.

CompanyProblemDifficultyPublic evidenceAction
UBUber
Jump Game with Prime-3 StepsDynamic ProgrammingArrayHard
2 public reportsLast reported Aug 2026
Practice
UBUber
Last Truck to Leave the LaneMathSimulationMedium
2 public reportsLast reported Jul 2026
Practice
UBUber
Balanced Permutation SubarraysUnrated
2 public reportsLast reported Apr 2026
Practice
UBUber
Bus TimeArrayBinary SearchEasy
2 public reportsLast reported Feb 2025
Practice
UBUber
Count Palindromic Ancestor PathsTreeDepth-First SearchHard
1 public reportLast reported Aug 2026
Practice
UBUber
Chain of CommandTreeDepth-First SearchMedium
1 public reportLast reported Jul 2026
Practice
UBUber
Total Palindrome Substring CostUnrated
1 public reportLast reported Jun 2026
Practice
UBUber
Jump Game with Prime-Step RuleDynamic ProgrammingMathMedium
1 public reportLast reported May 2026
Practice
UBUber
Pipeline Throughput Maximization Under BudgetBinary SearchGreedyMedium
1 public reportLast reported May 2026
Practice
UBUber
Balanced Prefix Sets in a PermutationArrayHash TableMedium
1 public reportLast reported Apr 2026
Practice
UBUber
Minimum Edge Reversals to Root a TreeGraphDepth-First SearchHard
1 public reportLast reported Apr 2026
Practice
UBUber
Get Balanced StringArraySliding WindowMedium
1 public reportLast reported Apr 2026
Practice
UBUber
Graph Palindrome QueriesTreeDepth-First SearchHard
1 public reportLast reported Apr 2026
Practice
UBUber
Maximum Riders in CarArrayBinary SearchMedium
1 public reportLast reported Apr 2026
Practice
UBUber
Palindrome Path Queries in a TreeUnrated
1 public reportLast reported Apr 2026
Practice
UBUber
Minimum Plate Collection TimeUnrated
1 public reportLast reported Mar 2026
Practice
UBUber
Kth Greater Element IndexesUnrated
1 public reportLast reported Feb 2026
Practice
UBUber
Kth Largest Subarray Bitwise ORUnrated
1 public reportLast reported Feb 2026
Practice
UBUber
Minimum Spanning Tree Weight in a Complete Binary GraphUnrated
1 public reportLast reported Feb 2026
Practice
UBUber
Balanced Prefix PermutationUnrated
1 public reportLast reported Feb 2026
Practice

Current official guidance

How Uber describes engineering interviews.

Uber says its hiring process varies by role and location. Its engineering guidance emphasizes collaborative problem solving, clarifying questions, reasoning, tradeoffs, and practical scenarios rather than one universal sequence.

Primary sources checked .

  • A technical interview may use a shared problem or real-world scenario and asks candidates to explain how they approach it.
  • Uber's current backend guide shows a HackerRank assessment for at least one displayed level, followed by role-specific technical interviews; it is an example, not a universal loop.
  • Use the invitation and recruiter guidance for the current platform, timing, and round sequence.

01 · Stage workflow

Practice technical reasoning across reported stages.

Use the broad staged coding inventory to rehearse collaborative problem solving while treating the role-specific Uber guide as the current process authority. Your invitation and recruiter guidance remain the source of truth.

  1. 01

    Online Assessment

    Use the timing and format in your invitation as the source of truth. In practice, work without interruptions, budget time to read constraints, and reserve a final review window for boundary cases.

    • State the input, output, and complexity target before coding.
    • Implement one complete solution inside a fixed timebox.
    • Run small, duplicate, empty, and boundary cases before finishing.
  2. 02

    Phone Screen

    Treat the problem as a conversation. Clarify the contract, describe the approach before implementation, and keep narrating meaningful decisions while you code and test.

    • Ask clarifying questions instead of silently filling gaps.
    • Explain the data structure and expected complexity.
    • Walk through at least one example and one edge case aloud.
  3. 03

    Onsite

    Use the catalog's onsite labels as practice context, not as a promise about a specific loop. Focus on collaborative problem solving: compare approaches, implement cleanly, and explain how the solution behaves at scale.

    • Compare a straightforward approach with the optimized one.
    • Keep the implementation readable while discussing tradeoffs.
    • Test the result, then name follow-up improvements explicitly.

02 · Broader technical practice

Practice beyond standalone coding questions.

These public Uber-tagged exercises cover additional technical formats. They are included only when a verified catalog record and a crawlable practice page both exist.

Low-level designLast reported Aug 2026

Design and Implement Ride Dispatch and Trip Lifecycle

Model the objects and executable core for requesting a ride, assigning one available driver, and completing or cancelling the trip safely.

Open practice
System designLast reported Aug 2026

Design a Price Movement Alert Platform

Design a one-shot alert service that evaluates rolling price changes and notifies subscribers quickly and reliably.

Open practice
System designLast reported Aug 2026

Design a Nearby Autonomous Vehicle Search Service

Design a low-latency, jitter-aware geospatial service that indexes fresh autonomous-vehicle state, asynchronously persists accepted location history, and returns nearby eligible vehicles under skewed traffic.

Open practice
System designLast reported Aug 2026

Design a Driver Review Leaderboard

Design a fresh, reproducible city leaderboard derived from versioned rider reviews of completed trips.

Open practice
Low-level designLast reported Jul 2026

Design and Implement a Parking Lot

Model a parking journey and implement the allocation and release core safely.

Open practice
System designLast reported Jul 2026

Rolling Stock Price Alert System

Design one-shot percentage-jump alerts over per-second market data and rolling minute-to-year windows.

Open practice
System designLast reported Jul 2026

Design a Driver Payout System

Design a correct, auditable payout flow that turns driver earnings into one externally settled transfer without double spending.

Open practice

03 · Evidence boundary

What “Uber interview questions” means here.

It means practicing transferable implementation, testing, and technical reasoning with public catalog assets FastPrep tags to Uber. It does not mean FastPrep has access to the company's assessments or any private interview bank.

Repeated public sightings and last-reported dates can help you prioritize practice, but they cannot predict the questions, format, or platform in a specific interview.

  • Only Uber-tagged FastPrep catalog problems appear above.
  • Stage labels and report dates remain visible as context.
  • No official, private, leaked, or proprietary questions are claimed.

04 · Plain answers

Uber interview practice questions, answered plainly.

This page owns technical-practice intent for Uber. Hiring activity, timelines, and market signals remain on the separate hiring-insights page.

01Does Uber use CodeSignal or HackerRank?

FastPrep currently has 43 Uber-tagged coding problems with an explicit CodeSignal label and 5 problems with a HackerRank label. 32 other records have no proven platform label. These catalog labels do not establish the platform in a current interview; use the role-specific Uber guide and your invitation.

02Is FastPrep affiliated with Uber?

No. FastPrep is an independent interview-preparation product and is not affiliated with Uber. The page uses FastPrep's public practice catalog and does not claim official, private, leaked, or proprietary employer questions.

03How are Uber problems assigned to interview stages?

Stage labels come from FastPrep's public problem metadata. A problem can carry more than one reported stage, and hiring processes can change by role, level, location, and date. Treat the labels as preparation context, not a guarantee.

04Which Uber interview stage should I practice first?

Start with the stage named in your invitation or recruiter message. If no stage is known, use the largest available set to build general problem-solving fluency, then rehearse explanation and testing separately.

05Does this page predict the Uber interview process?

No. Public catalog counts, stage tags, and last-reported dates can help prioritize practice, but they cannot predict a specific interview's questions, sequence, timing, or platform.

Your next stage, made concrete

Pick a problem. Solve it end to end.

Start with the stage named in your invitation, then use public evidence as context—not as a promise of what you will be asked.

Open the practice set