Start free
All interview guides

Sources checked

Uber

Uber publishes its engineering loop stage by stage: a recruiter call, a HackerRank assessment, a 60-minute technical screen that covers design and architecture as well as coding, then two 60-minute coding rounds and a named collaboration and leadership round.

The Uber process

4 of 7 stages you can practise here

  1. 01
    Recruiter Screen30 minchill

    Warm, logistical, fast-moving

    motivationbackground fitcommunication
  2. 02
    HackerRank coding assessment (not simulated here)

    An online coding assessment Uber lists between the recruiter call and the technical screen. Uber does not publish a duration or a problem count for it.

  3. 03
    Technical phone screen

    Uber's own label is "Business (Technical) Phone Screen to Assess Coding + Design & Architecture Competencies (Online | 60 min)". Design and architecture are assessed inside this screen rather than as a separate round.

    2 rounds you can practise

    Coding, Phone Screen50 minrealistic

    Shared editor, camera on, brief intros then straight to 1-2 problems

    problem-solvingds&a fluencycode quality
    System Design55 minbrutal

    Verbal plus diagramming

    requirementsarchitecturescalability & latency
  4. 04
    Coding, Onsite55 minbrutal

    Same live-editor setup, higher bar

    problem-solving at scaleadaptabilitycode quality
  5. 05
    Interview 2: Depth in specialization

    Uber publishes this as "Software Engineering - Depth in Specialization (Coding 2)", 60 minutes. The applied round, weighted toward your domain rather than general algorithms.

  6. 06

    Conversational, STAR-driven, calibrated interviewer

    ownership & impactcollaboration & conflictambiguity
  7. 07
    Decision

    Uber names a "Decision" stage in which recruiters and hiring teams review performance against the role criteria. Uber does not publish committee mechanics or a debrief format.

Common questions

What levels does Uber use for software engineers?
Uber's SWE ladder on levels.fyi runs from L3 (Software Engineer I, entry level) and L4 (Software Engineer II) through L5 (Senior, shown as 5a; Staff shown as 5b) up to L7+. Your target level shapes the loop: more senior means more weight on system design and leadership scope; new-grad L3 is coding-heavy with little or no full system design.
What does Uber's engineering culture emphasize?
Uber's engineering site says engineers are "trusted to explore and experiment freely, using innovation to drive impact," and describes building "systems that learn from billions of signals in real time." Teams span AI, ML, autonomous vehicles, safety infrastructure, real-time systems, and marketplace platforms, so ownership, real-world impact, and scale run through the interview.
Does Uber have a 'bar raiser' round like Amazon?
The bar-raiser construct is canonically Amazon's. Uber runs a leadership-and-values behavioral round with calibrated interviewers and a hiring-committee debrief, but we could not confirm a formally named, cross-org 'Bar Raiser' program at Uber from any citable source. Treat the behavioral round as leadership & values, not a named bar-raiser.
What kind of system design does Uber ask engineers?
System design is standard for senior (L5+) loops. Given Uber's business, prompts skew geospatial and real-time, matching riders to drivers, nearby-driver proximity search, ETA, surge pricing, rate limiting, notifications. This aligns with Uber's own description of real-time systems processing billions of signals. New-grad (L3) loops usually skip or lighten full system design.

Sources

Built from what Uber publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.

  • Engineering culture and values framing: engineers 'trusted to explore and experiment freely, using innovation to drive impact'; 'systems that learn from billions of signals in real time'; domains include AI/ML, autonomous vehicles, real-time and marketplace systems.

  • Uber SWE level ladder: L3 (SWE I, entry) through L4 (SWE II), L5 (Senior 5a / Staff 5b), and L7+. Compensation context only, no interview-process detail.

  • Uber's published engineering loop with its own stage names and durations: recruiter or sourcer call (30 min), HackerRank coding assessment, "Business (Technical) Phone Screen to Assess Coding + Design & Architecture Competencies" (60 min), Algorithms & Data Structures (60 min), Depth in Specialization (60 min), Collaboration & Leadership (60 min), Decision. Shows the L3, L4, L5A, L5B, L6+ ladder and names no standalone system design round.

Sources last checked . Hiring loops change, so this date is the honest limit on everything above.