Interview Playbook / Big Tech

How Uber Interviews in 2026: Process, Questions & What They Score

HOW TO READ THIS PLAYBOOK

Compiled from 25 public sources: candidate interview reports, coaching guides, and Uber's own hiring pages. Interview processes change and vary by role, team, level, and region. This is one well-documented shape of Uber's interviews to prepare against, not a script of what your interview will be. Confirm specifics with your recruiter. SupaCV is not affiliated with or endorsed by Uber.

High confidenceLast verified JUL 202625 sourcesSources

Uber Technologies is best known for hiring Software Engineers (plus closely related Data Scientist, Engineering Manager, and Product Manager roles) against its ride-hailing/delivery/freight marketplace. Its process is broadly similar to other Big Tech companies (recruiter screen -> assessment/phone screen -> multi-round virtual onsite loop -> hiring committee), but with two distinctive features that recur across independent sources: (1) a dedicated "Bar Raiser" round modeled on Amazon's practice, staffed by a cross-team interviewer with no stake in the specific team, and (2) a publicly stated set of named company values that recruiters and interviewers (especially the Bar Raiser) explicitly evaluate candidates against. Reported end-to-end timelines range widely, from about 3-4 weeks to as long as 2 months, and the exact number/mix of rounds is level- and team-dependent (system design is generally reserved for mid-level+/senior candidates; specialized teams may swap in domain-specific coding or ML rounds).

