Uber Interview Guide: Process, Questions, and How to Prepare

Uber runs three main stages for most engineering roles. They are a recruiter screen, a technical screen, and an onsite loop of four to six interviews. Candidates report about two to six weeks from the first call to a decision.

This guide covers each stage, what the interviewer grades in it, the reported timeline after the loop, and how to prepare.

The Interview Process

Two parts of this order surprise people.

The first is CodeSignal. Uber uses it for the technical screen, so your first coding round often has an automatic grader. New graduates report a separate online assessment of four problems in about 70 minutes.

The second is the bar raiser. This is an interviewer from a different team who is not hiring you. Their job is to keep the hiring standard the same across teams.

Candidates report that this round carries extra weight. A strong opinion from the bar raiser can change a close decision.

The loop also changes with level. New graduates report a coding heavy process. Mid level and senior candidates report system design and ownership questions instead.

For a stage by stage version of the timeline, read How long is the Uber interview process?.

The Recruiter Screen

The recruiter screen is a short call, about 30 minutes. The recruiter confirms your experience, the level you are being considered for, and your location.

You will be asked why you applied. Have a short answer ready that names the product area you want to work on. Recruiters treat a vague answer about the company as a sign that you did not prepare.

This call also sets your level. Say what you owned in your last two projects, not what your team owned. The recruiter writes that down and passes it to the interviewers.

The Coding Round

Coding appears at least twice. Once in the technical screen, and once or twice more inside the onsite loop.

The technical screen runs on CodeSignal for about an hour. Candidates report one or two problems at medium difficulty. Interviewers expect code that compiles and runs, not an outline in comments.

The topics reported most often are hash maps, arrays, strings, binary search, matrices, linked lists, and graphs. A typical question: given a grid of cells, return the number of separate connected regions. You would explain a traversal, write it, and then run it on a small grid yourself.

One onsite round is often a specialization coding round. It uses the same kind of problem, but shaped around the work of the team. Backend candidates report questions about parsing, rate limits, and in memory data structures.

For the question types candidates report most, see What questions are asked in the Uber interview?.

What the interviewer grades here is simple. They want correct code, tested by you, and explained while you write it.

Practice by pattern, not by problem count. Our course Grokking the Coding Interview groups problems into the patterns that repeat in these rounds.

The System Design Round

System design is a 60 minute session for mid level and senior candidates. You design a system out loud and defend the choices.

Uber's questions come from its own products. Candidates report questions such as designing a ride matching service and a real time location tracking service. Surge pricing, notifications, and payments also appear.

These questions share one hard part. Location updates arrive from a large number of drivers at the same time. A rider still has to be matched with a nearby driver in about a second.

So the interviewer listens for geospatial indexing, a streaming pipeline, caching, and sharding. Say how you split the map into cells. Then say how you find drivers in the cells next to the rider.

The answer pages on this site list the questions candidates report, with the parts each one is testing. Start with What are Uber system design interview questions? and work through the examples there.

Say your assumptions before you draw. Name the request rate you are designing for. Then name what breaks when one service stops answering, and what the system does next.

The Behavioral Round

Uber runs a dedicated behavioral session, often called collaboration and leadership. Candidates report about 75 minutes with a hiring manager. The bar raiser round also spends time on past projects.

The questions are about your past work, not hypotheticals. One example candidates report is the most ambitious goal you have set.

Another asks about a time two groups wanted opposite things. A third asks about a time you moved fast and caused a problem.

Uber publishes cultural values, and interviewers score your answers against them. The ones named most often are go get it, trip obsessed, and build with heart. Stand for safety, one Uber, and great minds do not think alike also appear.

Two of these shape the questions more than people expect. Trip obsessed means Uber serves riders and drivers at the same time, so an answer that weighs only one side scores lower. Stand for safety means a safety question needs a real decision you made, not a slogan.

Use one structure for every story. Situation, your task, the actions you personally took, and the measured result. Keep each story under two minutes.

