Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

30 stories

Likes earn the author +10 XP for the first 3 likes each day

UberSoftware EngineerSenior+
Sep 2026

Matrix Swaps and Infrastructure Design

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…

Onsite0
UberSoftware Engineer
Sep 2026

Building a Directory Tree and Traversing It with a Manual Stack

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…

RejectedTechnical Screen1
UberSoftware Engineer
Aug 2026

Tracking the Earliest Unrepeated Visitor

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…

Technical Screen0
UberSoftware EngineerSenior+
Aug 2026

A Three-Level Robot Path Optimization

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…

Technical Screen0
UberSoftware Engineer
Aug 2026

Four Onsite Rounds, All About the Follow-Ups

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…

Onsite0
UberSoftware Engineer
Jul 2026

Phone Screen, Onsite with Graph DB Design, Then Silence

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…

No responseOnsite0
UberSoftware EngineerIntern
Jul 2026

OA with a Delivery-Cost, Truck-Collision, and Org-Tree Broadcast Problem

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…

Online Assessment0
UberSoftware Engineer
Reported Jul 2026

Uber Software Engineer interview: recursion, tree questions, and full onsite loop

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…

Technical Screen0
UberSoftware Engineer
Reported Jul 2026

Uber Software Engineer interview: five coding rounds in almost a month

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…

RejectedTechnical Screen0
UberSoftware Engineer
Reported Jul 2026

Uber Software Engineer interview: three timed coding questions

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…

Online Assessment0
UberSoftware EngineerSenior+
Jun 2026

Phone Screen Then Four Onsite Rounds (Quadtree, Rate Limiter, System Design, Bar Raiser)

A premium story — unlock it to read the full loop.

OnsitePremium0
UberSoftware EngineerNew Grad
Jun 2026

Solved the Clothing-Size Sort Problem and Still Got Rejected

Locked — open it to unlock the full story with XP.

RejectedTechnical ScreenXP0
UberSoftware EngineerSenior+
Jun 2026

Rejected by the First Team, Then Matched to Another

A premium story — unlock it to read the full loop.

OfferOnsitePremium0
UberSoftware EngineerSenior+
Reported May 2026

Recruiter Outreach and a Pre-Drawn Architecture Diagram

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…

OfferOnsite0
UberSoftware Engineer
Apr 2026

Phone Screen, Four Onsite Rounds, Interviewers Replying to Work Messages

Locked — open it to unlock the full story with XP.

In progressOnsiteXP0
UberSoftware Engineer
Apr 2026

QuadTree Screen That I Ended Early

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…

RejectedTechnical Screen0
UberSoftware Engineer
Apr 2026

A Tournament-Ranking Question and the Interviewer's Wrong Hints

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…

Technical Screen0
UberSoftware Engineer
Apr 2026

Missed the OA's Iterative-DFS Trick But Still Advanced

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…

In progressTechnical Screen0
UberSoftware Engineer
Apr 2026

Two OA Questions in 90 Minutes

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…

Online Assessment0
UberSoftware Engineer
Mar 2026

OA, Phone Screen, Then a Four-Round Onsite

Locked — open it to unlock the full story with XP.

In progressOnsiteXP0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP