CalibrdReady. Confident. Hired.← All guides

Uber interview, level by level, from the phone screen that sets it.

Updated · Sources at the end

Uber publishes its own interview guide for each engineering track, Android, backend, iOS and others, with the rounds for each level from L3 to L6 and above. Every level starts with a 60-minute Business Phone Screen of about 45 minutes of coding and 15 of design, and Uber says it sets the level you go forward at. The onsite then has a general coding round, a Depth in Specialization round in your own track, a design round from L4, and a collaboration and leadership round; senior levels add a design round about a system you built before and, from L5B, a round on how you make others more effective.

Candidates call the system design round the Bar Raiser, though Uber's guides never use the word. The prompts repeat: a stock price alert service and a top trending items service each came up for seven candidates between 2025 and 2026. Hiring slowed in 2026: Uber paused many roles from June and cut about 10% of staff in September.

Free · 2 minutes · no account

The questions for your exact Uber role and level.

See the questions Uber asks ↓Run a free mock interview →

Interviewing at Uber? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Uber hires

Uber hires software engineers from new graduates (L3) to senior staff (L6 and above) across rides, delivery, freight, maps, payments and infrastructure, with Android and iOS engineers on its own interview tracks. Reported loops in 2025 and 2026 ran in Bangalore, Hyderabad, Amsterdam, Aarhus, Toronto, Sunnyvale and San Francisco. On 2 September 2026 Uber said it was reducing its team by about 10%, with tech teams in its hubs, about 1% of staff remote and three office days a week. Candidates reported a hiring pause from June 2026 that some loops still met in October.

Uber's guide lists different rounds for each level. These are the steps after the recruiter call and the Business Phone Screen.

  • Track · L3

    L3, new graduates

    A HackerRank coding test first, then the Business Phone Screen, then Coding 1 (algorithms), Coding 2 (Depth in Specialization) and Collaboration & Leadership. No design round in the onsite.

  • Track · L4

    L4, software engineer II

    Adds Design & Architecture on a new problem. Uber's guide expects you to engage actively and balance the interviewer's guidance with your own problem-solving. Backend L4 also lists the HackerRank test.

  • Track · L5A

    L5A, senior

    Adds a 75-minute round that combines Design & Architecture on a problem you solved before with collaboration and leadership. Uber expects a senior engineer to take the lead and drive the design with little guidance.

  • Track · L5B and L6+

    L5B and L6+, staff and above

    Adds Impact – Efficiency & Quality: how you scale yourself and the organisation by making others better. L6+ starts with two screens, one with the hiring manager on scope and impact, one on technical architecture, then both design rounds.

  • Track · Mobile

    Android and iOS

    For Android, Depth in Specialization is in Kotlin in Android Studio, and Uber says it may be a change to a project it provides; Uber's iOS guide uses the same round names. The design round can be an app or a library: MVVM, MVC or MVI, caching, pagination, debouncing and image loading, and at L6+ push against pull, dependency injection and image loading in depth.

02

What is the Uber interview process?

Uber's own engineering interview guides list these stages, and Uber says they can vary by role, location and business need. What happens inside each round comes from candidate reports and is marked so.

01
Recruiter call
About 30 minutes

Background, level and the guide for your track. Recruiters send Uber's interview guide; read the tab for your level.

02
Online coding test
HackerRank, camera on

Uber's guide names HackerRank. Candidates since November 2025 report 2 problems in 90 minutes, or 3 in 65 minutes for entry-level roles in India. Reports before then named CodeSignal.

L3, and backend L4
03
Business Phone Screen
60 minutes: about 45 coding, 15 design

Pair programming on HackerRank. Uber says it decides whether you continue and at what level. Candidates call it an elimination round, and some found no time left for the design part.

04
Coding 1: algorithms
60 minutes

Generic problems, testable code. Candidates report union-find problems in at least eight loops, and Longest Continuous Subarray With Absolute Diff Limit, Closest Palindrome and First Unique Number several times each.

05
Coding 2: Depth in Specialization
60 minutes

Day-to-day code in your own track, from scratch or by changing a project Uber provides. Candidates call it low-level design or machine coding, and say the code has to run: a parking lot, an in-memory file system, a pub-sub queue, a key-value store.

06
Design & Architecture
60 minutes on a new problem; 75 minutes with a past one at L5A

A whiteboard round in Miro or HackerRank. At L5A and above, a second round on an architecture you designed before, prepared in advance. Candidates call the new-problem round the Bar Raiser.

