Uber software engineering interview questions

The Process

Five rounds, and three of them happen in a single morning

01

30 minZoom call

Recruiter screen

Short, and it sets your band. The recruiter decides whether you are run at L4 or L5a before any engineer sees you, and the onsite is built for that band.

Ask which band the loop is built for.
L5a and above adds a system design round. If the recruiter has you down as L4 you will never be asked one, and you cannot be moved up afterwards.
Ask for the grant in shares, not dollars.
A dollar figure hides the share count and the pricing date. Uber is listed, so shares plus a date is a number you can check yourself.
Give one total compensation number.
Uber pays base, stock and an annual bonus target. Anchoring on base alone leaves two of the three out of the conversation.

02

70 to 90 minCodeSignal

CodeSignal assessment

Four problems in seventy to ninety minutes, auto scored against hidden tests with nobody watching. The first two are warm ups, the last two medium to hard graph and DP. There is no partial credit and speed counts.

Only passing tests count.
There is no partial credit and no interviewer to explain to. A brute force that passes every hidden test outscores an elegant solution that times out.
Practise in the editor, not on paper.
Candidates lose ten minutes to syntax errors they would never make in their own setup. Some teams swap this stage for a live CoderPad screen, so practise both.
Bank the warm ups before you gamble.
The first two problems are the free marks. Submit them clean, then spend everything that is left on the graph and dynamic programming pair.

03

4 to 6 rounds45 to 60 minSQL round included

The onsite loop

Four to six rounds of forty five to sixty minutes: a DSA round on trees, graphs and heaps, a dedicated SQL and database round that several teams run, system design from L5a upward, and a STAR behavioural.

Medium is the baseline, not the ceiling.
Arrays, hash maps, graphs and intervals dominate. The second problem is usually a step harder than the first, so pace the first one.
The SQL round catches people out.
Several teams run a dedicated database round: query writing, schema design, indexing and optimisation. Almost nobody prepares for it, and it is scored like any other.
Name the complexity before you type.
The trade off conversation is scored separately from the code. Stating the bound up front earns that mark even if the implementation runs long.

04

45 to 60 minOutside your teamReverse design

Cross team deep dive

A specialty interviewer from outside the hiring team takes a system you built and spends the hour asking why you made each choice. It carries outsized weight in the debrief, but there is no veto and no unanimity rule.

Bring one project you can defend for an hour.
The deep dive goes past the summary into what broke and what you measured. One project you know to the bottom beats three you can summarise.
Expect why, not what.
This is reverse system design. They already have the diagram, so what they want is your reasoning, the alternatives you rejected and the cost of each.
Pick a consistency story and defend it.
Dispatch tolerates a stale read, payments do not. Saying which parts of your design may be wrong for a second is what separates L5a from L5b here.

05

1 to 2 weeksLonger for pipeline

Team match and offer

One to two weeks to land a team and turn the packet into an offer. Pipeline hires wait longer, and matching on its own can add another two to four weeks.

Ask where the packet has got to.
The technical decision is already made, so a delay here is usually a headcount question rather than a doubt about you. Ask which teams have open slots.
Know which org you are joining.
Rides, Eats, Freight and the platform teams run different roadmaps and different on call. Ask before the day, because the manager will ask you.
The debrief happens without you.
Every interviewer writes up before the group meets, so the last conversation about you is one you never attend. Leave nothing implied.

Levels and Pay

The stock is public, so you can price the offer yourself

Pick a level to see how the package splits, what changes by city, and what the loop actually asks of you at that band.

San Francisco

New York

Seattle

Amsterdam

Level	Experience	Total comp
Software Engineer IL3Entry	0 to 2 yrs	~$195K
Software Engineer IIL4Mid	2 to 5 yrs	~$277K
Senior EngineerL5aSenior	5 to 9 yrs	~$449K
Staff EngineerL5bStaff	9 to 13 yrs	~$645K
Senior StaffL6Sr Staff	13+ yrs	~$865K

