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 91–120 of 217 results

  • This question evaluates a candidate's ability to design real-time distributed systems for geospatial aggregation, covering skills in spatial partitioning, high-throughput streaming ingestion, low-latency cell counting, WebSocket-based client updates, and top-K ranking within a fault-tolerant multi-region architecture.

    UberSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's competency in real-time ML system design, covering streaming data ingestion, GPS noise handling and denoising, online feature computation, low-latency model serving, and operational monitoring.

    UberMachine Learning EngineerML System DesignOnsite
  • A system design interview question asking you to design the data flow behind a food delivery app's restaurant list for a customer's delivery address. It tests geographic indexing of delivery areas, propagating restaurant status and delivery-time changes, read-path latency, caching, and freshness trade-offs.

    UberSoftware EngineerSystem DesignOnsite
  • This question evaluates ability to design efficient in-memory data structures for frequency tracking, including handling recency-based tie-breaking, memory bounds under churn, and concurrency implications.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • Design top-K tracker with linked lists evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Determine Sample Size for Promotion Campaign A/B Test states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • Practice a Uber coding interview problem focused on determine whether a word exists in a character grid. The prompt emphasizes edge cases, clean implementation, and verifiable test behavior without revealing the solution.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates algorithmic reasoning about permutations and contiguous subarray properties, testing skills in array manipulation, positional reasoning, combinatorial insight, and complexity-aware algorithm design within the Coding & Algorithms domain.

    UberSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This question evaluates a candidate's competency in designing comprehensive test plans and test-driven development workflows for grid-based word search algorithms, covering edge-case identification, input normalization, path validity, and performance/stress considerations within software testing and algorithmic reasoning.

    UberSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design a string format for rooted N-ary trees and implement serialize and deserialize so the decoded tree has the same values, shape and child order. It tests unambiguous encoding of variable child counts, linear-time parsing, iterative handling of very deep trees, and validation of malformed input.

    UberSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates a data scientist's skills in causal inference, experimental design, and marketplace analytics, including understanding of confounding, selection bias, interference, and the distinction between correlation and causation.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This problem tests your ability to design an A/B test for a two-sided marketplace, focusing on network effects, metric selection, and identifying potential interference between treatment and control groups.

    UberData ScientistAnalytics & ExperimentationOnsite
  • This question tests the ability to design an A/B test for promotions in a two-sided marketplace, focusing on identifying interference (network effects) and selecting appropriate metrics to measure causal impact.

    UberData ScientistMachine LearningTechnical Screen
  • Uber data scientist analytics prompt on evaluating a rider-incentive program, covering experiment design, rider and driver metrics, matching quality, ROI, marketplace externalities, spillovers, and guardrails.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to design an experiment for a marketplace feature and evaluate its impact on key business metrics like conversion, frequency, and total contribution margin.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to design an evaluation framework for a new feature in a two-sided marketplace while accounting for spillover effects and metrics that represent different stakeholder interests.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This problem tests your ability to parse and evaluate mathematical expressions involving integers, addition, subtraction, multiplication, division, and parentheses using stacks or recursion.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This question tests the ability to design an experiment that isolates the causal impact of reduced ETA on user retention and to translate these metrics into business value.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a data scientist's competence in causal inference and identification strategies for estimating promotion effects from observational longitudinal data, emphasizing challenges such as staggered rollout, interference (spillovers), seasonality, and uncertainty quantification.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to design an experimentation framework for a two-sided marketplace, specifically addressing interference between supply and demand and selecting appropriate success metrics.

    UberData ScientistAnalytics & ExperimentationOnsite
  • This question evaluates understanding of causal inference, product-metrics analysis, experimental design, and statistical hypothesis testing (including two-sample t-tests) as applied to operational problems in a marketplace.

    UberMachine Learning EngineerMachine LearningTechnical Screen
  • This question evaluates proficiency in experimental design, causal inference, and statistical diagnostics for A/B testing, covering competencies such as randomization integrity, SUTVA/interference, noncompliance, time-varying effects, metric missingness, sequential testing, and heterogeneous treatment effects.

    UberData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a candidate's competence in handling interval-based scheduling problems, specifically managing interval data and performing efficient searches within sorted bookings to detect potential overlaps.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • This question tests the ability to optimize searches in a sorted binary matrix by minimizing expensive API calls through efficient traversal techniques.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding of graph connectivity and temporal event processing, examining how pairwise interactions over time can merge components into a single connected set.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding of binary search tree properties, ordered data retrieval, and algorithmic efficiency in locating the k-th smallest element.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement an algorithm to identify all robots in a grid whose four-directional distances to the nearest obstacle or grid boundary match a target query.

    UberMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates proficiency in zero-order optimization and algorithm design, focusing on reasoning about convexity and unimodality when only function evaluations are available.

    UberMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates array manipulation and algorithmic problem-solving skills across two tasks: enforcing bounded value ranges within contiguous subarrays and identifying largest uniform square regions in binary matrices, exercising concepts such as range-tracking, efficient data structures, and dynamic programming.

    UberSoftware EngineerCoding & AlgorithmsOnsite
  • Find a path in a grid from start to target that lexicographically minimizes charging stations used, peak battery segment length, total moves, and breaks ties by flattened cell indices.

    UberSoftware EngineerCoding & AlgorithmsTechnical Screen

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