The Process

  1. 1

    Resume / application screen · Varies; days to a few weeks depending on volume

    Recruiting reviews the application; matching the resume closely to the target role/level is described by multiple prep sites as the most competitive filter in Uber's funnel.

  2. 2

    Recruiter phone screen · 30-45 minutes (some candidates report up to an hour)

    Non-technical call covering background, motivation for Uber, target role/level, logistics, and compensation expectations.

  3. 3

    Online assessment (role/source dependent) · About 70-90 minutes

    Not all candidates get this step; some SWE applicants (often those applying via job boards rather than referral) report a self-guided timed coding test, historically on CodeSignal and increasingly on HackerRank (both platforms are still in active use as of 2026), with typically 2-4 algorithmic (DSA) problems ranging easy to hard.

  4. 4

    Technical phone screen · 45-60 minutes

    Live video call with an Uber engineer, usually 1-2 LeetCode-style medium (occasionally hard) coding problems on a shared editor (often CodeSignal-hosted). For Data Science roles this stage blends SQL/Python coding with statistics and A/B-testing questions.

  5. 5

    Virtual onsite loop · Roughly 4-5.5 hours total, ~45-75 minutes per round

    A block of 4-6 back-to-back (sometimes split across a day or two) interviews: one or two coding/DSA or specialization-depth rounds, a system design round (mid-level and above), a behavioral/'collaboration and leadership' conversation often with the hiring manager, and a Bar Raiser round. The Bar Raiser is typically a deep, reverse-style walkthrough of one past project (architecture, tradeoffs, quantified impact) scaled to the level being interviewed for, conducted by an interviewer from outside the hiring team who is trained to protect hiring standards. Some candidate accounts also describe the Bar Raiser as influencing leveling, not just pass/fail: a weak showing can lead to a down-level rather than an outright rejection, though this is anecdotal rather than officially confirmed.

  6. 6

    Hiring committee / debrief · About 3-5 business days, though can stretch to a couple of weeks

    Interviewers submit written feedback and a hiring committee (or the hiring manager plus recruiter) reviews the full loop against job criteria to reach a decision; if a Bar Raiser was on the loop, they typically moderate this debrief.

  7. 7

    Reference checks and offer / negotiation · Several days to about a week

    Optional reference calls, then an offer is extended with room for compensation negotiation (Uber's packages tend to be equity-heavy).

Evaluation Framework

Uber company values (used as informal culture-fit criteria, most explicitly in the Bar Raiser and behavioral rounds)

Do The Right Thing: "Period." (ethics/integrity)Go Get It: "Bring the mindset of a champion." (ambition, ownership, hustle)Trip Obsessed: "Make magic in the marketplace." (customer/user focus)Build With Heart: "We care." (empathy for users, partners, communities)Stand For Safety: "Safety never stops."See The Forest And The Trees: "Know the details that matter." (balancing big-picture and detail)One Uber: "Bet on something bigger." (cross-team collaboration)Great Minds Don't Think Alike: "Diversity makes us stronger."

This 8-item list and count are verified correct and complete; I independently confirmed the exact wording and taglines against a primary source: Uber's own 2023 and 2024 SEC proxy statements (DEF 14A filings, Uber Technologies Inc., CIK 1543151) embed a values-page graphic with this identical 8-item list, word for word, including the 'Period.' tagline on Do The Right Thing. The most recent proxy statement on file (filed March 2026) still uses 'Go Get It' and 'Do the right thing. Period.' verbatim in its running text, so the underlying value names remain current through 2026. One nuance worth flagging to candidates: Uber's 2025 and 2026 proxy statements dropped the full 'Our Values' graphic that appeared in 2023-2024, and separately, Uber's 2024 annual report (filed early 2025) dropped its dedicated diversity section and removed DEI-linked metrics from executive compensation, consistent with a broader 2025 corporate pullback from DEI framing under political pressure. That's a change in how prominently the company publicizes the diversity-themed value, not evidence the value itself was renamed or retired; 'Great Minds Don't Think Alike' was still being used by external diversity researchers describing Uber as of 2025. Bottom line for prep: treat all 8 values, including this one, as live and in use, but don't be surprised if Bar Raisers lean harder on ownership/customer-obsession framing than on the diversity angle right now. Unlike Amazon's Leadership Principles, Uber does not brand this as a formal, single named 'framework' baked into every job posting and rubric, but these 8 values are consistently and independently quoted (with identical taglines) across Uber's own SEC filings, interview-prep guides (Exponent, InterviewQuery/FourWeekMBA), and firsthand accounts, including a self-described former Uber Bar Raiser interviewer, as what interviewers score behavioral/culture-fit answers against. Historical note (confirmed accurate against the original TechCrunch/CNBC coverage): Uber previously (Nov 2017, under CEO Dara Khosrowshahi, post-Holder Report) publicized a different 8-item list of 'cultural norms': We Build Globally We Live Locally; We Are Customer Obsessed; We Celebrate Differences; We Do The Right Thing, Period; We Act Like Owners; We Persevere; We Value Ideas Over Hierarchy; We Make Big Bold Bets, which was superseded by the current list above. Also reconfirmed via multiple independent sources (Blind threads, a self-described former Bar Raiser's LinkedIn post, Pragmatic Engineer commentary): the distinct Amazon-style 'Bar Raiser' round is real and a well-corroborated, high-stakes part of Uber's SWE loop, focused on deep technical project introspection plus values alignment, and the Bar Raiser typically moderates the post-loop hiring debrief.

Sample Interview Questions

Coding & Data Structures/Algorithms8 questions
  • Count the number of vowel substrings in a string that contain all five vowels
  • Given a 2D binary matrix with exactly two islands, find the minimum number of 0s that must be flipped to 1 to connect them into one island
  • Implement an LRU Cache
  • Design a Hit Counter / rate limiter using a sliding-window approach
  • Alien Dictionary: derive character ordering from a sorted word list (topological sort)
  • Bus Routes: minimum number of buses to get from source to target (BFS/graph); widely reported as one of Uber's most-repeated interview questions
  • Solve a 0/1 knapsack-style maximization or word-break dynamic programming problem
  • Design a simplified Twitter-like feed supporting post, like, and dislike operations (OOP + coding)
System Design8 questions
  • Design a ride-matching/dispatch system (pair riders with nearby drivers at low latency and scale)
  • Design a real-time surge-pricing engine that ingests live location/demand data and recalculates multipliers
  • Design a real-time driver/vehicle location-tracking system ingesting millions of GPS pings per second
  • Design an ETA-prediction service
  • Design a notification delivery system at global scale
  • Design a payment-processing system for a marketplace like Uber
  • Design Dropbox or WhatsApp (generic large-scale system, used to gauge fundamentals)
  • Design a ride-sharing app end-to-end (a generic version of Uber's own product)
Behavioral & Values Fit8 questions
  • Tell me about yourself / walk me through your background
  • Tell me about a time you disagreed with a coworker or teammate. How did you resolve it?
  • Describe a time you took ownership of a problem beyond your defined scope
  • How do you earn the trust of a new team you've just joined?
  • Tell me about a time you had to make a decision with incomplete information or high ambiguity
  • Describe a time you advocated for the end user/customer in a product or engineering decision
  • Tell me about a time you failed. What happened and what did you learn?
  • Describe how you managed a project with a tight timeline and limited context
Technical Project Deep-Dive (Bar Raiser round)6 questions
  • Walk me through the most technically challenging project you've shipped, from start to finish
  • What was the system architecture, and what specific tradeoffs did you make and why?
  • How did you quantify the impact or success of this project?
  • What would you do differently if you rebuilt this project today?
  • Describe a technical decision you made that other stakeholders disagreed with. How did you handle it?
  • What was your specific individual contribution versus the team's, on this project?

Coach's Tips

Prepare 5-6 STAR stories mapped explicitly to Uber's stated values (ownership/'Go Get It', customer focus/'Trip Obsessed', empathy/'Build With Heart', cross-team collaboration/'One Uber', valuing diverse perspectives/'Great Minds Don't Think Alike'); this is independently confirmed all the way back to Uber's own SEC filings, not just prep-site marketing, so it's worth the prep time.

Treat the Bar Raiser round as the highest-stakes interview in the loop: come with one project, scoped to match the level you're interviewing for, that you can defend in depth: architecture choices, tradeoffs considered, your specific individual contribution, and a quantified before/after result. At senior levels, a rough Bar Raiser round more often triggers a down-level than an outright rejection, so don't assume one bad round means you're out. Keep engaging.

For coding rounds, prioritize graphs, dynamic programming, sliding-window/two-pointer, and binary search at LeetCode medium (with some hard) difficulty, and practice writing clean, interview-ready code in 25-30 minutes per problem rather than just reaching a brute-force solution. 'Bus Routes' and 'Alien Dictionary' show up often enough in candidate reports that they're worth doing cold.

For system design, default toward Uber's own domain (real-time dispatch/matching, surge pricing, live GPS tracking, ETA prediction) even for a generically framed prompt, and explicitly reason about Uber-like scale and latency constraints (e.g., millions of location updates per second, sub-second matching).

Since onsite loops are often 4-6 rounds back-to-back in a single day (roughly 4-5.5 hours), plan logistics (breaks, food, environment for a virtual onsite), since interview fatigue is a commonly cited factor in candidate write-ups of underperforming in later rounds.

Confirm with your recruiter early which loop variant you're on: the mix of coding vs. system design vs. domain-specific/ML rounds and the presence of a system design round varies meaningfully by level (junior vs. senior) and by team (generalist SWE vs. specialized org).

Common questions

How many stages are in Uber's interview process?+

Uber's process has 7 stages, in order: Resume / application screen, Recruiter phone screen, Online assessment (role/source dependent), Technical phone screen, Virtual onsite loop, Hiring committee / debrief, Reference checks and offer / negotiation.

What framework does Uber use to evaluate candidates?+

Uber evaluates candidates against Uber company values (used as informal culture-fit criteria, most explicitly in the Bar Raiser and behavioral rounds): Do The Right Thing: "Period." (ethics/integrity), Go Get It: "Bring the mindset of a champion." (ambition, ownership, hustle), Trip Obsessed: "Make magic in the marketplace." (customer/user focus), Build With Heart: "We care." (empathy for users, partners, communities), Stand For Safety: "Safety never stops.", See The Forest And The Trees: "Know the details that matter." (balancing big-picture and detail), One Uber: "Bet on something bigger." (cross-team collaboration), Great Minds Don't Think Alike: "Diversity makes us stronger.".

What kinds of questions does Uber ask?+

Uber's question bank spans 4 categories: Coding & Data Structures/Algorithms; System Design; Behavioral & Values Fit; Technical Project Deep-Dive (Bar Raiser round).

How reliable is this Uber interview playbook?+

This playbook is high confidence, compiled from 25 public sources, and last verified July 7, 2026. It describes one well-documented shape of Uber's interviews, not a guarantee of what any individual loop will look like.

Sources

Interviewing at Uber?

Add it as a Target Role and tailor your resume against the actual job description.

Add Uber as a Target Role