← Back to Directory

Uber interview notes, page 47 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·Technical Phone Screen

Jun 2026
Uber SWE interview with a twist on the classic Jump Game problem. Not the hardest session I've had but the prime number constraint threw me off more than I expected.
  • Solve a variant of the Jump Game problem where the only allowed step sizes are prime numbers.

“I'd seen the standard Jump Game before so my first instinct was to just reach for the greedy approach, which was wrong here.”

View Post

Uber·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Uber MLE interview with a grid traversal problem that had a few layers to it. Pretty standard coding round but the follow-ups kept coming and I wasn't fully ready for the space optimization part.
  • Given a 2D grid where cells are either traversable or blocked, write a function to count the number of connected regions (4-directional adjacency only).
  • Follow-up: instead of just counting the zones, return the sizes of all zones sorted in descending order.
  • Analyze the time and space complexity of your solution, then optimize it to use as little extra space as possible.

“Classic connected components problem, BFS or DFS both work fine.”

View Post

Uber·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Uber SWE interview focused on designing a rate limiter from scratch, with a bunch of follow-ups that escalated pretty fast into distributed systems territory. The core question seems straightforward but they really push you on the edges.
  • Design a rate limiter with an allow(user_id, timestamp) interface that enforces a sliding window policy of at most N requests per W seconds per user.
  • How would you extend the rate limiter to support multiple users with different limits, and also per-endpoint rules?
  • How would you make this rate limiter work in a distributed environment with multiple service instances behind a load balancer?

“This is the kind of question where you think you know it and then the follow-ups make you realize you only knew half of it.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE coding round with a question that's been circulating in other posts and apparently showed up in hack2hire too. Nothing shocking, but the follow-up added some complexity.
  • Implement a calculator that handles addition and subtraction.
  • Given the calculator you just built, add input validation to verify the string is a valid expression before processing it.

“Seen this one floating around in other posts so I wasn't totally blindsided.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE interview with a string manipulation problem. Pretty standard stuff but worth knowing the edge cases cold before you walk in.
  • Given two strings s and t of equal length, determine if they are isomorphic. That means every character in s maps to exactly one character in t, and no two characters in s map to the same character in t, while preserving order.

“Seemed easy at first and I jumped straight to using one hashmap.”

View Post

Uber·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
Uber MLE system design round, one big question that sprawled across basically every dimension of ML infrastructure you can think of. The kind of prompt where you finish and genuinely can't tell if you crushed it or missed the whole point.
  • Design a real-time system that tracks remaining ETA for every active driver across a city grid. Walk through GPS ingestion and partitioning, denoising and map-matching, ETA computation and updates, model selection and training, online feature computation using only the provided data, low-latency serving, monitoring and rollback, and offline plus online evaluation.

“This is a monster of a question.”

View Post

Uber·Data Scientist·Technical Phone Screen

Jun 2026
Uber DS interview that went deep on experiment design, like really deep. It was basically one long question about A/B testing assumptions and I was not fully prepared for how systematic they wanted me to be about it.
  • Walk through the core assumptions required for a valid online A/B test. For each assumption, explain what it means formally, give a realistic product scenario where it breaks down, describe how you'd detect the violation, and explain how you'd fix or redesign around it. They specifically wanted coverage of: randomization integrity and sample ratio mismatch, independence and interference like network effects or shared inventory, stable unit exposure and crossover or noncompliance, stationarity and novelty effects, metric logging bias and missingness, sequential peeking and error inflation, and heterogeneous treatment effects.

“This was the whole interview basically.”

View Post

Uber·Data Scientist·Technical Phone Screen

Jun 2026
Uber Data Scientist coding round, basically one array manipulation problem with a follow-up that tightened the constraints. Not the most grueling session but the edge cases will bite you if you're not careful.
  • Given an array, rotate it by k positions. Walk through your approach, then redo it under tighter memory constraints (O(1) extra space).

“First pass I just reached for a temp array and it worked fine, but then they asked me to do it without allocating extra space and I stalled a bit.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber coding round for a Software Engineer role. One algorithmic problem, simulation-heavy, not the kind of thing you can brute force your way through in 45 minutes without thinking carefully about the traversal logic first.
  • You have two arrays and a starting energy value K. For each possible start index, simulate moving forward through the layers: at each step you subtract the current layer's cost from your energy, and if energy goes negative you stop immediately. If your remaining energy meets or exceeds a threshold for that layer, you score a point and keep going, otherwise you stop. Return an array where each entry is the max points achievable starting from that index.

“The simulation part clicked fast but I kept second-guessing the termination conditions.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Product-sense style question for an Applied Scientist role at Uber. One question, but it had a lot of layers to it and the conversation went deep into metrics and experiment design.
  • On a food delivery platform, alcohol products have a lower order completion rate than non-alcohol products. What could explain this, how would you investigate it, and what would you recommend to improve it?

“I started with age verification as the obvious culprit and the interviewer just kind of nodded and waited, so I kept going.”

View Post