Uber Data Scientist Interview Guide

We've seen Uber consistently favor candidates who can reason through messy marketplace tradeoffs, not just recite textbook methods. Multiple candidates reported questions that pushed beyond standard A/B testing into synthetic control, difference-in-differences, interrupted time series, and especially switchback testing. That tells us the bar here is less about naming the right framework and more about knowing why a framework fits a rides, delivery, or pricing problem. When candidates stumbled, it was usually because they stayed too abstract or couldn't defend the assumptions behind their design.

A recurring theme is that Uber cares deeply about metrics that map to marketplace health. Candidates were asked to define success for ETA changes, batching, surge pricing, driver assignment, and service expansion, and the strongest answers tied primary metrics to operational outcomes like match rate, completed rides, or order volume, then layered in guardrails like cancellations, complaints, retention, and driver earnings. We've also seen interviewers probe failure modes hard: what happens when an experiment looks off, how to verify results, and how to handle endogeneity when pricing and demand move together. That emphasis shows up again in the econometrics-style questions around price elasticity and surge pricing.

The non-obvious separator is clarity under ambiguity. Several candidates noted that the coding itself was not the hardest part; the harder part was framing the problem, stating constraints, and explaining tradeoffs without getting lost. Even behavioral feedback points in the same direction: the bar raiser expects stories that reflect Uber's values in concrete business decisions, not polished leadership language. In practice, our candidates who did best sounded like people who had actually thought about how a marketplace behaves when incentives, supply, and customer experience all interact.