RoundHound
?Sign inAccess
Prepare
HomeHomeTargetsTargetsPractice historyHistoryProgressProgress
Get full access?Sign in
Targets/Uber

Distributed Systems Engineer

Uber · Senior, L5a

Research from Sep 65 rounds, none tried
How did it actually go?

Recommended next: your first attempt

Do the Technical coding screen round.

A complete first attempt shows where you stand before any narrow practice starts.

Set up this round →Rehearse the full day
Length60 min · Senior, L5a level

The loop

5 rounds · 5 h

Pick a round to see what it asks of you and where you stand on it.

Technical coding screen

Solve an unfamiliar problem with a justified model, complete code and room for a meaningful follow-up.

Coding · 60 minSet up this round →
Not tried yetNo attempt yet.

What strong sounds like

  • Define the state and edge cases that determine the algorithm.
  • Explain why the selected structure or traversal fits the constraints.
  • Deliver readable code with correct state updates and termination.
  • Trace an adversarial input, state complexity and respond to the extension.

Expect to be pushed on

What changes if the input cannot fit in memory?
Which assumption makes the approach valid?

Shapes of problem you may get

  • An unfamiliar graph, geometry or spatial problem with an extension

How to prepare

  1. 01
    Select spatial modeling drills

    Choose two unfamiliar problems with grids, geometry, or spatial state. For each, write the state definition, boundary cases, invariant, and likely follow-up before coding.

    A reported L5A screen used a medium-hard to hard spatial problem. Prepare modeling work, not only familiar algorithm patterns.

    Company researchUber L5A senior offer: five-round experience

  2. 02
    Rehearse a coding explanation

    Prepare a short sequence for stating assumptions, selecting the data structure, explaining the invariant, and giving complexity. Rehearse it once in your strongest interview language.

    Uber guidance favors practical problem solving in a familiar language and an explanation of how the code works.

    Company research

A first attempt takes the full 60 minutes.

What this loop tests

Researched 27 days ago

Prepare for a coding screen followed by algorithmic coding, implementation depth, distributed-system design, and collaboration and leadership. Senior Uber preparation requires clear executable logic, deliberate concurrency decisions, and a design you can drive from requirements to failure recovery. Practice beyond ride matching: stateful services, caches, stream processing, and partitioned workflows. Defend the architecture and measured impact of a system you personally owned.

They reward

  • Correctness under concurrency
  • Candidate-led technical depth
  • Explicit failure behavior
  • Ownership beyond the first implementation

What to avoid

  • Do not assume the problem is a familiar tagged variant.
  • Do not leave complexity or boundary behavior unstated.
  • Do not round a scan down to constant time.
  • Do not let narration disappear under time pressure.
  • Do not add patterns that obscure state ownership.

How sure we are

Worth redoing if you hear something from the recruiter that contradicts this.

Attempts

Every session saved against this target, newest first. Standings live on the round cards.

All attempts in History →

Technical coding screen, Algorithms and data structures, Specialization: service implementation, Distributed systems design, and Collaboration and technical ownership have no attempts yet.

Uber: navigating the engineering coding interview
  • 03
    Prepare an adversarial trace

    For each selected problem, write one input that stresses boundaries or termination. Plan a manual trace and one meaningful extension before starting the practice attempt.

    The round requires complete code and a follow-up. A prepared trace protects time for verification and extension discussion.

    Suggested approach

    • Then try the round

    You have two selected spatial problems, a written state and invariant for each, and one adversarial trace with a planned follow-up.

    Resources to focus on
    • How to Stick Out from the Crowd in the Uber Engineering Interview Process

      Focus on “What does a technical recruiter look for in the phone screen?” and “If I want to get hired as an engineer at Uber, do you have any tips?”

      Use the guidance to rehearse clear reasoning, language fluency, and explanations for unfamiliar problems.

    Do

    • Use a small diagram when the state is spatial.
    • Keep the invariant explicit during coding.

    Avoid

    • Do not assume the problem is a familiar tagged variant.
    • Do not leave complexity or boundary behavior unstated.
    Confirmed · 8
    • Uber’s current engineering hiring page describes a collaborative coding interview followed by evaluation with the team and cross-functional partners.
    • Uber’s coding guidance favors practical problem solving in a familiar language and an explanation of how the code works.
    • An L5A offer report describes five one-hour interviews: phone screen, algorithms, specialization coding, design and leadership.
    • The L5A screen involved a medium-hard to hard geometry or spatial-reasoning problem.
    Likely · 2
    • Senior distributed-systems preparation should include retries, stale state, hot partitions and explicit concurrency invariants.
    • A convincing project account should connect a personal technical decision to reliability, latency, cost or delivery outcomes.

    Worth asking them

    Questions that close the gaps above.

    Which consistency or latency constraint dominates this team’s systems?
    What distinguishes L5a impact from strong individual execution here?
    How do teams coordinate when an incident crosses service boundaries?

    Research status

    Collected Sep 6. If the recruiter tells you something this brief contradicts, correct it after the interview and the brief updates.

    Correct this brief