# Uber Interview Process 2026: Rounds and Timeline

> The Uber interview process for software engineers: 5 stages over about 4 to 6 weeks, plus interview questions, online assessment and new grad notes, all cited.

Canonical: https://devsunite.com/interview-process/uber-interview-process
Last updated: 2026-11-20

The Uber interview process for software engineers takes about 4 to 6 weeks: Uber's backend engineering guide lists a 30 minute recruiter call, a HackerRank coding assessment, a 60 minute technical phone screen and three 60 minute interviews covering coding, depth in specialization, and collaboration and leadership. [2][5][6] This summary is compiled from 7 public sources, 5 of them published by Uber. Uber's official hiring page lists an application, a talent team conversation, a hiring manager chat, a technical interview for tech roles, a role-dependent exercise or assessment, a team interview and then a decision. Its backend engineering interview guide lists a 30 minute recruiter or sourcer call, a HackerRank coding assessment, a 60 minute technical phone screen on coding plus design and architecture, and then three 60 minute interviews covering coding, depth in specialization, and collaboration and leadership. interviewing.io describes a five round onsite that also includes system design and a bar raiser. [1][2][5]

_This guide is compiled from public information, not first-hand experience. Every claim links to its source. Sources last checked 2026-11-20._

## Uber interview rounds and timeline at a glance

- **Rounds**: Uber's backend engineering guide lists a 30 minute recruiter call, a HackerRank coding assessment, a 60 minute technical phone screen and three 60 minute interviews covering coding, depth in specialization, and collaboration and leadership. interviewing.io reports a five round onsite that adds system design and a bar raiser. [2][5]
- **Stages in order (5)**: Application and recruiter call, Coding assessment, Technical phone screen, Interview loop, Decision. [1][2][5][3][6]
- **How long it takes**: Uber does not publish an overall duration in the pages reviewed; interviewing.io reports about 4 to 6 weeks and Aced three to six weeks. [5][6]
- **Online assessment**: Reported: sometimes. [2][3][5][6]

## Uber software engineer interview stages

1. **Application and recruiter call**: Candidates apply and then talk with the talent team about their experience and the role. The backend guide lists this as a 30 minute virtual call with a recruiter or sourcer; interviewing.io says it covers role, team, location and level. [1][2][5]
2. **Coding assessment**: The backend guide lists completing a HackerRank coding assessment, and the internship guide lists a work-related assessment, pointing engineering candidates at levels L3 and L4 to a domain assessment. Aced describes an optional, auto-scored online assessment of easy to medium data structures and algorithms questions. [2][3][6]
3. **Technical phone screen**: The backend guide lists a 60 minute online business (technical) phone screen assessing coding plus design and architecture. interviewing.io reports one hour on CodeSignal with one or two algorithmic questions at about LeetCode medium level, and says a referral may let some candidates skip it. [2][5]
4. **Interview loop**: The backend guide lists three 60 minute interviews: algorithms and data structures (coding 1), depth in specialization (coding 2), and collaboration and leadership. interviewing.io describes a 4 to 5.5 hour onsite of five rounds: two coding rounds, system design, a 75 minute collaboration and leadership round with the hiring manager, and a one hour bar raiser with an interviewer from elsewhere in the company. Aced reports four to six rounds depending on seniority. [2][5][6]
5. **Decision**: Uber says each stage is a decision point and that recruiters review performance against the job criteria with the hiring team. interviewing.io reports that the panel decision must be unanimous and that one strong no-hire rejects a candidate. [1][2][5]

## Uber online assessment

Reported: sometimes. Uber's backend guide lists a HackerRank coding assessment and its internship guide lists a work-related assessment. Aced calls the online assessment optional, and interviewing.io describes a live CodeSignal phone screen with no separate assessment, so whether one is used appears to depend on role and level. [2][3][5][6]

## Uber interview questions: what the rounds cover

