TheJobsMap
Uber Technologies logo

Uber Technologies interview questions

From 28 candidate accounts, updated Oct 12, 2026

Candidate accounts
28
Rounds on average
4.6
Fewest and most rounds
2 to 7
Open roles at Uber Technologies
1

How the loop works

Uber runs a highly standardised, named-round loop that candidates describe almost identically across geographies: a timed online assessment (CodeSignal, HackerRank or Codility), a screening or BPS coding call that acts as the elimination gate, then a same-day set of one-hour rounds with fixed labels - Algorithms & Data Structures, Depth in Specialization (production-quality machine coding), Design & Architecture on a new problem, Design & Architecture on a previously solved problem, and a Collaboration/Leadership or bar-raiser conversation with a manager. Recruiters brief candidates on the round names and send prep material in advance, so the loop is unusually predictable. The bar inside it is not, with several writers reporting rejections for readability, missed edge cases or a project story judged not to be at Uber scale. Non-engineering loops diverge sharply: product management runs a multi-hour take-home plus a group-style product case day with PM, engineer and UX-designer interviewers, and analytics roles pair SQL/Python screening with city-launch and marketplace case studies.

These 28 writeups cover software engineering, data & science, product management and other roles, India-heavy, some US and Europe. 23 of them were posted under a forum handle, so we could not verify the authors’ identities.

See open roles at Uber Technologies

Interview experiences at Uber Technologies

Senior Software Engineer (L5A)

Received an offer

Experienced. 5 rounds. Shared by Rajat Goyal on blog, 2024-05-01

  1. 1Coding BPSTechnicalA single medium-difficulty coding problem acting as the elimination gate. The author notes clearing it books all four remaining rounds regardless of later performance. Class structure and naming are graded alongside correctness.Covered: Data structures & algorithms, OOP
  2. 2Algorithms and Data StructuresTechnicalRoughly fifty minutes of problem solving after introductions. The author worked through a DP problem, a follow-up on it, and a third problem answered verbally without implementation.Covered: Dynamic programming, Data structures & algorithms
  3. 3Depth In SpecializationLow-level designA second coding round graded on production-readiness rather than algorithmic cleverness: single-responsibility classes, sensible method and variable names, readable structure.Covered: Low-level design, OOP, Testing
  4. 4Design and Architecture (New Problem)System designA greenfield design brief where the candidate clarifies requirements, estimates capacity, gives a high-level architecture and then drills into API and schema detail before discussing bottlenecks and scaling.Covered: System design, Scalability, API design, DBMS
  5. 5Collaboration and Leadership + Previously Solved ProblemHiring managerA manager-led seventy-five-minute session split between a deep replay of the candidate's own past architecture decisions and their hindsight on them, and questions on leading, resolving conflict and setting team norms.Covered: Past projects, Behavioral, Conflict handling

Senior Software Developer (L5A Senior I)

Received an offer

Experienced. 7 rounds. Shared by Alexey Kislitsin (aikikode) on blog, 2022-03-01

  1. 1Screening / first technicalPhone screenA one-hour algorithmic call at roughly medium difficulty, with the author stressing that talking through trade-offs before coding mattered as much as the final solution.Covered: Data structures & algorithms
  2. 2Coding - Algorithms & Data structuresTechnicalAnother medium-level puzzle, run in CodeSignal so the candidate can compile, run and debug during the interview.Covered: Data structures & algorithms
  3. 3Design & Architecture - Previously Solved ProblemSystem designAn architecture conversation about one of the candidate's own shipped projects: what problem it solved, why each decision was made, how it behaved in production.Covered: Past projects, System design
  4. 4Coding - Depth in specializationLow-level designA build-a-small-real-thing round rather than a puzzle, for example a class or library that aggregates statistics over a request stream.Covered: Low-level design, OOP
  5. 5Design & Architecture - New ProblemSystem designA classic whiteboard system-design brief on a virtual board.Covered: System design, Scalability
  6. 6Behavioral - Citizenship and CollaborationBehavioralFocused on teams and people rather than technology: how the candidate worked with others, what went wrong, what they learned.Covered: Behavioral, STAR stories, Conflict handling
  7. 7Bar raiserBar raiserA behavioural interview run by an engineer, drifting back and forth between technical decisions and the people side of them.Covered: Behavioral, Past projects

What Uber Technologies is hiring for now

1 open role in our index.

Most-posted roles

  • Groceries & Retail Junior Account Manager1

Top locations

  • Panama City1

Open roles at Uber Technologies

See all 1 roles

Uber Technologies interviews: FAQ

What is the interview process like at Uber Technologies?
Uber runs a highly standardised, named-round loop that candidates describe almost identically across geographies: a timed online assessment (CodeSignal, HackerRank or Codility), a screening or BPS coding call that acts as the elimination gate, then a same-day set of one-hour rounds with fixed labels - Algorithms & Data Structures, Depth in Specialization (production-quality machine coding), Design & Architecture on a new problem, Design & Architecture on a previously solved problem, and a Collaboration/Leadership or bar-raiser conversation with a manager. Recruiters brief candidates on the round names and send prep material in advance, so the loop is unusually predictable. The bar inside it is not, with several writers reporting rejections for readability, missed edge cases or a project story judged not to be at Uber scale. Non-engineering loops diverge sharply: product management runs a multi-hour take-home plus a group-style product case day with PM, engineer and UX-designer interviewers, and analytics roles pair SQL/Python screening with city-launch and marketplace case studies.
What topics does Uber Technologies test in interviews?
Commonly reported topics include Data structures & algorithms, Dynamic programming, Graphs, Trees, Arrays & strings, System design.

These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.