Uber interview notes, page 42 of 61

Large Enterprises

Most of these Uber write-ups come from Software Engineers (407), then Data Scientists (78) and Machine Learning Engineers (65). The most reported rounds are the technical phone screen (387), the system design round (95), the product sense round (46) and the onsite coding round (23).

609 interview notes · updated Aug 2026

Uber·Software Engineer·Online Assessment (OA)

Jun 2026

Uber SWE online assessment, one algorithmic problem centered on maximizing pipeline throughput under a budget constraint. Pretty clean problem once you see the binary search angle, but the edge cases in the predicate function are where people trip up.

You have a pipeline of services running in series. Each service has an initial throughput and a cost to scale it up. Given a total budget, find the maximum pipeline throughput you can achieve, where pipeline throughput is the minimum across all services.

“I went greedy first, kept throwing budget at whatever the current bottleneck was.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026

Uber SWE interview with a deceptively simple autocomplete problem. The prompt was basically one line, which meant the real test was how much you could unpack from almost nothing.

Given a list of store names, implement an autocomplete function that returns all stores whose names begin with a given input string.

“The prompt was genuinely short, like one sentence and a list of strings.”

View Post

Uber·Software Engineer·Onsite - Coding / Algorithms

Jun 2026

Uber coding round that was framed as OO Design rather than a pure algorithm problem. Just the one question but it went in a direction I wasn't fully prepared for.

Design a parking lot system using object-oriented principles.

“Went in expecting LeetCode-style problems and got hit with OO Design instead.”

View Post

Uber·Data Scientist·Technical Phone Screen

Jun 2026

Uber data scientist interview with a coding question that looked deceptively simple. The palindrome problem had more edge cases than I expected and I fumbled through a couple of them live.

Given a positive integer n, find the smallest integer strictly greater than n that is a palindrome (no leading zeros allowed).

“I started with the obvious cases and worked inward.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026

Uber SWE interview with a graph problem that looks like a classic shortest path but has a constraint that changes everything. Not a bad experience, just needed to think more carefully before jumping to Dijkstra.

Given a directed weighted graph of flights between cities, find the cheapest route from a source city to a destination city using at most K stops. Return -1 if no valid route exists.

“My first instinct was Dijkstra and I started going down that road before realizing the K-stops constraint breaks the usual greedy logic.”

View Post

Uber·Backend Engineer·Technical Phone Screen

Jun 2026

Uber backend interview that went deep on dynamic graph connectivity, specifically a variant of the rider-connection problem where you have to handle both link additions and deletions in a time-sorted event log. The problem was harder than I expected and the follow-up about block events basically invalidated the approach I'd been building toward.

You have a time-sorted log of events between riders: connect events (two riders shared a ride) and block events (a rider blocked another, severing that link and potentially splitting a connected component). Find the earliest timestamp at which all riders belong to a single component. Standard Union-Find won't work because it can't handle deletions. Walk through your approach, its time complexity, and the key invariant that makes it correct.

“This wrecked me a little.”

View Post

Uber·Machine Learning Engineer·Technical Phone Screen

Jun 2026

Did an ML round at Uber for an MLE role, got asked to design the restaurant recommendation system for Uber Eats. The interviewer turned out to have an econ/OR background and worked on matching, not recommendations, which made the whole thing feel off. Probably didn't pass.

How would you design a restaurant recommendation system for the Uber Eats homepage?

“The rough part wasn't the question itself, it was that the interviewer clearly wasn't coming from a recommendations background.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026

Uber SWE coding round with one algorithmic problem centered on interval processing. The problem was well-scoped but had enough edge cases to trip you up if you weren't careful about how simultaneous start/end events interact.

Given a list of courier working intervals [start, end) that may overlap, return a timeline broken into segments [segmentStart, segmentEnd, activeCount], where each segment represents a period of constant courier activity. Only emit segments where at least one courier is active, and treat all changes at the same timestamp as a single atomic event before computing the next segment.

“The core idea clicks fast: sweep line, collect all the events, sort them, walk through.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026

Uber coding interview with a grid-based problem that looks approachable until you realize the naive approach is way too slow. The question had enough layers to keep me busy for the whole session.

You're given a 2D grid where each cell is a robot, empty, or an obstacle (grid boundaries also count as obstacles). You're also given a 4-element distance array representing how far a target robot is from the nearest obstacle in each direction (left, top, bottom, right). Find all robots in the grid whose distances to the nearest obstacle in all four directions match that profile exactly.

“My first instinct was to just iterate over every robot cell and scan outward in four directions each time.”

View Post

Uber·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

PM interview at Uber focused on a product analytics and diagnosis problem around trip cancellations. Pretty standard product sense round but the question had enough depth to trip you up if you jumped straight to solutions.

Uber is seeing a spike in trip cancellations from riders. How would you investigate and address this?

“My first instinct was to go straight into fixes, which was the wrong move.”

View Post