Uber's Product Analyst interviews run through a recruiter screen, a hiring manager or SQL/metrics screen, and a multi-round onsite covering product metrics cases and behavioral questions, with one candidate also facing a demanding experimentation round.
$121K
Avg. Base Comp
$170K
Avg. Total Comp
4-7 rounds
Typical Rounds
Not reported
Process Length
Uber's Product Analyst interviews start light and can get technical fast. Both reported processes opened with a recruiter call focused on background and fit; in one, the recruiter specifically checked whether the candidate understood how a two-sided marketplace works and aligned with Uber's values. The next step differed: one candidate had a 60-minute hiring manager conversation about past work and how they think about product problems, while the other faced a 45-minute live SQL screen built around window functions and on-the-spot metric diagnostics. The onsite is where the role gets tested in earnest: one candidate described a five-round day spanning product sense (diagnosing a sudden spike in rider cancellations in a specific city), statistics and experimentation, applied modeling, and a bar-raiser behavioral round, while the other's onsite centered on a metrics-and-funnel case alongside behavioral prompts like why Uber, why they were looking for a new role, and recent manager feedback.
Structured metrics thinking is the clearest common thread: in both accounts, the case required walking through which metrics to pull and how to interpret changes in the numbers. The candidate who received an offer said the experimentation round is where interviewers push hardest. They were not interested in a textbook A/B test description, and instead wanted reasoning about switchback experiments, synthetic controls, and variance reduction with CUPED because of network effects and driver cannibalization. That candidate's applied modeling round focused on handling imbalanced data and production tradeoffs. The bar raiser dug into whether past work drove measurable business impact and how the candidate pushed back on product managers with data. Practice talking through funnel and root-cause metrics out loud, and if your loop includes experimentation, prepare to go well beyond a standard A/B test. The other candidate noted that a Jam-style exercise was moved into the onsite, so it is worth confirming the format with your recruiter.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Uber process.
The question that stuck with me was how I would increase rider supply in a given market. That came up in the second round, and it was the moment the interview shifted from something I expected to be finance-heavy into a real product exercise. The first round was a recruiter call, and it was the easy part. The recruiter was friendly and informative, and walked me through what the role involved, which made the next step feel less like a gate.
The second interview was a set of mini case questions with interviewers who were not especially warm. They didn't seem very invested in the conversation, and I caught myself filling silences more than I wanted to. What caught me off guard was the expectation for precision. Reasonable answers in general growth language weren't enough. The recruiters had made it clear they wanted Uber-specific terminology, so I needed to talk about the marketplace the way the company does, not just in generic product-speak.
From what I've seen, this role leans heavily on analytics and can include a take-home alongside the cases, so budget time for that. I didn't get an offer. Looking back, I'd spend less time on general frameworks and more on how Uber's two-sided marketplace actually works, with concrete metrics for riders, drivers, and the balance between them. The interview was really testing whether I could think like someone already inside the business, and I didn't convince them I could.
Prep tip from this candidate
Be ready to answer market-growth cases like increasing rider supply in a city using Uber's own marketplace vocabulary and metrics for both riders and drivers. Interviewers expected precise, jargon-accurate answers rather than generic product frameworks.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
| Question | |
|---|---|
| Employee Salaries | |
| Button AB Test | |
| Bank Fraud Model | |
| Experiment Validity | |
| Download Facts | |
| WAU vs Open Rates | |
| Network Experiment Design | |
| Distance Traveled | |
| Weighted Keys | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Top 3 Users | |
| Third Purchase | |
| Type-ahead Search | |
| Encoding Categorical Features | |
| Uber User Journey | |
| Hurdles In Data Projects | |
| Bloated Mid-Funnel | |
| Revenue Retention | |
| Size of Joins | |
| Christmas Dinner Ingredient Optimization | |
| Assumptions of Linear Regression | |
| Testing Price Increase | |
| Random Forest Explanation | |
| Random Weighted Driver | |
| Xgboost vs Random Forest | |
| Cancellation Fees | |
| Data Preparation for Imbalanced Data | |
| Uniform Car Maker |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter call focused on background, motivation for applying, and general fit for the Product Analyst role. One candidate described it as largely a vibe check on understanding how a two-sided marketplace works and alignment with Uber's values, so expect this stage to be conversational rather than technical.
Reports diverge here: one candidate had a 60-minute hiring manager conversation about past work and how they think about product problems and team alignment, while another candidate instead faced a 45-minute live coding screen emphasizing SQL window functions and basic metric diagnostic questions. Candidates should prepare for either format, since the screening step after the recruiter call is not consistent across reports.
The onsite typically includes a case built around product metrics, such as explaining how to diagnose a funnel change or, per one candidate, walking through exactly which metrics to pull and in what order after a sudden spike in rider cancellations in a specific city. Candidates report this tests structured thinking about product metrics rather than memorized definitions.
One candidate described this as the round where most candidates get filtered, with interviewers pushing past a standard A/B test to probe switchback experiments and synthetic controls because of network effects and driver cannibalization, plus a deep question on CUPED for variance reduction and when to use it versus alternatives. That candidate's account suggests this round carries significant weight when it appears.
The same onsite included an applied modeling discussion about handling imbalanced data and production tradeoffs, and a bar-raiser behavioral round that, per the candidate, dug into whether past work drove real business impact and how the candidate pushed back on product managers with data. A separate candidate's final stage instead emphasized standard behavioral prompts (why Uber, why job hunting, recent manager feedback) alongside the metrics case, so the exact mix of behavioral depth may vary by interview loop.
