← Back to Directory

Uber interview notes, page 41 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 that went sideways on the second coding problem. The interviewer's hint to ignore odd-length inputs turned out to be kind of useless once you hit recursive subproblems, and I ran out of time going down the iterative path.
  • Given a tournament bracket where players compete in sequence, generate an input arrangement such that players with lower rank numbers are always eliminated later than players with higher rank numbers. This is a variant of the 'earliest and latest rounds' problem without the power-of-two constraint on input size.

“I asked if iterative bottom-up was fine and the interviewer said yes, but then casually mentioned recursion would be much simpler.”

View Post

Uber·Frontend Engineer·Onsite - System Design / Architecture

Jun 2026
Virtual onsite at Uber for a frontend engineer role, and the main thing they threw at me was a system design question about building Google Calendar. Not what I expected going in.
  • Design Google Calendar as a frontend system.

“This is a meaty one if you've never prepped frontend system design specifically.”

View Post

Uber·Technical Program Manager·Onsite - Product Sense / Strategy

Jun 2026
Uber TPM interview that was basically a deep-dive case on delivery failures. The whole thing was structured around one scenario but they kept peeling back layers with follow-ups, so it felt more like four or five questions dressed up as one.
  • A customer doesn't receive their delivery because the address was unclear. Walk through how you'd diagnose the root cause, prioritize fixes, and improve the experience for both customers and couriers.
  • How would you detect that an address is risky before the customer even completes checkout?
  • Walk me through how you'd design the courier recovery flow when they're already on-site and can't complete the delivery.
  • What data would you capture from successful deliveries to help future couriers at the same location?
  • How do you avoid degrading the checkout experience for the majority of users who have perfectly normal addresses?

“This is the kind of question that looks like one thing but is actually five things.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber phone screen for a SWE role, basically one algorithmic problem the whole time. Classic sliding window stuff but the dual-deque angle tripped me up a bit.
  • Given an integer array and a limit value, find the length of the longest contiguous subarray where the absolute difference between any two elements is at most the given limit.

“I knew sliding window was the right direction but fumbled on how to track min and max efficiently inside the window.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber coding round for a software engineer role. The problem was a twist on the classic meeting rooms question, asking for per-interval room counts instead of just the peak. Felt manageable once I saw the pattern, but the output format tripped me up at first.
  • Given a list of meetings as [start, end) intervals, output the number of rooms simultaneously in use for each unit time interval or each distinct timestamp in a sweep line.

“I recognized the meeting rooms problem pretty quickly but then stalled on what they actually wanted back.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE coding round, one question that apparently shows up constantly on 1point3acres. Not much else to say about the setup.
  • LeetCode 1053 (Previous Permutation With One Swap): given an array of positive integers, return the lexicographically largest permutation that is smaller than the given array, after exactly one swap. If no such permutation exists, return the original array.

“High-frequency question apparently, which made me more nervous than I should've been.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Phone screen for a software engineer role at Uber. Just one coding problem, Word Search.
  • Implement a Word Search algorithm: given a 2D grid of characters, determine whether a given word exists in the grid by searching horizontally, vertically, or diagonally through adjacent cells.

“Classic backtracking problem.”

View Post

Uber·Software Engineer·Technical Phone Screen

Jun 2026
Uber SWE coding round with a dynamic programming problem that looked deceptively simple but had a weird prime number twist that slowed me down more than I expected.
  • Given an integer n, you start at step 0 and want to reach step n exactly. Each move lets you jump exactly 1 step, or any prime number of steps whose decimal representation ends in the digit 3 (e.g. 3, 13, 23, 43). Count the distinct jump sequences to reach step n, returning the result modulo 1,000,000,007. Assume n can be up to 100,000.

“The DP structure itself wasn't the hard part, that clicked pretty fast.”

View Post

Uber·Data Scientist·Onsite - Product Sense / Strategy

Jun 2026
Uber data scientist interview with a pretty gnarly operations/leadership case about a broken candidate funnel. The question was more product-strategy-meets-program-management than anything I expected for a DS role, and I spent way too long on the metrics side before realizing they wanted concrete ownership and governance answers too.
  • You run a program where candidates complete paperwork first, then must take a specific qualifying action. Most drop off after the paperwork and never take that action. Given a 14-day deadline and limited reviewer capacity, how would you: diagnose the top drop-off causes within a week, redesign incentives or process to get 60%+ of paperwork-complete candidates to finish the qualifying action, protect against low-quality gaming of that action, and set up clear ownership and escalation paths across teams?

“This one sprawled in a way I wasn't ready for.”

View Post

Uber·Software Engineer·Hiring Manager Screen

Jun 2026
Uber SWE onsite hiring manager round, roughly 60-75 minutes split between a project deep-dive and structured behavioral questions. The bar for senior and above is clearly not just 'I shipped a thing' but whether you can show cross-functional influence and real business impact.
  • Walk me through a project from your resume: the architecture, the key decisions you made, your specific contributions, and what the measurable outcomes were.
  • What parts of that project did you not own, and who did?
  • Looking back, what would you have done differently on that project?
  • How did you measure success on that project, and what was the baseline before you started?
  • How did you handle the trade-off between competing priorities or constraints during the project?
  • Tell me about a time you disagreed with your manager or a cross-functional partner like a PM or designer. How did it get resolved?
  • Describe the time you had the most impact on your team.
  • Tell me about your current team's scope, how it's structured, and what metrics you're responsible for.
  • How have you mentored someone on your team, and how did you approach setting direction or a roadmap for others?
  • How did you manage a situation where you needed to resolve conflict across teams you had no direct authority over?

“This is the centerpiece of the round and I did not treat it seriously enough until I heard from people who failed it.”

View Post