Interview100x

Interview prep

How to prepare for an Uber software engineer interview

Uber publishes a backend engineering interview guide that names each stage and gives durations for most of them, from an online HackerRank assessment through two 60-minute coding rounds and a Collaboration & Leadership round4. The same guide lists the competencies interviewers use and says expectations rise by level, from L3 to L6+4. This page turns that guide into a preparation plan and marks the details, such as which competencies apply to you, that Uber says your recruiter will share4.

Last reviewed November 12, 2026

How the interview process works

Uber's backend guide lists a recruiter call, a HackerRank assessment, a 60-minute business phone screen, two 60-minute coding interviews and a 60-minute Collaboration & Leadership interview, with a decision possible after each stage4.
  1. 1.Recruiter or sourcer call

    A virtual conversation of about 30 minutes4. Uber's general hiring page says early conversations cover your experience, your fit for the role and your motivation in relation to Uber's mission1. Use this call to ask which competencies and which specialisation your loop will cover.

  2. 2.HackerRank coding assessment

    The backend guide lists an online HackerRank assessment as its own step, without a stated length4. Ask your recruiter for its length and format before you sit it rather than guessing.

  3. 3.Business (technical) phone screen

    About 60 minutes online, assessing coding and also design and architecture4. Design appears this early in Uber's list, so prepare the screen as a mixed round, not a pure coding test.

  4. 4.Coding 1: algorithms and data structures

    About 60 minutes4. Uber says its technical interview looks at how you build and solve problems, how clearly you think and how you work with others on a shared problem in real time1.

  5. 5.Coding 2: depth in your specialisation

    About 60 minutes on depth in your area4. Confirm with your recruiter what specialisation means for your team, for example concurrency, storage, APIs or something else your team owns.

  6. 6.Collaboration & Leadership

    About 60 minutes of behavioral discussion, for which Uber recommends the STAR method4.

  7. 7.Decision

    Uber treats each stage as a decision point and says candidates who are not a fit are told promptly4. At the end, the hiring team reviews performance against the role's criteria and Uber's values1.

What this is based on

This follows Uber's backend engineering guide as reviewed on 12 November 2026, which gives stage names and most durations but no question formats, HackerRank length or per-team definition of specialisation4. Frontend, mobile, data, ML & AI and other tracks have their own Uber guides, which this page does not cover, and Uber says steps can vary by role, location and business needs23.

Practice questions in the style of this role

Generated by Interview100x's question engine for this role. These are not questions reported from Uber.
  1. Tell me about a piece of work that shows the area of software engineering where you have gone deepest.
  2. As a Software Engineer here, what outcomes would you expect to deliver in your first six months?
  3. Consider two ways to structure matching: assign each request to the single closest driver right away, or collect requests for a few seconds and assign them together. How would you decide between them?
  4. How would you prevent two riders from being matched to the same driver when requests arrive at nearly the same moment?
  5. Walk me through a key design decision you made for a system, including the alternatives you considered.
  6. Tell me about a time you and a group of engineers had to settle a disagreement over a technical trade-off in a project.
  7. Tell me about a time you convinced your team to adopt a technical direction they were initially unsure about.
  8. Tell me about a time you disagreed with a teammate over a technical approach, such as a design choice or a code review.
  9. Describe a time you led a piece of work that required a partner team to change their plans or commit time.

A worked example

One practice question, a sample answer and what the evaluator said about it.

The question

How would you prevent two riders from being matched to the same driver when requests arrive at nearly the same moment?

Sample answer written for this demo

So the core problem is a race condition. Two matching processes both see the driver as available and both assign them. The simplest fix is to use a lock. When the matcher picks a driver, it takes a lock on that driver, checks that they are still available, assigns them, and releases the lock. If the lock is already held, it moves on to the next closest driver. We could use something like Redis for the lock, since it is fast. Another way is to do it in the database, with a conditional update, like update driver set status to assigned where driver ID is this and status is available, and if no rows are updated, someone else got them first. I think either would work. At this kind of scale I would probably go with Redis, because the database might be too slow. We should also make sure the lock has a timeout, in case the matcher crashes while holding it. And then once the driver is assigned, we notify them, and if they decline, we put them back as available.

