← Back to Directory

Uber

Large Enterprises

Most of these Uber write-ups come from Software Engineers (214), then Machine Learning Engineers (33) and Data Scientists (6). The most reported rounds are the technical phone screen (193), the system design round (44), the onsite coding round (9) and the behavioral / leadership round (7).

263 interview notes · updated Jun 2026

Uber·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Uber system design round for a software engineer role. The main prompt was designing the search component for Uber Eats, which spawned a bunch of follow-ups I wasn't fully prepared for, including having to design a metric monitoring system on top of it.
  • Design the search component for Uber Eats. How would you architect it end to end?
  • How would you design a metric monitoring system for the Uber Eats search component you just described?

“Started with the obvious stuff, indexing restaurants and dishes, ranking by relevance and distance.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE interview with a recursion-heavy algorithm problem that I tangled myself up in by going iterative when I shouldn't have. The interviewer's hint to ignore odd-n cases turned out to be a trap in disguise since recursive subproblems can produce odd sizes anyway.
  • Given a tournament bracket where players compete in rounds, generate an initial arrangement of players such that those with smaller rank numbers are always eliminated later than those with larger rank numbers. This is a variant of the earliest/latest rounds problem without the power-of-two constraint on the number of players.

“Asked if I could do it bottom-up iteratively and the interviewer said sure, but recursion is simpler.”

View Post

Uber·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Uber coding round, graph problem that looks clean on the surface but has a few ways to go wrong. Nothing too surprising if you've done graph traversal before, but the sorting requirement at the end is easy to forget under pressure.
  • Given a directed graph, find all nodes from which every possible path eventually leads to a terminal node (a node with no outgoing edges). Return a sorted list of these safe nodes.

“I went with DFS and three-color marking.”

View Post

Uber·Software Engineer·Online Assessment (OA)

Jun 2026
Took an OA for a Software Engineer role at Uber and got tripped up on a string/palindrome problem that needed a more optimal solution than what I could come up with under pressure. TLE'd on some cases and now I'm just sitting here hoping it doesn't tank my chances.
  • Given a string, compute the total cost of converting every possible substring into a palindrome. For example, for the string 'abc', the substrings 'ab', 'bc', and 'abc' each cost 1 to convert, giving a total cost of 3.

“I got the brute force working fine, enumerate all substrings, compute the cost for each, sum it up.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE coding round, pretty much one problem the whole time. Classic backtracking question but there's more to it than you'd think once they start asking follow-ups.
  • Given a string of digits (each between 2 and 9), return all possible letter combinations that the digits could represent on a phone keypad.

“I went straight to backtracking and that was the right call.”

View Post

Uber·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Uber MLE interview with a graph/BFS problem that looks deceptively straightforward until you actually try to implement it efficiently. Not the worst experience but definitely left me second-guessing my approach the whole way through.
  • Given an array of bus routes where each route loops forever, find the minimum number of buses you need to take to get from a source stop to a target stop. Return -1 if it's impossible.

“My first instinct was plain BFS on stops, which is wrong because the search space explodes.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Went through a technical phone screen for a software engineer role at Uber. Two coding questions, one pretty standard and one that threw me off more than I expected.
  • Solve a coding problem involving algorithms or data structures (first question).
  • Solve a second coding problem (title obscured by the original poster).

“Felt okay about this one.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber coding screen for a software engineer role. One algorithmic problem, bit manipulation flavored, the kind that looks like a math puzzle until you realize it isn't.
  • Given a positive integer n, you can add or subtract any power of 2 in a single operation. What is the minimum number of operations needed to reduce n to zero?

“My first instinct was greedy, just keep subtracting the largest power of 2 that fits.”

View Post

Uber·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Uber ML engineer screen, one coding question the whole time. It was a text generation problem that looked simple on the surface but had enough edge cases to trip you up if you weren't careful about how you built the frequency map.
  • Build a two-part text generation system: first a function that builds a word transition frequency map from a corpus, then a function that generates text by greedily picking the highest-frequency next word at each step.

“The frequency map part was fine, tokenize on whitespace, strip punctuation, nested dict.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE coding round, one main algorithm problem with a bunch of follow-ups tacked on. The core question wasn't too bad but the interviewer kept pushing after the solution was done, which is where things got more interesting.
  • Given plain-text ride-sharing logs (each entry has a timestamp and indicates that user A shared a ride with user B) and a list of all users, find the earliest timestamp at which every user becomes connected.
  • How would you modify your solution if the log file contained more than one type of log entry, not just ride-sharing events?
  • What is the approximate time complexity of your solution?

“Used Union Find, which felt like the right call and the interviewer seemed fine with it.”

View Post

Uber interview guides

Online Assessment

18 Uber OA Reports 2026: Real SWE Questions & Repeats

Data Scientist

What to Expect in a Junior Uber Data Scientist Interview: Geo Experiments and Marketplace Analytics

Data Scientist

Uber Senior Data Scientist Interview: Causal Inference, Noncompliance and Spillover Effects

Product Manager

Uber Product Manager Interview 2026: A Real Accessibility Product Case

Product Manager

How Uber Tests Senior Product Managers: A Ride Cancellation Product Sense Case

Uber interview FAQ

What rounds are in the Uber interview?

Candidates most often report a technical phone screen (193 write-ups), a system design round (44), an onsite coding round (9) and a behavioral / leadership round (7).

What does the Uber technical phone screen cover?

Across 193 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (201 questions), Technical Trade-offs (102) and System Design (38).

What is asked in the Uber system design round?

Across 44 system design write-ups, the most tagged question topics are System Design (91 questions), Technical Trade-offs (76) and Data Modeling (40).

Uber interview guides by role

214 notes

Uber Software Engineer interview questions

33 notes

Uber Machine Learning Engineer interview questions