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 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
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
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
UberSoftware Engineer
Jan 2026

A Pipeline Throughput OA, Then Radio Silence

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

No responseOnline AssessmentXP0
UberSoftware Engineer
Dec 2025

A Graph Question in a Frontend HackerRank Screen

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…

Technical Screen0
UberSoftware EngineerIntern
Dec 2025

PhD ML Intern OA, Coding, ML Round and Team Match

Sharing my process from December last year (2025) to January this year. Background: PhD, applied for the SDE PhD ML Intern role. Timeline: December: OA December: one coding interview round January: one ML interview round After that we talked about team match OA: I don't remember the exact problems, but the difficulty was low. They were basically all easy. Coding: The classic meeting rooms problem…

Technical Screen0
UberSoftware Engineer
Sep 2025

An OA With a Hand-Coded Tetris Fill Problem

I honestly don't remember the first two questions anymore, but they were both very easy, and it was explicitly stated that you didn't need to worry about complexity — brute force was totally fine. Even a rusty old-timer like me, who hasn't been grinding LeetCode for years, only spent 8 minutes total on those two combined. The third question was something I'd never seen before. It's similar to Tet…

Online Assessment0
UberSoftware Engineer
Sep 2025

a Candy-Crush Matrix and a Fruit-Pair Sliding Window on the OA

Questions 1 and 2 were easy, two array questions. Question 3 was kind of like a match-three game — a matrix where different numbers represent different colors. If a cell has two neighbors (up, down, left, or right) that are the same color as it, they explode and get cleared. After the whole matrix finishes clearing, the cells that weren't cleared fall down. Empty cells are represented by 0. Retur…

Online Assessment0
UberSoftware Engineer
Sep 2025

Meeting Scheduler Follow-ups, Paxos/Raft BQ, and a Driver HeatMap System Design

Technical Screen: The interviewer tested an algorithm problem (the name was written in an obscured/garbled way in the original post), with a follow-up asking for a simple multithreading variation. Virtual Onsite: Algorithm round: one of the interviewers tested something pretty similar to the earlier problem, with a follow-up about not passing time in as an argument. BQ round, with the hiring mana…

OfferOnsite0

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