Interview Experiences

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

Share yours, earn XP

59 stories

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

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
UberData ScientistSenior+
Apr 2026

Five Onsite Rounds, One a Surprise Clustering Question

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…

Onsite0
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
UberData ScientistNew Grad
Apr 2026

Two Rounds on Marketplace Experimentation, Then a Rejection

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

RejectedTechnical ScreenXP0
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
UberData ScientistNew Grad
Mar 2026

Econ PhD, Two Phone Screens, Then a Verbal Offer

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

OfferOnsiteXP0
UberSoftware Engineer
Mar 2026

OA, Phone Screen, Then a Four-Round Onsite

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

In progressOnsiteXP0
UberEngineering ManagerSenior+
Mar 2026

Cart System Design Screen Plus Behavioral

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…

Technical Screen0
UberData ScientistNew Grad
Feb 2026

Econ PhD Track, Phone Screens to a Three-Round Onsite

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

OfferOnsiteXP0
UberSoftware Engineer
Feb 2026

Four Onsite Rounds, Rejected After System Design

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…

RejectedOnsite0
UberData ScientistIntern
Feb 2026

Rejected in Both Full-Time and Intern Loops

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…

RejectedOnsite0
UberData Scientist
Feb 2026

Rejected After a Round Full of Interruptions

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

RejectedTechnical ScreenXP0
UberData Scientist
Feb 2026

An In-Place Coding Question and a Deep ETA Case Study

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…

Technical Screen0
UberSoftware Engineer
Jan 2026

HackerRank OA Then a Tradeoff-Heavy Phone Screen

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…

Technical Screen0
UberData Scientist
Jan 2026

A Move-Zeroes Coding Question and an ETA Case Study

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

Technical ScreenXP0
UberSoftware Engineer
Jan 2026

Solved the Dependency Graph Problem, Still Rejected for Not Flagging Edge Cases

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…

RejectedTechnical Screen0
UberSoftware Engineer
Jan 2026

Two Weeks of Recruiter Silence After the Onsite

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

No responseOnsiteXP0
UberData Scientist
Jan 2026

A Move-Zeros Coding Problem and an ETA Business Case Study

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

Technical ScreenXP0

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