Uber Interview Experiences

42 results

• 

  Diff-in-Diff, Switchback Design, and a Causal Inference Deep DiveUber · Data Scientist · Senior+ · Technical Screen · Dec 2025

  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…

• 

  PhD ML Intern OA, Coding, ML Round and Team MatchUber · Software Engineer · Intern · Technical Screen · Dec 2025

  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…

• 

  Two Brutal Phone Rounds on Airport Supply and DemandUber · Data Scientist · Senior+ · Technical Screen · Nov 2025

  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…

• 

  Network Effects, IV Assumptions, and a String-Matching QuestionUber · Data Scientist · Senior+ · Technical Screen · Oct 2025

  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…

• 

  Phone Screen Pairs a Quick Coding Question with a Full A/B Testing Case StudyUber · Data Scientist · Technical Screen · Oct 2025

  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…

• 

  Rejected After a Tough BPS Round With AB Testing, an ML Case, and CodingUber · Data Scientist · Technical Screen · Oct 2025

  Rejected

  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…

• 

  Two Tech Screens, Screwed Over by My Own Round 2 InterviewerUber · Data Scientist · Technical Screen · Oct 2025

  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…

• 

  a Candy-Crush Matrix and a Fruit-Pair Sliding Window on the OAUber · Software Engineer · Online Assessment · Sep 2025

  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…

• 

  An OA With a Hand-Coded Tetris Fill ProblemUber · Software Engineer · Online Assessment · Sep 2025

  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…

• 

  Meeting Scheduler Follow-ups, Paxos/Raft BQ, and a Driver HeatMap System DesignUber · Software Engineer · Onsite · Sep 2025

  Offer

  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…

• 

  MLSD on Driver ETAs, Then a Coding Problem I'd Never Seen BeforeUber · Machine Learning Engineer · Onsite · Sep 2025

  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…

• 

  Passed the Third Round the Same AfternoonUber · Program Manager · Senior+ · Onsite · May 2025

  Offer

  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…