The answer page Top Uber Behavioral Interview Questions (and How to Answer Them) gives the question list and a worked answer for each.

You will also be asked why Uber. The strong version names a product problem you find interesting. Connect it to work you have already done.

See Why do you want to join Uber answer? for how to build that answer without guessing.

The Bar Raiser Round

The bar raiser is about 60 minutes with an engineer from a team that is not hiring you. Their job is to keep the hiring standard the same across teams. Candidates report that this round often decides a close case.

Most of the hour is one past project in deep detail. Expect questions about what the system did, the design choices you made, and the impact of the work. Be ready to name what went wrong and what you changed after.

The interviewer is also checking your level. Say what you decided yourself and what you handed to other people. An answer that never says what you personally did makes your level hard to judge.

After the Interview

After the last session, your recruiter and all your interviewers meet. This meeting is called the debrief. Candidates report that it happens within a few days of the last round.

The panel needs agreement. Candidates report that one strong no is usually enough to end the process. A weak no can be discussed if the other rounds are strong.

Feedback timing is reported as a few days to about a week after the loop. Team matching adds more time, because you speak with teams before an offer is written. That step is the most common reason a process runs longer than expected.

The stage by stage waiting times are listed in How long is the Uber hiring process?.

Rejections usually arrive as a short email from the recruiter. Detailed round by round feedback is rarely given. You can ask your recruiter for a summary, and some candidates report getting one.

Follow up once, about a week after the date the recruiter gave you. One short email is enough. Uber does not publish a waiting period before you reapply, and candidates report different waits for the same team and for a different team.

How to Prepare

Practice coding under a timer. The screen is graded partly on finished, running code. Solve medium problems in 30 to 35 minutes, then test them yourself without help.

Learn the patterns, not the problem list. Sliding window, two pointers, binary search on the answer, graph traversal, and heaps cover most of what candidates report.

Prepare geospatial and streaming design. Uber questions repeat around location, matching, and pricing. Be ready to explain map cells, message queues, caches, and sharding in plain words.

Write six behavioral stories. Cover conflict, failure, ownership, a tight deadline, working across teams, and a decision you changed. Map each one to a value listed above.

Rehearse the why Uber answer out loud. Name a product area and a concrete problem in it. Two sentences is enough.

Do a full mock loop in one sitting. The onsite is four to six sessions back to back. Practice the sequence, not only single rounds.

For the design rounds, Grokking the System Design Interview walks through the building blocks these questions repeat, including a ride sharing service.

Frequently Asked Questions

How many rounds does the Uber interview have? Most engineering candidates report three stages and four to six onsite sessions. The stages are a recruiter screen, a technical screen, and the onsite loop. The exact session count depends on the level and the team.

Is the Uber coding interview hard? Candidates report medium difficulty problems, similar to other large technology companies. The pressure comes from the timer and from the expectation of running code. Interviewers want you to test your own solution before they ask.

Does Uber ask system design questions? Yes, for mid level and senior engineering roles. The questions usually come from Uber products such as ride matching, location tracking, and surge pricing. New graduates are less likely to get one.

What is the Uber bar raiser round? It is an interview with an engineer from a team that is not hiring you. That person checks that the hiring standard is the same across teams. Most of the hour is a deep dive on one past project. Candidates report that this round often decides a close case.

How long does Uber take to respond after the onsite? Candidates report a few days to about a week for a decision. Team matching can add more time. Ask your recruiter for a date, then follow up once after that date passes.

Can I reapply to Uber after a rejection? Yes. Uber does not publish a fixed waiting period. Candidates report shorter waits for a different team than for the same team, so ask your recruiter what applies to you.

All Uber Interview Questions and Answers

System design round

• What are the top system design interview questions for Uber interview?

Behavioral round

• How to answer why do you want to work at Uber?

Company and role questions

• What do they ask in an Uber interview?
• Why do I want to join Uber?
• What is Uber interview?
• Why Uber interview questions?

Guides for other companies are collected in the tech company interview guides hub.