L4 and above
07
Collaboration & Leadership
60 minutes

Behavioural, scored against Uber's values, such as Trip Obsessed and One Uber. Candidates report rejections decided by this round alone.

08
Decision
Debrief

Uber says your recruiter meets the panel to review your performance against the role's competencies and its values, and that interviewers follow up within two to three business days. Candidates report being offered a level below the one they applied for, more often than an outright no.

03

Uber system design interview: the rounds and the prompts that repeat

Uber's own guides and 2025 to 2026 candidate reports

Uber's system design interview is its Design & Architecture round: 60 minutes in Miro or HackerRank designing a large system from L4 up, and from L5A a second round on an architecture you designed before, prepared in advance. Candidates call the first one the Bar Raiser, a name Uber's guides do not use. Uber's guides say the level shows in how you drive it: at L4 you balance the interviewer's guidance with your own ideas, and from L5A you lead with little guidance. The prompts repeat more than at most companies.

  • Price alerts on stocks: Seven candidates in 2025 and 2026 had a variant: notify users when a stock moves past a threshold. Index alerts by symbol and threshold, partition the price stream, and plan for a whole market moving at once.
  • Top trending items: Seven more had a top-K service: trending items in a shop, popular orders, recommendations on a home page. Cover counting over a time window, approximate counting at scale, and how fresh the list must be.
  • Chats, feeds and brokers: Fewer reports each: a chat system, a feed with notifications, a message broker like Kafka. One self-described Uber interviewer said they look for breadth, clarity and naming the problems in your own design, then go deep, such as how you would partition Kafka.
  • The previously solved problem, from L5A: Bring a system you designed, ready in Miro or HackerRank before the call, and expect questions on why you made each choice and what you would change. Uber puts it in the same 75-minute round as collaboration and leadership at L5A.
  • Mobile: an app or a library: Android and iOS candidates design an app or a library. Uber's guide lists architecture patterns, caching, pagination, debouncing and image loading, and at L6+ dependency injection and push against pull.
  • What decides it: Candidates report rejections turned by this round alone, and others where a soft no here was weighed against strong coding rounds. Several were offered a level down instead of a no.

Candidates report no generic design-Uber-the-app prompt in 2025 or 2026. Uber's own example systems are a photo posting app and a messaging platform.

04

What Uber screens for

Uber's guides say every stage is a decision point, and name what they look for at each level:

  • Testable, running code in the coding rounds, and in Depth in Specialization how you would take it to production
  • In design, driving the conversation yourself from L5A, with the trade-offs said out loud
  • Uber's values in the behavioural rounds: Trip Obsessed, One Uber, Great Minds Don't Think Alike, Do the Right Thing
  • At senior levels, scope and impact: delivering projects from start to production and making the people around you better
  • No AI tools in interviews unless your recruiter says so, though some technical rounds provide an AI agent in the coding environment
05

Uber interview questions

Candidate-reported themes

Uber's design prompts repeat more than most: a stock price alert service and a top trending items service each came up for seven candidates in 2025 and 2026. The questions here follow those reports and the values Uber's guides name.

Behavioural & motivation

  • Why Uber?Listening for: Specificity · Connection · Research
  • Tell me about a project where you changed how your team works for the better.Listening for: What needed changing · What they changed · Result in numbers
  • Describe how you work across teams to deliver something neither team could alone.Listening for: The teams and the goal · How they aligned · What it delivered
  • Tell me about a time you disagreed with a decision and how it played out.Listening for: The disagreement · How they raised it · What happened
  • Tell me about someone you helped become more effective.Listening for: Who and why · What they did · Measurable impact

Technical

  • Practice: drivers and riders join shared trips over the day, given as timestamped pairs. When does everyone first become connected? Explain your approach and its complexity.Union-find, Uber's favourite disguise: Reported in at least eight loops, 2025 to 2026, often dressed in Uber's domain: islands added one at a time, riders who become connected over time. A practice questionListening for: Spots union-find · Efficient · Edge cases
  • Practice: build an in-memory file system with mkdir, cd and pwd, where cd accepts * as a wildcard for one directory name. Make it run, and test it.Depth in Specialization: running code: Candidates say Uber wants code that runs in this round: a parking lot for cars and bikes (six reports), an in-memory file system with a wildcard in paths (four), a multithreaded pub-sub queue (three). A practice questionListening for: A clean structure · The wildcard · It runs, with tests
  • Practice: design a service that lets millions of users set price alerts on stocks and notifies them within seconds when one triggers.System design: price alerts: The most repeated design prompt, seven candidates from 2025 to 2026: notify users when a stock moves past a threshold, such as 5% from the close. A practice questionListening for: Requirements first · Matching at scale · Delivery and duplicates
  • Practice: design an Android SDK with a search bar that shows matching places as the user types.Mobile design: an app or a library: Uber's Android guide asks for the architecture of a large app, such as photo posting or messaging, or a library, with caching, pagination, debouncing and image loading. One 2025 candidate was asked for a places search SDK. A practice questionListening for: A clean public API · Typing done right · Mobile constraints

