← Back to Directory

Uber interview notes, page 50 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·Onsite - System Design / Architecture

Jun 2026
System design round at Uber for a software engineering role, focused entirely on building an internal driver queue service for pickup zones like airports. Dense question with a lot of moving parts and I'm not sure I covered everything they wanted.
  • Design an internal service that manages a driver queue for each pickup zone (like an airport staging lot). Drivers join the queue when they enter the area and get removed when they leave, go offline, or become ineligible. Internal services should be able to query the queue and see driver ordering. Cover API design, data modeling, event ingestion, queue ordering rules, consistency, scalability, fault tolerance, and observability.

“This is a big question and I burned probably 10 minutes just trying to scope it before drawing anything.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE coding round, one algorithmic question the whole time. Not a brutal session but the problem had a specific twist that I almost missed.
  • Given a 2D character matrix and a target word, check whether the word appears in the grid as a straight line. You can move in any of 8 directions (horizontal, vertical, or diagonal) but once you choose a starting cell and a direction, you must go straight without turning.

“My first instinct was to reach for the classic backtracking word search approach and I started explaining it before realizing they said no turning.”

View Post

Uber·Product Manager·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Uber for a PM role. Just one question but it had some weight to it.
  • Tell me about a time you failed to pitch something to leadership.

“I had a story ready but it was too clean.”

View Post

Uber·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Short Uber product question about cash payments in markets where that's the norm. Not much to report on the interview itself, just the one question.
  • Should Uber support cash payments in markets where users strongly prefer it over digital payments?

“This is actually a pretty interesting product strategy question if you dig into it.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE interview with a tree-based palindrome pairs problem. The algorithmic depth here was real, not just a standard leetcode warmup. Came away thinking I should practice iterative DFS more because the call-stack constraint was the part that nearly tripped me up.
  • Given a tree where each node holds a single lowercase character, count the number of node pairs whose path characters can be rearranged into a palindrome. N is large enough that a naive recursive DFS will blow the call stack.

“The palindrome condition clicked pretty fast for me, at most one character with odd frequency, so you can encode a path as a 26-bit XOR mask.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber coding round with a dynamic programming problem that looks straightforward until you actually think about what jumps are valid. The prime-ending-in-3 constraint is the kind of thing that trips you up if you don't slow down and enumerate your options first.
  • You have an integer array and start at index 0. At each position you can jump forward either 1 step or X steps, where X is a prime number whose last digit is 3 (so 3, 13, 23, 43, and so on). Each cell holds a value that can be positive or negative. Find the maximum sum you can accumulate by the time you reach the last index.

“My first instinct was just standard DP, which is right, but I fumbled the setup because I didn't precompute the valid primes ending in 3 before writing the recurrence.”

View Post

Uber·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Uber system design round for a software engineer role, one question the whole time: design a parking garage. Sounds almost too simple at first, but they pushed hard on concurrency and pricing logic.
  • Design an object-oriented model for a multi-level parking garage that supports multiple vehicle types, different spot types, vehicle entry and exit flows, ticket and payment handling, spot availability queries, and concurrent access.

“I started with the class hierarchy and got a bit too deep into vehicle subclasses before touching the spot assignment logic, which I think was the wrong order.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE coding round, one algorithmic question on squared sorted arrays. Pretty standard stuff but the two-pointer variant tripped me up more than I expected.
  • Given a sorted array of integers (possibly including negatives), return a new array of the squared values in non-decreasing order.

“I jumped straight to the sort-after-squaring approach because my brain went blank on anything cleverer.”

View Post

Uber·Data Scientist·Technical Phone Screen

Jun 2026
Summer internship interview for a Data Scientist role at Uber. Two meaty questions, one product case and one safety analysis, both with a lot of moving parts. Felt like they were testing whether you could hold a whole system in your head at once.
  • Propose a new or significantly improved feature for the Uber app (rider-facing or driver-facing). Walk through the target user and pain point, how the feature would change behavior, your north-star and success metrics, the tradeoffs across rider experience, driver experience, safety, and revenue, and how you'd design an experiment to test it including randomization unit, duration, power considerations, and handling of marketplace spillovers.
  • You're shown a line chart where a city's monthly accident rate (accidents per 100,000 completed trips) rises sharply from June through November and then drops quickly. How do you analyze this? Cover how you'd validate the metric's numerator and denominator, what hypotheses you'd consider, what internal and external data you'd pull, how you'd separate a real safety change from a reporting artifact, and what statistical or causal methods you'd apply.

“This is a beast of a question.”

View Post

Uber·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Uber MLE round with a combinatorics-heavy coding problem. The question had enough edge cases to make you second-guess yourself the whole way through.
  • Given a list of intervals, count the number of unordered triplets (i, j, k) such that all three intervals are pairwise non-overlapping.

“The first thing I fumbled was not asking whether endpoints touching counts as overlapping.”

View Post