Uber Software Engineer Interview Guide

The short answer: Uber's backend engineering interview guide lists a 30-minute recruiter call, an online coding assessment and a 60-minute technical phone screen on coding and design, then three 60-minute interviews: algorithms and data structures, depth in your specialization, and collaboration and leadership. A trained Bar Raiser moderates the debrief. Uber says steps can differ by role and level, and one Uber engineer describes a longer loop with two design rounds. Last reviewed October 2026.

Uber software engineer interview: quick answers

The Uber software engineer role

What Uber engineers work on, the skills its job postings ask for, and what a normal week looks like.

Uber software engineer levels and pay

Your level sets the bar you are interviewed against and the pay band of the offer.

Level names and experience come from Uber's postings where they state them, and otherwise from compensation data and candidate reports.

Pay in Uber's US job postings

Uber's US postings list a base salary range plus eligibility for Uber's bonus program and possibly an equity award. The ranges were the same in San Francisco, Sunnyvale, New York and Seattle. Postings do not name the level, so the table maps titles to the levels in Uber's interview guide.

No Software Engineer I (L3) or new grad US posting was open on October 27, 2026. Ranges seen October 27, 2026.

Uber software engineer interview process

Uber publishes interview guides for its engineering roles. The steps below come from the backend engineering guide, which says details vary by domain and that different levels may have distinct processes.

Based on Uber's hiring pages and candidate reports.

Uber says recruiters usually follow up within two to three business days after each interview. Candidate guides put the full process at about three to six weeks. Last reviewed October 2026.

What is different at Uber

• Bar Raisers run the debrief. Uber trains engineers as Bar Raisers to moderate the hiring debrief, remove bias and reach a consensus decision based on what you showed in the interviews. Candidate reports also describe a bar raiser interview with a deep dive on a past project.
• A coding round for your specialty. Coding 2 tests depth in your area rather than repeating Coding 1.
• Values and success attributes. Uber's guide lists seven success attributes (adaptability, bias towards action, collaboration, entrepreneurial, grit, interpersonal influence and inquisitiveness) and asks you to prepare examples of its values, such as Trip Obsessed and One Uber.
• The phone screen sets your starting level. Uber says the final level is decided after the debrief and can still change.
• No AI unless your recruiter says so. Uber's guide rules out tools like ChatGPT and code autocompletion, but some technical interviews include an AI agent in the coding environment.
• Design at Uber's scale. Candidate guides say design prompts sometimes draw on Uber's own early problems, such as showing every Uber driver in the world on a map.

Uber software engineer interview questions

Coding problems from our bank, then design and behavioral practice prompts we wrote for this guide.

1from typing import List, Tuple
2
3def closest_drivers(drivers: List[Tuple[int, float, float, bool]], rx: float, ry: float, k: int) -> List[int]:
4    """Return up to k available driver ids, nearest first, ties by id."""
5    pass

1import heapq
2from typing import List, Tuple
3
4def closest_drivers(drivers: List[Tuple[int, float, float, bool]], rx: float, ry: float, k: int) -> List[int]:
5    if k <= 0:
6        return []
7    heap = []  # max-heap of the best k, stored as (−dist², −id)
8    for driver_id, x, y, available in drivers:
9        if not available:
10            continue
11        # Squared distance keeps the same order and avoids a square root.
12        item = (-((x - rx) ** 2 + (y - ry) ** 2), -driver_id)
13        if len(heap) < k:
14            heapq.heappush(heap, item)
15        elif item > heap[0]:
16            heapq.heapreplace(heap, item)
17    return [-neg_id for _, neg_id in sorted(heap, reverse=True)]
18
19# O(n log k) time and O(k) space, so it never sorts the full driver list.

How to prepare

A plan for the Uber loop, most important first:

1. Practice medium problems in code that compiles and runs.
2. Ask which specialization your Coding 2 round covers, then practice building realistic components in it.
3. Practice design and architecture for the phone screen, with real-time, location-heavy systems.
4. Prepare one or two past projects for each of Uber's three competencies, in STAR form.

Practice path

Courses that cover the rounds above:

• Data Structures and Algorithms
• System Design