Live Question Feed

What Uber is asking right now

90 questions · new ones added every 7 days

90 Verified

CODING

Search a rotated sorted array for a target index, then handle duplicates without dropping back to linear time.

CodeSignal assessment

70 to 90 min

CodeSignal

Reported 9 times

Open

SYSTEM DESIGN

Design driver dispatch: geospatial indexing, real time matching, ETA estimates and surge under a demand spike.

Locked

LEADERSHIP

Tell me about a decision you made on incomplete data that you would still make the same way today.

Locked

CODING

Merge k sorted trip event streams and return the first n events under a fixed memory budget.

Locked

SYSTEM DESIGN

Design a ranking service for Eats storefronts taking ten thousand updates a second across regions.

Locked

DEEP DIVE

Take one system you owned end to end and defend the architectural trade off you now regret.

Locked

CODING

Return every combination of positive integers that sums to a target, then memoise the recursion.

Locked

CODING

Implement an LRU cache with O(1) get and put, then make it safe under concurrent reads.

Locked

LEADERSHIP

Tell me about disagreeing with a senior engineer on architecture and what happened next.

Locked

89 more questions available

The exact questions Uber is asking this week, tagged by round and difficulty.

Unlock All 90 Questions

Each question stays in the bank for 14 days, so everything here was asked in the last 14 days. Candidates who see them first pass at 3.2 times the normal rate.

Get Full Access

The Unfair Advantage

Why this actually works

01

Real questions, not guesses

Collected from engineers who sat the loop, then cross validated against other intel sources.

02

Fresh every week

The database updates every 7 days, so you never study stale problems.

03

Covers every round

Compiling coding rounds, dispatch and marketplace design, the manager round and the cross team deep dive.

04

120+ companies tracked

Also interviewing at Lyft, DoorDash or Instacart? We have their questions too.

05

Difficulty and pattern data

Tagged by difficulty, round and category, so you know where prep time goes.

06

Candidate verified only

Reported by a candidate, then cross verified against multiple data points.

3.2×

Higher pass rate

120+

Companies tracked

3.2K+

Engineers using this

FAQ

Common questions

How are the questions sourced?

Directly from engineers who interviewed at Uber, then cross validated against other intel sources into a stack ranked list.

How often are questions updated?

We add new questions every 7 days and retire each one after 14 days, so the bank turns over twice in the window it covers. Uber holds its banks per org, so Rides, Eats, Freight and platform rotate separately.

Does Uber ask LeetCode questions?

Yes, and a machine grades them first. The CodeSignal test runs four problems against hidden tests with no partial credit. The onsite adds a live DSA round and, on several teams, a SQL and schema round.

Can I use AI tools in the interview?

No. The CodeSignal assessment is auto scored against hidden tests, and every live round runs in a shared editor with the interviewer watching you type.

What is the cross team deep dive?

A specialty interviewer from outside the hiring team spends an hour asking why you made each choice in a system you built. It carries outsized weight in the debrief, though it has no veto.

What does Uber pay a Software Engineer II?

Around $277K at L4 in San Francisco, about $269K in Seattle. Just over a quarter is stock, and because Uber is listed you can price it the day you sign.

How long does the process take?

Three to six weeks is normal, and team match can add one to two more. The onsite is a single day, so most of the wait sits between the CodeSignal test and getting that day booked.

Is this just for Uber?

No. GothamLoop covers 120+ companies including Google, Amazon, Stripe, Airbnb and OpenAI.

The Uber interview cheat code nobody talks about

Five rounds, and three of them happen in a single morning

Recruiter screen

CodeSignal assessment

The onsite loop

Cross team deep dive

Team match and offer

The stock is public, so you can price the offer yourself

What Uber is asking right now

Why this actually works

Real questions, not guesses

Fresh every week

Covers every round

120+ companies tracked

Difficulty and pattern data

Candidate verified only

Common questions

Pricing plan

Company Interview Guides