Interview100x's evaluator output, unedited (fill-in gaps shown in brackets)

Ready

You made a quick, reasonable tool choice and gave a clear reason for it, which is a solid start for a system design discussion. The next step is to show how the chosen component actually behaves under load and failure.

  • What worked: You named Redis and tied it to a concern about database speed at scale, which shows you are thinking about a trade-off, but the answer stayed at the level of the component choice and did not yet explain how it works or what can go wrong with it.From the answer: At this kind of scale I would probably go with Redis, because the database might be too slow.
  • Next step: Explain how the key part works, for example how state is claimed or updated so two workers cannot take the same driver at once, using an atomic claim, lock, or conditional update.
  • Next step: Describe how retries and lease expiry handle a crashed worker or a duplicate message, so the same request is not processed twice.
  • Next step: Name the failure modes you would watch for, such as a crash mid-update, duplicate messages, or stale state in the cache, and say how you would detect them.
  • Next step: Pick one component from your design and walk through how it handles a crashed worker and a duplicate message, stating the mechanism you would use to prevent double assignment.

What the role is evaluated on

Software engineering
A named competency in the backend guide4. Good looks like correct, readable code you can test and reason about aloud. Uber says it values how you solve a problem as much as the solution itself1, so a working answer reached in silence leaves evidence on the table.
Design & architecture
Also a named competency, and the business phone screen assesses it alongside coding4. Expect to explain components, data flow, failure handling and the trade-off you chose, at a depth that fits your target level.
Collaboration & leadership
It has its own 60-minute round4. Uber's hiring page says team conversations look at collaboration, decision-making and how you contribute in fast-moving environments1. Stories should show your decision and its consequence, not only the team's result.
Scope that matches your level
The guide describes expectations from L3 to L6+ that grow in scope, complexity and impact4. An L5 or L6 candidate whose examples are all single-ticket work will read as under-levelled even with clean code.
Behavioural traits Uber names
Uber's engineering guides also list adaptability, bias towards action, entrepreneurial, grit, interpersonal influence and inquisitiveness, and say the recruiter will share which apply to you45. Have at least one specific story for each one that applies.

Common ways answers fall short

  • Preparing the phone screen as coding only

    Uber's list puts design and architecture inside the 60-minute business phone screen4. Candidates who only drill algorithm problems can run out of material when the conversation turns to how a system should be built.

  • Solving in silence

    Uber's guide asks candidates to explain how they reached an answer4. A correct solution with no narration gives the interviewer little to judge your reasoning by. Say what you are trying, why, and what you would test.

  • No depth ready for Coding 2

    A whole hour is set aside for depth in your specialisation4. If you cannot name the two or three areas you know deeply and go several layers down on each, this round becomes a second generic coding round, which it is not meant to be.

  • Treating the interviewer as an examiner only

    Uber's guidance encourages you to challenge, clarify and collaborate with interviewers4. Asking about constraints, pushing back on an assumption with a reason, and checking your direction are part of what the session can show.

  • Stories pitched at the wrong level

    Behavioral stories that describe tasks rather than decisions, or a team's win with no clear personal contribution, are a common weakness in leadership rounds generally. Against a level rubric from L3 to L6+4, they make it hard for interviewers to place you.

A prep plan for the time you have

One week

Confirm the shape, then cover each round once

  1. Ask your recruiter three things: the HackerRank format, what Coding 2 will treat as your specialisation, and which competencies apply at your level4.
  2. Do two timed algorithm problems a day, speaking your reasoning out loud the whole time.
  3. Prepare one 10-minute spoken walkthrough of a system you built: components, data flow, the main trade-off and what you would change.
  4. Write four STAR stories that map to collaboration, leadership, adaptability and bias towards action, each with your decision and a concrete result.
  5. Run one full voice practice session on the Collaboration & Leadership round and rewrite the story that drew the hardest follow-up.
  6. Skim Uber's newsroom for recent launches and read the job description line by line, as Uber suggests1.

Suggested pass: Trial Pass, $12One week leaves room for one realistic behavioral session to test whether follow-up questions expose a weak story; the trial is credited toward Sprint if you want more.

