Uber Data Scientist Interview Questions (2026)
200 real Data Scientist interview questions compiled for Uber, 200 of them tailored to Uber's actual interview flavor. Turn data into insight and models that inform decisions and products. Below: the interview process, the questions with answer outlines, the topics tested, and how to prepare.
Uber runs a fast, bar-heavy loop: a CodeSignal or live coding screen, then a virtual onsite with two coding rounds, a system design round steeped in real-time/marketplace problems, and a behavioral round mapped to its rewritten cultural norms. Uber India (Bangalore/Hyderabad) engineering interviews at the same global bar.
Questions
200
200 company-tailored
Difficulty
Medium
from our question mix
Rounds
6
typical loop
Uber rating
4.06/5
Top 99% in Internet
Uber's interview process
- 1Recruiter Screen30 minEasy
Role targeting, level calibration and process expectations.
- 2Technical Phone Screen60 minMedium
One or two medium DSA problems (CodeSignal or live) with emphasis on correct, runnable code and edge cases.
- 3Onsite Coding I60 minHard
Practical problem such as building a rate limiter or an in-memory index, judged on working code and API cleanliness.
- 4Onsite Coding II60 minHard
Algorithmic problem often with a geospatial or streaming flavor, pushed to optimal complexity.
- 5System Design60 minHard
Design a real-time marketplace system (dispatch, ETA, surge) with hard follow-ups on scale, geo-sharding and failure modes.
- 6Behavioral / Hiring Manager Round45 minMedium
STAR stories mapped to Uber's cultural norms: ownership, bold bets, customer obsession and conflict handling.
Data Scientist interview questions asked at Uber
- Q1
Design an A/B test for a change to Uber Rides intended to improve completed trips
HardExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Rides; context = mobility, delivery, freight, and advertising marketplace; objective = completed trips; ecosystem/entity = riders and drivers.
How to answer: Define hypothesis, treatment/control, eligible users, randomization unit, metrics, duration, and decision rule.
- Q2
Choose primary, secondary, and guardrail metrics for a Uber Eats experiment
EasyExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Eats; context = mobility, delivery, freight, and advertising marketplace; objective = order delivery time; ecosystem/entity = riders and drivers.
How to answer: Map metrics to business/user value; include quality, safety, latency, monetization, and retention guardrails.
- Q3
Estimate experiment duration for a Uber Freight test with limited traffic and small expected lift in completed shipments
MediumExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Freight; context = mobility, delivery, freight, and advertising marketplace; objective = completed shipments; ecosystem/entity = riders and drivers.
How to answer: Use baseline variance, traffic, MDE, alpha/power, seasonality, and segment prioritization.
- Q4
Should the Uber for Business test randomize by trip, session, market, or cluster? Justify your choice
MediumExperiment design caseExperimentationUber-specificContext: Uber variation: Uber for Business; context = mobility, delivery, freight, and advertising marketplace; objective = repeat trip rate; ecosystem/entity = riders and drivers.
How to answer: Discuss exposure consistency, interference, statistical power, implementation, and estimand.
- Q5
Uber Advertising has social, marketplace, or ranking spillovers. How would interference violate standard A/B assumptions?
HardExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Advertising; context = mobility, delivery, freight, and advertising marketplace; objective = ad CTR; ecosystem/entity = riders and drivers.
How to answer: Explain SUTVA violations, cluster tests, switchbacks, geo tests, and spillover measurement.
- Q6
Design a switchback experiment for driver incentives where marketplace conditions change quickly
HardExperiment design caseExperimentationUber-specificContext: Uber variation: driver incentives; context = mobility, delivery, freight, and advertising marketplace; objective = driver acceptance rate; ecosystem/entity = riders and drivers.
How to answer: Choose time windows, washout, balance, seasonality controls, clustered inference, and operational feasibility.
- Q7
Your airport pickups experiment spans a holiday or major event. How would you protect inference for ETA accuracy?
EasyExperiment design caseExperimentationUber-specificContext: Uber variation: airport pickups; context = mobility, delivery, freight, and advertising marketplace; objective = ETA accuracy; ecosystem/entity = riders and drivers.
How to answer: Use pre-planned duration, stratification, time fixed effects, holdouts, and sensitivity analysis.
- Q8
Initial restaurant discovery results are strong but fade after one week. How do you detect and account for novelty effects?
MediumExperiment design caseExperimentationUber-specificContext: Uber variation: restaurant discovery; context = mobility, delivery, freight, and advertising marketplace; objective = restaurant conversion; ecosystem/entity = riders and drivers.
How to answer: Analyze time-since-exposure, retention cohorts, longer tests, ramp patterns, and long-term holdouts.
- Q9
The dispatch matching test is neutral overall but positive for new drivers. How would you evaluate the segment claim?
MediumExperiment design caseExperimentationUber-specificContext: Uber variation: dispatch matching; context = mobility, delivery, freight, and advertising marketplace; objective = rider cancellation rate; ecosystem/entity = riders and drivers.
How to answer: Use pre-specified segments, interaction tests, power, shrinkage, and replication.
- Q10
A shared rides experiment expected 50/50 allocation but shows 53/47. How do you investigate?
HardExperiment design caseExperimentationUber-specificContext: Uber variation: shared rides; context = mobility, delivery, freight, and advertising marketplace; objective = gross bookings; ecosystem/entity = riders and drivers.
How to answer: Check assignment logs, eligibility, bots, logging loss, bucketing changes, and rerun criteria.
- Q11
Create a ramp plan for launching Uber Rides after a positive experiment on completed trips
HardExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Rides; context = mobility, delivery, freight, and advertising marketplace; objective = completed trips; ecosystem/entity = riders and drivers.
How to answer: Use phased traffic, guardrail monitoring, segment checks, incident thresholds, and owner accountability.
- Q12
Before testing Uber Eats, what instrumentation and logging validation would you require?
EasyExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Eats; context = mobility, delivery, freight, and advertising marketplace; objective = order delivery time; ecosystem/entity = riders and drivers.
How to answer: Validate exposure, assignment, event timing, metric definitions, missingness, and audit dashboards.
- Q13
Another team is testing a related change that may affect Uber Freight. How would you handle concurrent experiments?
MediumExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Freight; context = mobility, delivery, freight, and advertising marketplace; objective = completed shipments; ecosystem/entity = riders and drivers.
How to answer: Discuss interaction effects, layer design, orthogonal allocation, exclusions, and analysis adjustments.
- Q14
A PM wants to stop the Uber for Business test as soon as repeat trip rate becomes significant. What do you advise?
MediumExperiment design caseExperimentationUber-specificContext: Uber variation: Uber for Business; context = mobility, delivery, freight, and advertising marketplace; objective = repeat trip rate; ecosystem/entity = riders and drivers.
How to answer: Explain inflated false positives, pre-set analysis windows, alpha spending, and decision governance.
- Q15
Only some users actually see Uber Advertising. Should you analyze all assigned users or only exposed users?
HardExperiment design caseExperimentationUber-specificContext: Uber variation: Uber Advertising; context = mobility, delivery, freight, and advertising marketplace; objective = ad CTR; ecosystem/entity = riders and drivers.
How to answer: Contrast ITT, treatment-on-treated, triggering, compliance, and unbiased estimators.
Practice these with instant AI feedback in a live mock interview → Start a Uber Data Scientist mock
Topics tested most
How to prepare for the Uber Data Scientist interview
Strong DSA and scalable system design; prepare analytical/behavioral stories
Indicative Data Scientist pay in India: ~₹11–48 LPA (role-level range, not a Uber-specific figure).
Frequently asked questions
How hard is the Uber Data Scientist interview?
Based on our bank of 200 Data Scientist questions asked at Uber, the overall difficulty is medium (Uber's process is generally rated elevated). Expect around 6 rounds spanning Machine Learning, Statistics, Experimentation.
How many interview rounds does Uber have for a Data Scientist?
Uber typically runs about 6 rounds for Data Scientist candidates: Recruiter Screen → Technical Phone Screen → Onsite Coding I → Onsite Coding II → System Design.
What is the interview process at Uber?
The Uber interview process typically runs: Recruiter screen -> technical screen -> onsite (coding x2, system design, behavioral). Prepare for each round in order rather than only the first — the later stages usually carry the most weight.
How hard is the Uber interview?
Uber interviews are rated high difficulty. The bar is highest on coding — go deep there and practise explaining your reasoning out loud.
What does Uber look for in candidates?
Uber focuses on Coding, large-scale system design, analytical thinking. Culturally, it values We build globally, customer obsession, bold bets, ownership. Line up your examples to hit both the technical bar and these values.
Explore more
Other roles at Uber
Data Scientist interviews at other companies
Compiled by PrepNPlaced from 200+ interview reports and question banks for the Uber Data Scientist loop, cross-referenced with 1,051 employee reviews. Data refreshed 2026-07-12. Updated 2026.