Uber Data Scientist interview questions

6 Data Scientists have shared notes from their Uber interviews, with the questions they were asked in each round. That is 2% of the 263 Uber interview notes on Screna AI.

6 Data Scientist interview notes

Uber·Data Scientist·Technical Phone Screen

Jun 2026
Uber data scientist interview with a pandas/Python coding problem centered on computing completion rates from order data, followed by a product case study on diagnosing low completion rates in a specific city. The technical bar felt more like applied analytics than pure algorithms, which I wasn't fully expecting.
  • Given a DataFrame of orders with columns for order_id, city, order_type, and status, compute the completion rate (completed / total) for a given (city, order_type) pair. Handle NaN values, zero denominators, and case sensitivity correctly.
  • If the completion rate for a specific city is unusually low, what are the possible root causes and how would you validate each? Which intervention would you ship first?

“I went straight for pandas groupby and immediately second-guessed myself on NaN handling.”

View Post

Uber·Data Scientist·Onsite - Behavioral / Leadership

May 2026
Second behavioral and case-study round at Uber for a Data Scientist role, focused on project deep dives with a twist: they want a different project than what you covered earlier, and they'll stress-test your design by changing the constraints mid-conversation.
  • Walk me through a project you haven't discussed in previous rounds, covering the design decisions and trade-offs you made.
  • Now imagine the scale is 10x what you described. What breaks first in your design and how would you address it?
  • If you had to optimize for a completely different success metric than the one you chose, how does your approach change?
  • How would your analysis or model hold up if a key data source was unavailable or unreliable?

“The 'different project' requirement is the part people underestimate.”

View Post

Uber·Data Scientist·Technical Phone Screen

May 2026
Uber Data Scientist technical screen with a classic array manipulation problem and a follow-up that tightened the constraints. Nothing too exotic but the boundary cases will bite you if you're not careful.
  • Given an array, rotate it by k positions. Then, as a follow-up, implement the same operation in O(1) extra space.

“First pass I just allocated a new array and copied elements over.”

View Post

Uber·Data Scientist·Technical Phone Screen

May 2026
Uber DS interview that went deep on experiment rollout. The whole session was basically one extended case built around launching an ETA-related experiment into production, covering everything from bucket design to the launch decision itself.
  • You've designed an experiment around ETA multipliers. How would you actually roll it out in production? Walk through how you'd structure the treatment buckets and decide on bucket sizes.
  • What guardrails would you set before launching? Define the key metrics that can't regress and describe how you'd handle auto-rollback.
  • Once the experiment runs, how do you interpret the results and translate them into a launch or no-launch decision? Cover things like confidence intervals, multiple comparisons, practical vs statistical significance, and confounders like novelty effects or day-of-week patterns.

“I went straight to equal splits and they pushed back immediately.”

View Post

Uber·Data Scientist·Technical Phone Screen

Apr 2026
Uber DS interview that went deep into experimentation design for a two-sided marketplace. The whole session was basically one long question about switchback experiments, and it got technical fast.
  • Design an experiment to measure the causal effect of showing different ETAs on whether a rider session ends in a completed ride request. Walk through why a standard individual-level A/B test breaks down here, and propose an alternative experimental design.

“This is the kind of question where you think you know where it's going and then it just keeps going.”

View Post

Uber·Data Scientist·Onsite - System Design / Architecture

Apr 2026
Uber DS interview focused almost entirely on a full recommendation system design, the kind where they want you to go deep on every layer and actually defend your choices rather than just listing buzzwords. Pretty intense for a single question.
  • Design a recommendation system end-to-end for a product like a feed, e-commerce platform, or short-video app. Walk through your goals and metrics, data, features, model architecture, serving, and monitoring.

“This thing ate the whole session.”

View Post