Katkat

Company

Uber interview questions

217 practice questions in the style of Uber's interviews, covering Behavioral & Leadership, Statistics & Math, Coding & Algorithms, Machine Learning, System Design, Data Manipulation (SQL/Python), Analytics & Experimentation, Software Engineering Fundamentals, ML System Design, Product / Decision Making, Product Design & Strategy.

Questions217

9 easy156 medium52 hard

Your progress0/217

Uber interview questions by the numbers

Last updated

Katkat has 217 Uber interview questions. The largest topics are Coding & Algorithms (53%), System Design (12%) and Analytics & Experimentation (10%). By difficulty: 4% easy, 72% medium and 24% hard. The most common round is Technical Screen (47%). Frequent concepts include System Design, Algorithms, Greedy and Data Structures.

Difficulty

  • Easy4% · 9
  • Medium72% · 156
  • Hard24% · 52

Interview rounds

  • Technical Screen47% · 102
  • Onsite41% · 88
  • Online Assessment12% · 26
  • Other0% · 1

Roles

  • Software Engineer63% · 137
  • Data Scientist25% · 54
  • Machine Learning Engineer10% · 21
  • Frontend Engineer1% · 2
  • Backend Engineer0% · 1

Frequent concepts

  • System Design6% · 13
  • Algorithms5% · 11
  • Greedy5% · 11
  • Data Structures5% · 10
  • Causal Inference4% · 9
  • Distributed Systems4% · 9

Showing 121–150 of 217 results

  • This problem tests your ability to navigate a 2D grid using backtracking and optimize dictionary lookups using a Trie data structure.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates graph algorithm proficiency and problem-modeling skills, specifically working with directed weighted graphs to optimize path cost under a constraint on intermediate stops.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests interval management and the ability to find a common free window across multiple disjoint sets of busy times while respecting daily working constraints.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • Assesses understanding of graph connectivity, temporal event processing, and dynamic graph data-structures for determining when a set of nodes becomes a single connected component.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates understanding of interval overlap counting, efficient use of ordered data structures for range events, tie-breaking logic, and robustness to numeric edge cases such as large coordinates and floating-point radii.

    UberSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This question evaluates the ability to model Euclidean-distance relations as a static connectivity graph and reason about the minimum number of activations needed to absorb all nodes, testing computational geometry and graph algorithms competency.

    UberSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This question evaluates understanding of directed graphs and rooted trees, the ability to reason about edge orientations and minimal reversals, and competency in traversal techniques and complexity analysis.

    UberSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This question evaluates string-based numeric manipulation and palindrome construction, including edge-case handling (all 9s, single-digit inputs, length changes), candidate generation and magnitude comparison of large numbers as strings, and carry propagation for fixed-length decimal palindromes.

    UberSoftware EngineerCoding & AlgorithmsOnline Assessment
  • Given a grid of robots, blockers and empty cells plus a query of four distances, return every robot whose distances to the nearest blocker or grid edge going up, down, left and right match the query exactly. Tests precise distance definitions, boundary handling and scaling past a per-robot scan.

    UberMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests spatial reasoning, multi-source Breadth-First Search (BFS) for distance mapping, and pattern matching within 2D grids.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates graph-traversal and modular arithmetic skills by requiring modeling a circular array as a state graph and determining reachability and minimum-distance jumps under wrap-around constraints.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's ability to analyze reachability and cycle behavior in array-based functional graphs, testing competency in array manipulation, traversal, loop detection, and runtime optimization within the Coding & Algorithms domain.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • Find the largest conversion factor obtainable between two currencies in a directed graph where rates multiply along each path. Handle parallel rates, unreachable targets, identical currencies, cycles, and floating-point tolerance under a finite-optimum guarantee.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Find the cheapest round-trip flight pair satisfying a minimum stay duration constraint in linear time with deterministic tie-breaking.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to efficiently process a stream or list of logs to identify the first log entry that appears exactly once, emphasizing the use of hash maps and ordered tracking.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests the ability to efficiently find the k nearest neighbors using a priority queue (max-heap) and custom sorting logic for tie-breaking.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates proficiency in numeric and string manipulation, algorithmic thinking, and edge-case reasoning related to palindromic number generation.

    UberData ScientistCoding & AlgorithmsOnsite
  • Diagnose and fix unclear delivery addresses in a marketplace delivery product. Covers root-cause analysis, risky-address detection, address validation, courier recovery, metrics, guardrails, and phased rollout.

    UberTechnical Program ManagerProduct / Decision MakingTechnical Screen
  • This question evaluates skills in defining a quantitative driver-backtracking metric from GPS and assignment logs, detecting and validating backtracking segments, and formulating constrained optimization models for dispatch and repositioning, drawing on statistics, operations research, and stochastic optimization.

    UberData ScientistStatistics & MathOnsite
  • This question evaluates a data scientist's competency in experimental design and statistical inference for A/B testing, covering hypothesis formulation, difference-in-proportions testing and confidence intervals, guardrail analysis, multiple-testing correction, interim alpha-spending approaches, and variance-reduction techniques such as CUPED.

    UberData ScientistStatistics & MathTechnical Screen
  • This problem tests your ability to identify and implement an efficient grouping mechanism using hash maps to categorize strings by a common canonical form.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to efficiently group strings by their character composition using hash maps or sorting techniques.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates the ability to parse and evaluate nested Lisp-like expressions, manage variable bindings and scope resolution, and detect malformed input and syntax errors.

    UberSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This problem tests the ability to design an A/B test for product improvements and address potential confounding factors like selection bias and spillover effects.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This question assesses the ability to design an end-to-end ranking system for a food delivery platform, focusing on objective formulation, feature selection, and the trade-offs between relevance and business constraints.

    UberData ScientistMachine LearningTechnical Screen
  • This problem tests the ability to design an end-to-end machine learning system for predicting ride arrival times, focusing on feature selection, model architecture, and evaluation strategies.

    UberData ScientistMachine LearningTechnical Screen
  • An Uber Machine Learning Engineer technical-screen question on derivative-free 1D convex optimization: minimize a black-box convex function on a closed interval using only function evaluations. It tests method selection (golden-section vs ternary search), stopping criteria and tolerances, function-evaluation and time/space complexity analysis, and robust handling of flat regions, boundary optima, noisy evaluations, and numerical precision.

    UberMachine Learning EngineerMachine LearningTechnical Screen
  • This question evaluates proficiency in grid-based string search, traversal techniques (fixed-direction scanning versus flexible-path exploration), algorithm design including backtracking/DFS, and the ability to analyze time and space complexity while accounting for redundancy and edge cases.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding and implementation of contrastive representation learning concepts—specifically similarity matrices, symmetric image-text contrastive loss, normalization, temperature scaling, and label construction—testing competency in building losses for embedding alignment in the Machine Learning domain.

    UberMachine Learning EngineerMachine LearningTechnical Screen
  • This problem tests your ability to combine a Least Recently Used (LRU) cache mechanism with a greedy strategy for geometric optimization in seat assignments.

    UberSoftware EngineerCoding & AlgorithmsOnsite

