0 day streak

Uber interview rounds

Product US and India Bar raiser Machine coding / LLD

Pick your level above: the list shows only your rounds, with what interviewers score at that level.

0%ready
  1. Phone / recruiter screen · 30 min

    A recruiter call on background, the target business line and why Uber.

    At : Usually one medium problem. Explain your idea before coding and test by hand at the end.

    At : One or two problems, a little faster. Some companies mix in a design question.

    At : Often a coding problem plus questions about your past systems; some companies (Uber) use it to set your level.

    At : Frequently a hiring-manager conversation about scope and impact instead of pure coding.

  2. Online assessment · 90 min

    A timed online assessment scored on hidden tests; problems are hard and must pass every case.

    At : The main filter for new grads and campus drives. Expect two medium problems, sometimes one hard. Passing all test cases on both usually gets you to the next round.

    At : Used by some companies for experienced hires (Amazon, Uber, Salesforce, Oracle). The bar is the same as for SDE 1 but the time is often shorter.

    At : Rare. Most companies replace it with a live screen for senior candidates.

    At : Almost never used.

  3. Coding (DSA) · 60 min

    The business phone screen mixes coding with some design, and largely sets the level you interview for.

    At : The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.

    At : Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.

    At : Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.

    At : One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.

  4. Coding (DSA) · 60 min

    Onsite Coding 1 covers algorithms and data structures at medium-hard level; graphs and DP are common.

    At : The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.

    At : Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.

    At : Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.

    At : One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.

  5. Low-level design / machine coding · 60 min

    Coding 2, 'Depth in Specialization', is often machine coding or object-oriented design for backend roles, such as file-system commands with concurrency.

    At : Object-oriented design with clear classes and responsibilities. Working code matters more than patterns.

    At : The core round at many product companies: working, modular, extensible code with validation, error handling and tests, finished on time.

    At : Same as SDE 2 plus concurrency (two users booking the same seat) and a clean extension story.

    At : Rare as a standalone round; folded into design discussions.

  6. System design (HLD) · 60 min

    System design focused on scale, async processing and failure handling, sometimes starting from your own past work.

    At : Usually absent, or light design questions inside a coding round.

    At : Present at most companies. A sound end-to-end design with sensible components and basic scaling is enough.

    At : One or two rounds that set your level. Expected to lead, size the system and go deep on two or three hard parts.

    At : Two rounds at many companies. Expected to handle ambiguity, cost, operations and cross-team trade-offs, and to change the design when the interviewer pushes.

  7. Hiring manager · 60 min

    Collaboration & Leadership: a behavioral round, usually with the hiring manager, on past projects and conflicts.

    At : Motivation, learning, a project walk-through and sometimes CS fundamentals.

    At : Ownership of features, handling production issues, working with product and other teams.

    At : Technical leadership, mentoring, and how you choose what to work on.

    At : Strategy, influence without authority and the biggest bets you have made.

  8. Bar raiser · 60 min

    A cross-org Bar Raiser runs a project deep dive or reverse design, carries a lot of weight for leveling, and moderates the debrief.

    At : Behavioral depth plus a coding or object-oriented design problem.

    At : Behavioral depth with probing follow-ups; sometimes design.

    At : Scope and leadership of your projects; a strong signal for level.

    At : Org-level impact and judgment.

What interviewers look for

  • Working, test-passing code under time pressure
  • Extensible OOP design with concurrency awareness in machine coding
  • Scalability and failure handling in design
  • Scope and impact of past projects
  • Bias towards action and ownership

Worth knowing

  • The official backend guide lists the onsite as Coding 1 (algorithms), Coding 2 (depth in specialization) and Collaboration & Leadership, 60 minutes each.
  • India SDE-2 loops in 2025 consistently include a machine-coding round of 45–90 minutes plus a separate HLD round.
  • The Bar Raiser decides a lot about leveling; one strong no-hire is generally enough to sink a candidate.
  • The OA requires passing all hidden tests, and its problems often reach hard level.

Sources

Written in our own words from public candidate reports and Uber's careers pages, checked 2026-11. Company names and logos belong to their owners; AlgoRung is not affiliated with Uber.

Questions people ask

How many interview rounds does Uber have for SDE 1 (L3 Software Engineer I)?

About 4 interviews after the screening: phone / recruiter screen, online assessment, coding (dsa), low-level design / machine coding, hiring manager. Design is part of the loop at this level.

How many interview rounds does Uber have for SDE 2 (L4 Software Engineer II)?

About 5 interviews after the screening: phone / recruiter screen, online assessment, coding (dsa), low-level design / machine coding, system design (hld), hiring manager. Design is part of the loop at this level.

How many interview rounds does Uber have for SDE 3 (L5A Senior Software Engineer)?

About 6 interviews after the screening: phone / recruiter screen, coding (dsa), low-level design / machine coding, system design (hld), hiring manager, bar raiser. Design is part of the loop at this level.

How many interview rounds does Uber have for staff (L5B Staff, L6 Senior Staff)?

About 5 interviews after the screening: phone / recruiter screen, coding (dsa), system design (hld), hiring manager, bar raiser. Design is part of the loop at this level.

What coding questions does Uber ask?

The most reported are Evaluate Division, Swim in Rising Water, Number of Operations to Make Network Connected, My Calendar I, Task Scheduler, Surrounded Regions. Candidates say Uber focuses on graphs, union-find, dynamic programming, heaps, intervals.

What is the Uber behavioral interview based on?

Interview competencies (official interview guide): Collaboration & Leadership, Design & Architecture, Software Engineering, Adaptability, Bias Towards Action, Entrepreneurial, Grit, Interpersonal Influence, Inquisitiveness. The official guide lists these as the competencies scored across rounds; the recruiter tells you which apply to your role. The behavioral round wants STAR stories showing ownership, influence and grit.