These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my Uber questions →
06

Pay

L3, software engineer I$207K total a year (base $153K)
L4, software engineer II$274K total a year (base $178K)
L5a, senior$440K total a year (base $223K)
L5b, staff$615K total a year (base $246K)
L6, senior staff$802K total a year (base $284K)
Amsterdam, L3 to L5b$108K to $321K total a year

Levels.fyi figures for Uber software engineers in the United States, from 2,981 submissions, and in the Netherlands, read on 13 October 2026. Levels.fyi reports Uber's stock as front-loaded and vesting monthly, most often 35% in the first year, 28%, 22% and 15%, though Uber publishes no schedule. Ask the recruiter for the split by year; our big tech RSU guide covers what to ask.

07

How to prepare for an Uber interview

  1. Read Uber's interview guide for your track and the tab for your level. Recruiters send it.
  2. Treat the Business Phone Screen as the round that sets your level: practise one medium problem in 45 minutes with time left to talk design.
  3. Practise union-find until it is automatic, and the sliding-window and palindrome problems candidates name.
  4. Build one Depth in Specialization problem end to end in your interview language, such as a parking lot or an in-memory file system, and make it run with tests.
  5. Prepare a price alert system and a top trending items system, with numbers and failure handling.
  6. From L5A, prepare one system you designed, drawn in Miro before the call, with the reasons for each choice.
  7. Prepare stories for Uber's values: Trip Obsessed, One Uber, Great Minds Don't Think Alike, Do the Right Thing.
  8. Ask the recruiter whether the role is open after the 2026 pause, and the stock split by year before you talk numbers.

This guide covers Uber's software engineering hiring, including Android and iOS. Uber's guides cover data, frontend, machine learning, security and engineering management too, with their own rounds. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at DoorDash, Netflix or Google Zurich? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run an Uber mock: spoken answers, coached on the spot. Your first mock is free.

Run an Uber mock →
08

FAQ & sources

What is Uber's interview process?

Uber's own engineering interview guides list these stages, and Uber says they can vary by role, location and business need. The stages, in order: Recruiter call; Online coding test; Business Phone Screen; Coding 1: algorithms; Coding 2: Depth in Specialization; Design & Architecture; Collaboration & Leadership; Decision.

What does Uber look for in candidates?

Uber's guides say every stage is a decision point, and name what they look for at each level: Testable, running code in the coding rounds, and in Depth in Specialization how you would take it to production; In design, driving the conversation yourself from L5A, with the trade-offs said out loud; Uber's values in the behavioural rounds; At senior levels, scope and impact.

What questions does Uber ask in interviews?

Uber's design prompts repeat more than most: a stock price alert service and a top trending items service each came up for seven candidates in 2025 and 2026. Technical themes: Union-find, Uber's favourite disguise; Depth in Specialization: running code; System design: price alerts; Mobile design: an app or a library.

What is the Uber system design interview?

Uber's system design interview is its Design & Architecture round: 60 minutes in Miro or HackerRank designing a large system from L4 up, and from L5A a second round on an architecture you designed before, prepared in advance. Candidates call the first one the Bar Raiser, a name Uber's guides do not use. Covered on this page: Price alerts on stocks; Top trending items; Chats, feeds and brokers; The previously solved problem, from L5A; Mobile: an app or a library; What decides it.

How do I prepare for an Uber interview?

Read Uber's interview guide for your track and the tab for your level. Recruiters send it. Treat the Business Phone Screen as the round that sets your level: practise one medium problem in 45 minutes with time left to talk design.

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.

Prep for a real Uber role

Practise your Uber interview, out loud.

Paste a real Uber posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Set up your workspace for free →Add to Chrome, it reads the posting for you →

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Uber prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Uber Interview: Business Phone Screen, Design, Pay — Calibrd