Uber interview experiences

All 42 →
  • Building a Directory Tree and Traversing It with a Manual StackUber · Software Engineer · Technical Screen · Sep 2026
    Rejected

    The interview lasted 45 minutes. We first went through my resume. I was asked about my most challenging project and the technology stack I normally use, and the interviewer introduced the work of the hiring group. The remaining half hour was for coding. Given a series of file paths, I needed to build a directory tree and find the full path of a file in that tree. Directory names could repeat, but…

  • Matrix Swaps and Infrastructure DesignUber · Software Engineer · Senior+ · Onsite · Sep 2026

    The author describes an Uber infrastructure-backend interview process with a phone screen and three virtual-onsite rounds. The screen asked for a valid sequence of adjacent swaps that arranges a matrix into alternating-direction sorted rows, followed by discussion of reducing the number of operations. The applicant had to create tests and found the time limit demanding. Onsite coding involved rep…

  • 45 Min Coding Plus 15 Min Free-Form ML Design, Onsite Invite Next DayUber · Machine Learning Engineer · Technical Screen · Aug 2026
    In progress

    The phone screen format was 45 min coding + 15 min design. For coding I got the high-frequency "find robot" problem. I discussed the brute force solution with the interviewer, then how to precompute the distances in all four directions to speed it up, and finally wrote the optimized version. The interviewer didn't provide any test cases in HackerRank and didn't ask me to write any either. I only…

  • A Three-Level Robot Path OptimizationUber · Software Engineer · Senior+ · Technical Screen · Aug 2026

    In a grid, a robot needs to move from a starting point to a destination. Each move consumes one unit of battery power. Charging cells are distributed throughout the grid, and when the robot reaches one, its battery is recharged to full. The task is to find an optimal path using the following priorities, compared lexicographically: Minimize the number of charging cells used. Minimize the maximum b…

  • Four Onsite Rounds, All About the Follow-UpsUber · Software Engineer · Onsite · Aug 2026

    Four rounds, questions weren't hard but the pace was really fast Let me lead with the conclusion: Uber's problems really aren't hard, but they move fast. 45 minutes a round, and the interviewer practically wants you to knock out the main problem in 15 minutes so there's a full half hour left for piling on requirements. It felt less like solving problems and more like sitting in a requirements rev…

More companies