Interview Experiences

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

Share yours, earn XP

7 stories

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

Uber DriversSoftware Engineer
Reported Jul 2026

Uber Drivers Software Engineer interview: five coding interviews and non-selection

I went through essentially the full process and wasn't selected. It took almost a month, which felt reasonably quick to me despite how challenging it was. There were five coding interviews. I don't have many details about the individual questions, but the number of coding rounds made the process feel intense and more selective than I'd expected. After the "not selected" result, I was left with th…

RejectedTechnical Screen0
Uber DriversData Scientist
Reported Jul 2026

Uber Drivers Data Scientist interview: framing consumer fraud risk

The first round was about risk. I completed one SQL task and then answered a question about a confusion matrix. The follow-up on consumer fraud risk was what threw me. When I explained the risks as I saw them, they did not seem impressed, and that feedback came across quite directly. I did not move to later stages. It felt as though the bar was not only technical correctness. How I framed fraud r…

RejectedTechnical Screen0
Uber DriversAccount Executive
Reported Jul 2026

Uber Drivers Account Executive interview: aptitude and phone screen

I had a direct process that began with a recruiter-style check. The early screening asked about my client-facing work and how I had handled vendor relationships, including relationships with different alcohol vendors. An aptitude-style step followed, then a phone interview focused on my experience and gave me more information about what the role would involve. These early rounds felt average in d…

RejectedOnline Assessment0
Uber DriversData Scientist
Reported Jul 2026

Uber Drivers Data Scientist interview: SQL bottleneck in a timed test

My first step was a 60-minute test with 17 questions: two medium SQL questions and 15 aptitude questions. The aptitude questions felt easier, as though I could get through most of them in under half the time. I spent longer on the SQL section and could not fully solve everything. By the end, I was hoping that the partial progress would be enough to move forward, but I did not get an interview aft…

Online Assessment0
Uber DriversOperations Manager
Reported Jul 2026

Uber Drivers Operations Manager interview experience

After the recruiter screen, I had a 1:1 with the hiring manager. I then gave a case-study presentation and went through three business interviews, explaining my thinking and answering questions as I went. Repeated waits for interviewer availability made the process drag, and its length was draining even though it was not unusually chaotic. People communicated consistently, expectations were clear…

0
Uber DriversSoftware Engineer
Reported Jul 2026

Uber Drivers Software Engineer interview: time-boxed coding exam

I went through an online coding exam with medium-to-hard LeetCode-style questions. The format was tightly time-boxed: 45 minutes for each of three questions. It felt like a real test of both DSA fluency and time management. Even without an onsite, the exam itself carried a good amount of difficulty, and I did not move forward. I approached it knowing I needed to be efficient as well as correct. W…

Online Assessment0
Uber DriversSoftware Engineer
Reported Jun 2026

Uber Drivers Software Engineer interview: recursive strings and trees

I had two separate interviews built around DSA problems. The first was a recursion-based string-manipulation question. The second moved to trees and asked for a tree coding solution. Both interviews added follow-ups after the main question, so finishing the initial problem was not the end of it. Those extensions raised the difficulty and made the rounds feel more demanding than the opening prompt…

Technical Screen0

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