READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 142 of 153
Interview experiences · Uber
Uber Senior+ Data Scientist Interview Experience — 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…
Interview experiences · Uber
Uber Senior+ Data Scientist Interview Experience — 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…
Interview experiences · Uber
Uber Senior+ Data Scientist Interview Experience — 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…
Interview experiences · Uber
Uber Senior+ Machine Learning Engineer Interview Experience — Withdrew After a Possible L5A-to-L4 Downlevel
I interviewed for a Sr MLE / MLE role. The whole process was pretty short — in the end, after HR indicated I might get downleveled from L5A to L4, I decided not to move forward, so this is basically a withdrawal report. The first round was mainly a project deep dive. It opened with self-introductions, then the interviewer asked me to walk through a recent representative project. I talked about a…
Interview experiences · Uber
Uber Senior+ Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
Uber Software Engineer Interview Experience — 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…
Interview experiences · Uber
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…
Interview experiences · Uber
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…
Interview experiences · Uber
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…
Interview experiences · UBS
UBS Software Engineer Interview Experience: Intended offer cancelled in a hiring freeze
The process began unusually smoothly and went far enough that I thought it was essentially finished. I received verbal and email confirmation of an intended offer, and HR walked me through the compensation package. I submitted identification and onboarding documents and was told the relevant internal system approvals were complete. Then everything stalled. Hiring was stopped because of an interna…
Interview experiences · UCB
UCB Research Scientist interview: long panel and late technology feedback
I went through several steps that ended with a long final panel. After two earlier rounds, I was invited to a face-to-face stage lasting roughly 3 to 4 hours. It began with a presentation, moved into Q&A, and involved discussions with about 10 interviewers. I was eager to meet the team and understand how the group worked, but the day took substantial time and preparation. The feedback afterward t…