Uber Interview Process (2026) — rounds, timeline & what they hire for

How many interview rounds does Uber have?

Uber runs 8 round types:

• Recruiter screen — 45–60min call · background, motivation, mutual expectations
• Online assessment — self-guided coding questions (optional, level-dependent) · easy-to-medium data structures & algorithms
• Technical phone screen — ~60min on CodeSignal with an Uber engineer · general coding; seniors also discuss past design/architecture work
• Onsite: general coding — 45–60min (30–40min problem + experience questions) · easy-to-medium DSA, clean working code
• Onsite: specialized coding — 45–60min domain problem · backend: data-structure design (e.g. parking lot); web/mobile: component implementation
• Onsite: system design — 45–60min design discussion · requirement clarification, architecture, bottlenecks, trade-offs
• Onsite: behavioral — 45–60min with the hiring manager · collaboration, leadership, cultural alignment
• Onsite: technical retrospective (senior) — 45–60min project deep-dive · technical decisions, infrastructure, trade-offs, stakeholder dynamics

How long does the process take?

Uber takes 3–6 weeks end to end.

Recruiter screen, an optional online assessment (easy-to-medium DSA), a one-hour CodeSignal technical phone screen, then an onsite of four to six rounds: general coding, domain-specific coding, 'design Instagram'-style system design, and a hiring-manager behavioral. Senior candidates add a technical retrospective deep-diving one resume project.

What does Uber look for?

• End-to-end ownership — Engineers carry projects from conception through rollout without a safety net.

  • owned a project across design, build, and operations

• Collaboration and leadership — What the hiring-manager round exists to probe.

  • led through influence in a cross-functional setting

Insider tips

• Uber engineers own design end-to-end — there's no separate architect, so design rounds carry hire-level weight for every level.
• The OA doesn't require a perfect score, but you should be able to solve every question type it shows.
• In specialized coding, the domain matters: practice modeling real-world objects for backend or building components for web/mobile.
• Clarify requirements and edge cases out loud before designing — it's an explicit assessment criterion.

How it varies by team

• entry vs senior: Seniors add the technical retrospective round and get architecture discussion already at the phone screen; entry loops stay coding-heavy.

Most-asked at Uber

FAQ

Sources

• Exponent: Uber Software Engineer Interview Guide

Compare with other companies