Interview Experiences

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

Share yours, earn XP

53 stories

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

UberData ScientistSenior+
Dec 2025

Diff-in-Diff, Switchback Design, and a Causal Inference Deep Dive

Sharing an interview. I'm guessing I failed. Uber Staff Scientist. Coding + experimentation The first part was data manipulation. I was given a pandas DataFrame and had to convert a column's type from string to int. There was a missing value that needed to be imputed using a simple average. After those two steps, I had to compute a diff-in-diff. The experimentation part was pretty relaxed. He ask…

Technical Screen0
UberData ScientistSenior+
Nov 2025

Two Brutal Phone Rounds on Airport Supply and Demand

Overall impression: this one was really hard. First there was a 15-minute recruiter call — a quick chat about my current job, why I was looking, and visa/status questions. They said the interview process would be laid out in a follow-up email. The phone interview was two rounds total, one hour each. Round 1: coding (SQL and Python), plus a case study. The SQL question was built around drivers and…

Technical Screen0
UberData Scientist
Oct 2025

Four Onsite Rounds, Rejected on Analytics and Bar Raiser

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

RejectedOnsiteXP0
UberData Scientist
Oct 2025

Two Tech Screens, Screwed Over by My Own Round 2 Interviewer

Two rounds of tech screens at Uber — tl;dr, I got screwed over by one of my own. Sharing this for those who come after. Round 1: coding and case study. The coding part was simple Python scripts, nothing like an LC medium, I blew through it in 15 minutes. The case study asked about the various downstream effects of a change in rider ETA, and how I'd design an experiment for it — we went from suppl…

Technical Screen0
UberData Scientist
Oct 2025

Rejected After a Tough BPS Round With AB Testing, an ML Case, and Coding

I have a master's degree and 1.5 YOE as a DS at a pretty chill, low-pressure company. Even though I got rejected, this was still one of the best interview experiences I've had. HR Screening They asked about my background on my resume, my visa/status situation, and my willingness to relocate. Then they asked why I was interested in the role, what tech stack I use day to day, etc. They also introdu…

RejectedTechnical Screen0
UberData ScientistSenior+
Oct 2025

Network Effects, IV Assumptions, and a String-Matching Question

Last month I interviewed for a senior DS role at Uber, so I'm sharing it here. There were two technical rounds, each an hour long. They covered past projects and some case studies. Overall the difficulty wasn't that high, but I kept feeling like we weren't quite on the same wavelength — I probably wasn't giving the answers they were looking for. The first round was with a DS director, who asked a…

Technical Screen0
UberData Scientist
Oct 2025

Phone Screen Pairs a Quick Coding Question with a Full A/B Testing Case Study

Before the interview, Uber's recruiter sends over some documents to help you prepare — a rough outline of the interview process, what knowledge you should study, and a bunch of links to help you get familiar with Uber's products. The first round is a one-hour phone screen. It starts with talking about the team and about yourself, then a 20-minute easy-difficulty coding question, then a case study…

Technical Screen0
UberData ScientistSenior+
Sep 2025

Two Phone Screens After No Sleep with a Sick Kid

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

Technical ScreenXP0
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
UberMachine Learning Engineer
Sep 2025

MLSD on Driver ETAs, Then a Coding Problem I'd Never Seen Before

The first round was MLSD, but it wasn't a traditional recommendation system or search problem — it was a design for real-time updates to the remaining ETA of every driver within a grid. You could only use the data they gave you, so the questions got very detailed, and any manual feature was challenged down to the last detail — I had to spell out exactly how every step would be implemented. GPS si…

Onsite0
UberProgram ManagerSenior+
May 2025

Passed the Third Round the Same Afternoon

Last Friday I had my third-round interview for a Senior Program Manager role at Uber's San Francisco office. Worth reading if you have a liberal-arts, business, or other non-tech background. Interview length: 45 minutes Questions asked: Intro Why Uber Why U... Where do you see yourself in 3-5 years Your biggest, proudest project A story backed by data and metrics Uber Eats vs. DoorDash Small case…

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