Two weeks

Build depth for Coding 2 and repeat the leadership round

  1. Days 1-5: one algorithms topic per day (graphs, intervals, heaps, hashing, dynamic programming), three problems each, narrated.
  2. List the two or three specialisation areas you will claim and write five questions you would expect on each; answer them aloud.
  3. Do two design walkthroughs at increasing scale, timing yourself to fit inside part of a 60-minute screen.
  4. Run the Collaboration & Leadership round in voice practice three or four times, changing the story set until the feedback stops flagging vague ownership.
  5. In week two, simulate a loop day: two 60-minute coding sessions back to back, then a behavioral session, resetting between rounds since Uber advises not letting one interview define you4.
  6. Prepare two questions for each interviewer, which Uber's guide recommends doing in advance4.

Suggested pass: Sprint Pass, $99Two weeks leaves room to rehearse the talk-through and the Collaboration & Leadership round several times; practice sessions are spoken only, so write and run your code in your own editor.

Four weeks

Close gaps by level, then rehearse the full loop

  1. Week 1: take a baseline on each round, including one timed HackerRank-style set, and note which competency is weakest.
  2. Week 1-2: fix algorithm gaps by topic; keep a log of mistakes and redo each problem two days later.
  3. Week 2: map your experience to the L3 to L6+ scope description in Uber's guide4 and rewrite stories so their scope matches your target level.
  4. Week 3: practise specialisation depth by explaining one area per day for 20 minutes without notes, then checking what you missed.
  5. Week 3: run two design discussions per week out loud, focusing on trade-offs and failure modes.
  6. Week 4: two full mock loops with rest days between, then a light final review of stories and questions for interviewers.

Suggested pass: Sprint Pass, $99A month covers the HackerRank assessment, both 60-minute coding rounds and the Collaboration & Leadership round for this Uber loop; if you are also interviewing elsewhere, Search covers several jobs.

Questions candidates ask

Does the Uber software engineer process include a HackerRank test?
Uber's backend engineering guide lists an online HackerRank assessment as a stage4. As reviewed on 12 November 2026, the guide gives no length or problem count for it, so ask your recruiter.
Is there a separate system design round in the Uber backend loop?
In the backend guide as reviewed on 12 November 2026, design and architecture are assessed in the business phone screen and listed as a core competency, with no separate design round in the stage list4. Uber's data engineering guide, by contrast, does list a separate design round5, so check which guide applies to your role.
How long are the Uber engineering interviews?
The recruiter call is about 30 minutes, and the phone screen, both coding rounds and the Collaboration & Leadership round are about 60 minutes each4. Uber notes that steps can vary by role, location and business needs2.
Can I use AI tools during an Uber interview?
Uber's guides include this among their frequently asked questions46. Ask your recruiter for the current answer, and assume not unless they say otherwise.
What levels does the Uber backend guide cover?
It describes expectations from L3 to L6+, growing in scope, complexity and impact4. Ask your recruiter which level you are being considered for so you can pitch your examples to it.

Practice with an interviewer that follows up

A Trial Pass is one full practice session with feedback on your own answers. It counts toward a Sprint Pass if you continue.

Practice this question now

Sources

  1. 1.How we hire | Uber Careers · jobs.uber.com · undated · accessed 2026-11-12
  2. 2.Uber Interview Guide · jobs.uber.com · undated · accessed 2026-11-12
  3. 3.Engineering Interview Guide | Uber Careers · jobs.uber.com · undated · accessed 2026-11-12
  4. 4.Backend Engineering Interview Guide | Uber Careers · jobs.uber.com · undated · accessed 2026-11-12
  5. 5.Data Engineering Interview Guide | Uber Careers · jobs.uber.com · undated · accessed 2026-11-12
  6. 6.Sciences Interview Guide | Uber Careers · jobs.uber.com · undated · accessed 2026-11-12

Interview100x is not affiliated with, endorsed by, or sponsored by Uber. Company names are used only to identify the employer. Process details are summarized from Uber's public pages, linked above; they can change, so check the company's own careers site.

Last reviewed November 12, 2026