- Coding rounds focus on data structures and algorithms, reported as mostly LeetCode medium style problems on topics such as hash maps, arrays, strings, graphs and binary search. [2][5][6]
- The depth in specialization round follows the candidate's domain; Uber publishes separate engineering guides for domains such as Android, Backend, Data, Frontend, iOS and ML and AI. interviewing.io says this round is sometimes algorithmic and sometimes design oriented. [2][5][7]
- Design and architecture is assessed by Uber; third-party guides describe fairly standard system design prompts with a focus on scale, and a technical retrospective on a past project for senior candidates. [2][5][6]
- Collaboration and leadership questions are tied to Uber's values and success attributes, covering teamwork, handling failure and leadership. [2][5]
- interviewing.io reports the bar raiser is usually a deep dive into one past project and is used for leveling. [5]

## How long is the Uber interview process?

Uber does not publish an overall duration in the pages reviewed; its guides say rescheduling is limited and that each stage is a decision point. interviewing.io reports about 4 to 6 weeks overall, with team matching, when needed, taking weeks to months. Aced expects a final decision in three to six weeks. [2][3][5][6]

## Uber new grad interview

Uber's internship interview guide lists a recruiter phone screen, a work-related assessment, a business interview with the team and an outcome, and says engineering candidates at levels L3 and L4 take a domain assessment. It does not publish round counts or durations. The backend guide lists levels from L3 to L6+ and says expectations grow with level. [2][3]

## Team matching at Uber

interviewing.io describes Uber's process as hybrid: candidates may be matched to a team at the start or at the end, and niche roles such as ML are more likely to be matched early. Aced says each team recruits and interviews independently, so requirements vary by team. [5][6]

## How to prepare for the Uber interview

- Prepare at least 1 to 2 examples of past projects for each competency and use the STAR method. [2]
- Practice talking through the approach out loud while solving problems, for example in mock interviews. [4]
- Ask the recruiter what the second coding round will involve, since expectations vary. [5]
- Write code that runs and test it during coding rounds. [5]
- Research Uber's recent launches, priorities and values before interviewing. [1]

## What the sources do not agree on

- Uber's backend guide names HackerRank for the coding assessment, while interviewing.io and Aced describe CodeSignal for the phone screen and interviews.
- Round counts differ: the backend guide lists three interviews after the phone screen, interviewing.io describes a five round onsite with system design and a bar raiser, and Aced reports four to six rounds depending on seniority.
- The backend guide's own introduction says it outlines the general Android engineering process, so its steps may not be backend specific.
- The collaboration and leadership round is 60 minutes in Uber's guide and 75 minutes in interviewing.io's description.
- Uber publishes no overall timeline; interviewing.io reports about 4 to 6 weeks and Aced three to six weeks.

## Practice for the Uber interview

