Uber's PM interviews combine a recruiter and hiring-manager screen with product-sense rounds on real marketplace problems, a distinctive JAM session, and, in some reports, a case study presented to a panel.
$165K
Avg. Base Comp
$230K
Avg. Total Comp
4-7 rounds
Typical Rounds
4-8 weeks
Process Length
Uber's Product Manager interviews pair a fairly conventional recruiter and hiring-manager screen with a few distinctive later stages. The most memorable for several candidates is the JAM session. One candidate received a prompt a few days in advance and prepared a strategy presentation to pitch to a panel of PMs and engineers. Others called the round tiring, domain-specific and centered on prioritization and tradeoffs, and one JAM prompt asked for designing support for an autonomous vehicle. Some candidates also describe a separate case study or take-home assessment that they prepared and then presented to a panel, followed by behavioral and product questions. One noted the assessment tested analytics and SQL.
Product-sense questions tend to focus on Uber's real marketplace mechanics rather than generic feature brainstorming. Candidates report being asked how they would reduce ride cancellations, improve the driver experience, think about rider-driver matching, or launch a product like Uber Train. Interviewers pushed for two-sided tradeoff thinking and clear metrics. Hiring-manager rounds commonly dig into a past experiment, a product strategy or a single resume item in depth, so come with three or four strong product stories and know the metrics behind them. Expect cross-functional sessions as well: candidates mention rounds with engineering and data science covering real-time systems, A/B testing versus pre-post analysis, and their own past experiments.
End-to-end timelines in these reports ranged from about four weeks to roughly two months, and round counts differ by team. Several candidates received little feedback or follow-up after later rounds, so a slow response is not unusual.
Synthesized from 25 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 process kicked off with an HR conversation where they walked me through the role and benefits package. That was straightforward enough, but then came the case presentations, which were the real test. I did a quick case with the director overseeing the role, followed by a more comprehensive case with the broader leadership team and their direct reports. The cases weren't incredibly complex, but the questions came fast and relentless. They weren't just asking for my answer—they were pushing hard on my reasoning, challenging my assumptions, and digging into why I'd made certain decisions. One case specifically focused on how I'd manage the rollout of a new onboarding feature, which required thinking through phasing, user impact, and cross-functional coordination. Throughout, I noticed the interviewers used a STAR-like structure to evaluate whether I had real experience backing up my points and could think critically in a structured way. They seemed more interested in understanding my perspective on past experiences and my critical thinking than in me having the "right" answer. The whole process moved quickly—the TA was genuinely helpful in coordinating everything smoothly. Still, despite the efficient logistics, the substantive rigor of the cases and the depth of questioning left me feeling uncertain. The difficulty wasn't in the complexity of the problems themselves, but in articulating decisions under pressure and demonstrating that I had both the experience and the reasoning to back them up.
Prep tip from this candidate
Prepare concrete examples using the STAR method where you can clearly articulate your reasoning and trade-offs on product decisions. For case questions around feature launches and user onboarding, focus on demonstrating both business acumen and structured thinking—they'll push hard on your assumptions, so anticipate follow-up questions on phasing, metrics, and cross-functional dependencies.
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.
Featured question at Uber
How would you assess the validity of the result?
| Question | |
|---|---|
| Employee Salaries | |
| Button AB Test | |
| Top 3 Users | |
| Download Facts | |
| WAU vs Open Rates | |
| User Experience Percentage | |
| Distance Traveled | |
| Size of Joins | |
| Google Maps Improvement | |
| Third Purchase | |
| Bank Fraud Model | |
| Encoding Categorical Features | |
| Uber User Journey | |
| Network Experiment Design | |
| Hurdles In Data Projects | |
| Bloated Mid-Funnel | |
| Revenue Retention | |
| P-value to a Layman | |
| Christmas Dinner Ingredient Optimization | |
| Testing Price Increase | |
| Random Forest Explanation | |
| Type-ahead Search | |
| Random Weighted Driver | |
| Xgboost vs Random Forest | |
| Cancellation Fees | |
| Demand Metrics | |
| Uniform Car Maker | |
| Assumptions of Linear Regression | |
| RAG Strict Source Control |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call covering background, why Uber, and fit for the role. It is typically straightforward. One candidate said the recruiter gave helpful tips on what to expect, while another described delayed communication between rounds.
A hiring manager round, reported at around 30-45 minutes, goes beyond standard behavioral questions. Candidates were asked to explain a past experiment in detail, walk through their resume with heavy follow-ups, or reason about improving the driver experience and rider-driver matching.
Several candidates describe a JAM round focused on prioritization and tradeoffs. One received the prompt a few days early and pitched a strategy presentation to a panel of PMs and engineers. Another was asked to design support for an autonomous vehicle.
Some candidates prepared a product case study or take-home assessment and presented it to PMs or a panel, followed by behavioral and product questions. One reported the assessment tested analytics and SQL, with prompts such as launching Uber Train and choosing post-launch KPIs.
Reported onsite loops include product cases on marketplace liquidity or improving a favorite product. They also include sessions with engineering and data science covering real-time systems, A/B testing versus pre-post analysis, and past experiments. These rounds push for two-sided marketplace reasoning rather than single-feature answers.
Later stages for some candidates included a leadership/behavioral chat, a skip-level conversation, or an in-person round about motivations. Not every report includes this stage, and several candidates received little feedback afterward.
