real interview stories, told over a cup of tea ♡
Uber Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
42 results
- Building a Directory Tree and Traversing It with a Manual StackUber · Software Engineer · Technical Screen · Sep 2026Rejected
The interview lasted 45 minutes. We first went through my resume. I was asked about my most challenging project and the technology stack I normally use, and the interviewer introduced the work of the hiring group. The remaining half hour was for coding. Given a series of file paths, I needed to build a directory tree and find the full path of a file in that tree. Directory names could repeat, but…
- Matrix Swaps and Infrastructure DesignUber · Software Engineer · Senior+ · Onsite · Sep 2026
The author describes an Uber infrastructure-backend interview process with a phone screen and three virtual-onsite rounds. The screen asked for a valid sequence of adjacent swaps that arranges a matrix into alternating-direction sorted rows, followed by discussion of reducing the number of operations. The applicant had to create tests and found the time limit demanding. Onsite coding involved rep…
- 45 Min Coding Plus 15 Min Free-Form ML Design, Onsite Invite Next DayUber · Machine Learning Engineer · Technical Screen · Aug 2026In progress
The phone screen format was 45 min coding + 15 min design. For coding I got the high-frequency "find robot" problem. I discussed the brute force solution with the interviewer, then how to precompute the distances in all four directions to speed it up, and finally wrote the optimized version. The interviewer didn't provide any test cases in HackerRank and didn't ask me to write any either. I only…
- A Three-Level Robot Path OptimizationUber · Software Engineer · Senior+ · Technical Screen · Aug 2026
In a grid, a robot needs to move from a starting point to a destination. Each move consumes one unit of battery power. Charging cells are distributed throughout the grid, and when the robot reaches one, its battery is recharged to full. The task is to find an optimal path using the following priorities, compared lexicographically: Minimize the number of charging cells used. Minimize the maximum b…
- Four Onsite Rounds, All About the Follow-UpsUber · Software Engineer · Onsite · Aug 2026
Four rounds, questions weren't hard but the pace was really fast Let me lead with the conclusion: Uber's problems really aren't hard, but they move fast. 45 minutes a round, and the interviewer practically wants you to knock out the main problem in 15 minutes so there's a full half hour left for piling on requirements. It felt less like solving problems and more like sitting in a requirements rev…
- Tracking the Earliest Unrepeated VisitorUber · Software Engineer · Technical Screen · Aug 2026
An Uber phone-screen report describes a data-structure exercise for recording ID visits and retrieving the earliest ID seen exactly once. The task includes a defined result when no eligible ID remains and permits keeping the data in memory, with IDs ranging to roughly one million. The follow-up asks how to make queries constant time. The reported hint involves removing repeated IDs from the front…
- OA with a Delivery-Cost, Truck-Collision, and Org-Tree Broadcast ProblemUber · Software Engineer · Intern · Online Assessment · Jul 2026
OA Problem 1 There are n cities, each with a deliveryCharge value. Delivering from city i to city j can be costed in two ways: The cost is abs(deliveryCharge[i] - deliveryCharge[j]) If city j is city i's unique nearest city, the cost is 1 The distance between cities is defined as abs(deliveryCharge[i] - deliveryCharge[j]). Given a queries array where each entry is [Start, End], compute the minimu…
- Phone Screen, Onsite with Graph DB Design, Then SilenceUber · Software Engineer · Onsite · Jul 2026No response
Phone screen: similar to the Design Meeting Scheduler on hack2hire, but simpler. Onsite: coding 1 was serialization and deserialization of an n-ary tree. Coding 2 I really can't remember. The system design was about using a graph DB to store who can access which resources (this was role-related, not a general system design), how to migrate over from the existing DB, how to design the schema, scal…
- Uber Account Executive interview: vendor experience screenUber · Account Executive · HR Screen · Jul 2026
After applying through the website, I was shortlisted and had an initial HR screen. The questions focused on my client-facing experience and how I worked with vendors, including different alcohol vendors and what that looked like in practice. The round was average in difficulty. It was not overly technical, but it did require me to explain real-world vendor and stakeholder work. I did not receive…
- Uber Data Scientist interview: 17-question SQL and aptitude testUber · Data Scientist · Online Assessment · Jul 2026
My first step was a 60-minute test with 17 questions: two medium SQL questions and fifteen aptitude questions. The aptitude portion felt fairly straightforward, and I think I could have finished it in about half the allotted time. I used more of the clock on SQL because I did not fully solve one problem, then submitted what I had. The process did not continue after that test. The non-SQL portion…
- Uber Data Scientist interview: SQL and consumer fraud riskUber · Data Scientist · Technical Screen · Jul 2026Rejected
The interview was centered on risk. I worked through an SQL question and then a confusion-matrix-style question, and I felt technically comfortable with both. The problem came when the discussion moved to consumer fraud risk. I answered, but the reaction suggested that the way I framed the risk analysis and reasoning had not landed. That difference in how we saw the quality of the answer stayed w…
- Uber Operations Manager interview experienceUber · Operations Manager · Jul 2026
After a recruiter screen, I had a one-on-one with the hiring manager and then three business-style interviews built around presenting a case study. The process was long and draining because every round expected real output rather than just discussion. Communication was clear throughout. I did not receive an offer, but the process remained organized and professional, which made it easier to stay e…
- Uber Software Engineer interview: five coding rounds in almost a monthUber · Software Engineer · Technical Screen · Jul 2026Rejected
I completed the interview process but didn't pass. It involved five coding interviews over almost a month, which felt faster than I'd expected. All the questions focused on coding. I wondered whether the standard was aimed particularly at candidates closer to the new-grad track, since they seemed to engage broadly. I don't have much more detail about the individual questions to share. What I did…
- Uber Software Engineer interview: recursion, tree questions, and full onsite loopUber · Software Engineer · Technical Screen · Jul 2026
After a recruiter conversation, I moved quickly into coding interviews. Across two interviews, I had two DSA problems: a recursion-based string-manipulation task and a tree question. Both came with follow-up extensions, so each session became a continuing problem-solving stretch rather than one fixed prompt. Later, I had a loop-style onsite day with all interviews on the same day. The interviewer…
- Uber Software Engineer interview: three timed coding questionsUber · Software Engineer · Online Assessment · Jul 2026
My first major step was an online coding exam with medium-to-hard LeetCode-style questions. There were three questions, with 45 minutes for each one. I had previously tested myself for a fresher-level setup, so the structure did not completely blindside me, but the time pressure still mattered a lot. It tested DSA fundamentals and, honestly, how well I could manage my pace. I did not receive an o…
- Recruiter Outreach and a Pre-Drawn Architecture DiagramUber · Software Engineer · Senior+ · Onsite · May 2026Offer
A recruiter contacted me first, and I figured I'd give it a shot, since Uber had been sitting on my target list for quite a while. Coding: Ahead of the phone screen and the coding onsite rounds, I put most of my prep time into LeetCode problems that were tagged with the company. Python is my pick for coding interviews. The syntax is compact enough that I get time to finish the main problem and an…
- A Tournament-Ranking Question and the Interviewer's Wrong HintsUber · Software Engineer · Technical Screen · Apr 2026
The interviewer's tone was very friendly. For the second question though, I think it's genuinely hard to come up with if you haven't seen something like it before — the corner cases are rough. I went through about six months of interview experience posts and didn't see this question anywhere. It's not even in the LeetCode Uber tag. The problem: [1, 2, 3, 4, 5, 6, 7, 8] represents ranks, where a s…
- Five Onsite Rounds, One a Surprise Clustering QuestionUber · Data Scientist · Senior+ · Onsite · Apr 2026
Round 1: past project deep dive. Not much to say about this kind of subjective round. I feel like I explained it well, but that doesn't mean I won't still get rejected. Round 2, coding: we spent 25 minutes going over my resume. The coding question was: given an integer, find the next palindrome integer greater than it. I'd never seen this before. The question is pretty abstract — you can't even e…
- Missed the OA's Iterative-DFS Trick But Still AdvancedUber · Software Engineer · Technical Screen · Apr 2026In progress
Today's technical screen: 5-minute self-introduction, then 20 minutes of coding: Given a 2D grid with empty cells, robots, obstacles, and a target like [1, 1, 2, 2] — this represents each robot's distance to the nearest obstacle in the up, left, down, right directions respectively, indexed accordingly. Output a list of robot locations that fit this criteria. Then a 30-minute deep dive on one of m…
- QuadTree Screen That I Ended EarlyUber · Software Engineer · Technical Screen · Apr 2026Rejected
They asked me how to build a QuadTree. There's a similar problem on LeetCode (the original post referenced it in a garbled, obfuscated way, probably to dodge the forum's keyword filter), but the interview version wasn't limited to just 0s and 1s — the description given was pretty high-level, and I had to implement the data structure from scratch by hand. I'd solved this problem more than once, th…
- Two OA Questions in 90 MinutesUber · Software Engineer · Online Assessment · Apr 2026
90 minutes, two questions. Question 1: Balanced Numbers You're given a permutation array of 1 to N. For each length k from 1 to N, determine whether the k elements in the permutation whose values fall in the range 1 to k are exactly contiguous in the original array. Return a string of '1' and '0' indicating whether each k satisfies the condition. Question 2: Minimum Reversal You're given a direct…
- Withdrew After a Possible L5A-to-L4 DownlevelUber · Machine Learning Engineer · Senior+ · Technical Screen · Apr 2026Withdrew
I interviewed for a Sr MLE / MLE role. The whole process was pretty short — in the end, after HR indicated I might get downleveled from L5A to L4, I decided not to move forward, so this is basically a withdrawal report. The first round was mainly a project deep dive. It opened with self-introductions, then the interviewer asked me to walk through a recent representative project. I talked about a…
- Cart System Design Screen Plus BehavioralUber · Engineering Manager · Senior+ · Technical Screen · Mar 2026
I recently interviewed for a manager position at Uber. Overall the experience was pretty good — both interviewers were easy to talk to and felt pretty nice & chill (not quite what I expected from Uber based on my old stereotype, lol). Writing up the System Design question and what I think you need to prepare for it, as a reference for anyone else interviewing for something similar. 1) System Desi…
- An In-Place Coding Question and a Deep ETA Case StudyUber · Data Scientist · Technical Screen · Feb 2026
Part 1: Coding Given an integer array, move all zeros in the array to the front while keeping the relative order of all non-zero elements unchanged. Requirement: it must be done in-place. Part 2: Case Study Business scenario: Uber wants to evaluate the business value of lowering ETA (the estimated time for a driver to arrive at the pickup location). What metrics would you look at? From a business…
- Four Onsite Rounds, Rejected After System DesignUber · Software Engineer · Onsite · Feb 2026Rejected
Did the OA first, two questions. The first was a somewhat convoluted binary search problem (kind of like an elevator problem), and the second was a server throughput problem solved with a heap (at the time I only managed to write a recursive solution). After that was the tech screen. The interviewer gave a lock combination problem — find the minimum number of steps to unlock it, basically BFS. Th…
- Rejected in Both Full-Time and Intern LoopsUber · Data Scientist · Intern · Onsite · Feb 2026Rejected
I got rejected for both their full-time and intern positions — the intern process was rejected after the second (final) round, and the full-time process was rejected after the first round. I don't know what the interviewers were looking for; I felt like I answered every question, and communication went smoothly enough. For the full-time role, the first round jumped straight into a case study afte…
- A CDF Coding Question, Constant Interruptions, and a Second Round That Never HappenedUber · Data Scientist · Technical Screen · Jan 2026Rejected
The coding question was: given a PDF, compute the CDF. Then the case question was about designing an ETA system — what you need to consider. This was my first interview, and I found this interviewer's style was completely different from the paid mock interviews I'd done before. When I did mock interviews before, several people advised me not to think out loud while talking — better to take a minu…
- HackerRank OA Then a Tradeoff-Heavy Phone ScreenUber · Software Engineer · Technical Screen · Jan 2026
I finished the Uber OA and did the phone screen too, so sharing both. The OA was on HackerRank, camera required. First question: a Hard DP problem, a variant of a well-known Jump Game problem where the jump-step rule was changed to a prime-number condition. I got stuck for a bit but eventually worked it out. Second question: Pipeline Throughput, solved with binary search on the answer. You're giv…
- Solved the Dependency Graph Problem, Still Rejected for Not Flagging Edge CasesUber · Software Engineer · Technical Screen · Jan 2026Rejected
I finished the problem and ran a few test cases I wrote myself. A week later I got a "moving forward with other candidates" rejection. I had AI polish up the problem statement a bit: Package Build Order (dependency build order) Problem description (abstract version): The interviewer gave me an interface: — it returns the direct dependencies of a given package. Requirements: given a target package…
- A Graph Question in a Frontend HackerRank ScreenUber · Software Engineer · Technical Screen · Dec 2025
At first it was the usual back-and-forth introductions. The code was written on HackerRank, and the moment I heard the question I broke out in a sweat — since when does a frontend interview ask a graph question? Simply put, it was a flight ticket problem. Input: number of cities, [[departure city number, arrival city number, ticket price]...], and the maximum number of stops. Output: the lowest t…
