Uber

Updated · techinterview.org

Interview Process Overview

Uber’s interview process is fast-paced and practical, reflecting the company’s operational focus. Interviews emphasize real-world problem-solving, scalability, and ability to move quickly in ambiguous situations.

What to Expect

Recruiter Screen: Brief call about your experience and interest in Uber. Quick turnaround – Uber moves fast in hiring.

Technical Phone Screen (1-2 rounds): 45-minute coding interviews. Medium difficulty problems with focus on efficiency and clean code. Use HackerRank or CoderPad.

Onsite Interviews (4-5 rounds):

  • Coding Rounds (2-3): Algorithm problems focusing on graphs, dynamic programming, and optimization. Uber likes questions related to maps, routing, and location-based services.
  • System Design (1 round): Design scalable systems like ride-matching, surge pricing, or real-time location tracking. Focus on handling high throughput and low latency.
  • Behavioral (1 round): Questions about handling pressure, working in ambiguous situations, and driving results quickly. Uber values “bias for action” and “owner mentality.”

Common Question Topics

  • Graphs: Shortest path algorithms (Dijkstra), routing optimization. Expect to model a road network as a weighted graph and find the fastest route between two points; know when Dijkstra beats a plain BFS (weighted edges) and how the priority queue drives it. Interviewers often push on scaling to millions of nodes or adding constraints like live traffic weights.
  • Trees: Binary trees, BST operations, tree traversals. Drill inorder and level-order traversal and BST insert/search/delete until they are automatic. Common follow-ups ask you to validate a BST or find the lowest common ancestor, so practice carrying state up and down the recursion.
  • Arrays/Strings: Two pointers, sliding window, frequency counting. Reach for two pointers on sorted arrays and a sliding window for substring problems like longest substring without repeats. A hash map for frequency counting turns many O(n²) scans into a single O(n) pass.
  • Dynamic Programming: Optimization problems, memoization. Start from the brute-force recursion, spot the overlapping subproblems, then add memoization or a bottom-up table. Be ready to state the recurrence out loud and give the time and space cost before you write code.
  • System Design: Real-time systems, geospatial indexing, matching algorithms, surge pricing systems. For ride-matching you will partition the map with a geospatial index like geohash or a quadtree so a driver search only touches nearby cells. Interviewers probe how you hold latency down under bursty demand and how surge pricing reads real-time supply and demand per region.

Preparation Tips

  1. Study Graph Algorithms: Uber’s core business involves routing and location. Master Dijkstra’s, BFS, DFS, and graph representations.
  2. Focus on Scalability: Practice designing systems that handle millions of requests. Think about data partitioning and caching.
  3. Show Bias for Action: Demonstrate examples of moving quickly with incomplete information and delivering results under pressure.
  4. Use the Uber App: Understand rider and driver experiences deeply. Be ready to discuss improvements.
  5. Practice Time Complexity: Uber interviews often involve optimizing solutions from brute force to optimal.

Interview Culture

Uber values speed, execution, and results. The company operates in a highly competitive market and seeks people who can move fast, make data-driven decisions, and handle ambiguity. Demonstrate hustle, ownership, and customer focus.

Last Updated: February 2026

Adjacent Transport / Marketplace

  • Grab — Southeast Asia super-app

newsletter

What's actually being asked right now

Interview patterns & comp trends, straight to your inbox.

No spam. Unsubscribe anytime.

newsletter

What's actually being asked right now

Interview patterns & comp trends, straight to your inbox.

No spam. Unsubscribe anytime.

1972 Soviet postage stamp commemorating the Mars 2 probe

worth a read

Mars For The Rest of Us — a weekly-or-more deep dive on the technical side of Mars exploration: rocket propulsion, microbiology, mission architecture, and everything in between. Written by Maciej Ceglowski.

Read it on Substack
Scroll to Top