- [Browse software engineering jobs](https://devsunite.com/jobs) - Uber has too few open roles on DevsUnite for its own page right now
- [Uber coding interview questions](https://devsunite.com/resources/faang-interview-questions/uber) - LeetCode problems tagged Uber, grouped by topic
- [Behavioral interview questions](https://devsunite.com/guides/behavioral-interview-questions) - 35 common questions by theme, with STAR sample answers
- [Uber H1B sponsorship](https://devsunite.com/h1b-sponsors/uber) - Certified H-1B LCAs and offered wages from US Department of Labor data
- [AI mock interview](https://devsunite.com/mock-interview) - Practice role-based questions and get feedback
- [Resume match score](https://devsunite.com/analyse) - Check your resume against a job description
- [Resume builder](https://devsunite.com/resume-builder) - Build an ATS-ready resume
- [Share your interview experience](https://devsunite.com/share-interview-experience) - Sat this interview? Tell the next candidate what each round was like

## Uber interview process FAQ

### How many rounds are in the Uber interview process?

Uber's backend engineering guide lists a 30 minute recruiter call, a HackerRank coding assessment, a 60 minute technical phone screen and three 60 minute interviews covering coding, depth in specialization, and collaboration and leadership. interviewing.io reports a five round onsite that adds system design and a bar raiser. The published stages, in order: Application and recruiter call, Coding assessment, Technical phone screen, Interview loop, Decision.

### What is the Uber software engineer interview like?

Uber's official hiring page lists an application, a talent team conversation, a hiring manager chat, a technical interview for tech roles, a role-dependent exercise or assessment, a team interview and then a decision. Its backend engineering interview guide lists a 30 minute recruiter or sourcer call, a HackerRank coding assessment, a 60 minute technical phone screen on coding plus design and architecture, and then three 60 minute interviews covering coding, depth in specialization, and collaboration and leadership. interviewing.io describes a five round onsite that also includes system design and a bar raiser.

### How long is the Uber interview process?

Uber does not publish an overall duration in the pages reviewed; its guides say rescheduling is limited and that each stage is a decision point. interviewing.io reports about 4 to 6 weeks overall, with team matching, when needed, taking weeks to months. Aced expects a final decision in three to six weeks.

### Is there an Uber online assessment?

Uber's backend guide lists a HackerRank coding assessment and its internship guide lists a work-related assessment. Aced calls the online assessment optional, and interviewing.io describes a live CodeSignal phone screen with no separate assessment, so whether one is used appears to depend on role and level.

### What is the Uber new grad interview like?

Uber's internship interview guide lists a recruiter phone screen, a work-related assessment, a business interview with the team and an outcome, and says engineering candidates at levels L3 and L4 take a domain assessment. It does not publish round counts or durations. The backend guide lists levels from L3 to L6+ and says expectations grow with level.

### What Uber interview questions should I expect?

Coding rounds focus on data structures and algorithms, reported as mostly LeetCode medium style problems on topics such as hash maps, arrays, strings, graphs and binary search. The depth in specialization round follows the candidate's domain; Uber publishes separate engineering guides for domains such as Android, Backend, Data, Frontend, iOS and ML and AI. interviewing.io says this round is sometimes algorithmic and sometimes design oriented. Design and architecture is assessed by Uber; third-party guides describe fairly standard system design prompts with a focus on scale, and a technical retrospective on a past project for senior candidates. Collaboration and leadership questions are tied to Uber's values and success attributes, covering teamwork, handling failure and leadership. interviewing.io reports the bar raiser is usually a deep dive into one past project and is used for leveling.

## Sources

1. [How We Hire](https://jobs.uber.com/en/what-moves-us/how-we-hire/), Uber (official)
2. [Backend Engineering Interview Guide](https://jobs.uber.com/en/uber-interview-guide/backend-engineering-interview-guide/), Uber (official)
3. [Internship Interview Guide](https://jobs.uber.com/en/uber-interview-guide/internship-interview-guide/), Uber (official)
4. [Ace an Uber engineering interview: tips from Aarhus](https://jobs.uber.com/en/people-stories/interview-prep/ace-an-uber-engineering-interview-tips-from-aarhus/), Uber (official)
5. [Uber's Interview Process & Questions](https://interviewing.io/uber-interview-questions), interviewing.io
6. [Uber Software Engineer Interview Guide](https://www.aced.io/guides/uber-software-engineer-interview), Aced
7. [Engineering Interview Guides](https://jobs.uber.com/en/uber-interview-guide/engineering/), Uber (official)

## Related

- [Goldman Sachs interview process](https://devsunite.com/interview-process/goldman-sachs-interview-process)
- [Salesforce interview process](https://devsunite.com/interview-process/salesforce-interview-process)
- [Adobe interview process](https://devsunite.com/interview-process/adobe-interview-process)
- [Atlassian interview process](https://devsunite.com/interview-process/atlassian-interview-process)
- [All interview process guides](https://devsunite.com/interview-process)
