1. What is a Product Growth Analyst?

As a Product Growth Analyst at Uber, you occupy a strategic intersection between data science, product management, and marketing. While many analyst roles focus strictly on reporting, this position is fundamentally about driving the business forward. You are the navigator for the Product Growth teams—such as Rider Growth or Growth Bets—helping them identify where to grow, how to optimize funnels, and why users behave the way they do.

Your work directly impacts Uber’s ability to scale globally. You will not just query data; you will shape the strategy for critical initiatives like converting Riders into Uber Eats customers, unlocking new geographic markets, or reducing churn among high-value users. You are responsible for designing rigorous experiments, defining success metrics for new features, and uncovering insights that lead to "0 to 1" product launches.

This role requires a unique blend of technical precision and product intuition. You will tackle complex questions regarding two-sided marketplace dynamics (supply and demand) and user lifecycle management. At Uber, data is the loudest voice in the room, and as a Product Growth Analyst, you provide that voice.

2. Common Interview Questions

The following questions are representative of what you might face. They are drawn from actual candidate experiences and the specific context of Uber’s growth teams. They are grouped by category to help you practice different "modes" of thinking.

Technical & SQL

These questions test your raw execution ability.

• "Given a table of trips and users, write a query to find the retention rate of riders who signed up in January 2024."
• "Calculate the average time between a user's first and second ride."
• "Write a query to find the top 3 city-pairs (origin to destination) by revenue for each day of the week."
• "How would you deal with missing values in the driver_location dataset?"

Product Execution & Metrics

These questions test how you apply data to business logic.

• "We noticed that ride cancellations increased by 5% yesterday. Walk me through how you would debug this."
• "What metrics would you track to measure the success of a new 'subscription pass' for Uber Eats?"
• "How would you measure the cannibalization effect of Uber Pool on Uber X?"
• "If we want to increase the number of First Trips for new users, what part of the funnel would you focus on and why?"

Strategic Growth & Case Studies

These questions test your ability to think big and structure complex problems.

• "We want to launch Uber in a new city. How do we determine which city to pick?"
• "How would you design an experiment to test if offering a coupon to dormant users is profitable?"
• "Should we prioritize features that increase Driver supply or Rider demand right now? How would you decide?"

These questions are based on real interview experiences from candidates who interviewed at this company. You can practice answering them interactively on Dataford to better prepare for your interview.

3. Getting Ready for Your Interviews

Preparing for an interview at Uber requires a shift in mindset. You are not just being tested on your ability to write SQL or calculate a p-value; you are being evaluated on your ability to use those tools to solve ambiguous business problems at a massive scale.

You will be evaluated on the following core criteria:

Data Proficiency & Technical Execution – You must demonstrate advanced proficiency in SQL and data manipulation. Interviewers expect you to write clean, optimized code that can handle complex joins and window functions typical of Uber’s massive datasets. You also need a solid grasp of statistical concepts, particularly regarding A/B testing and experimentation design.

Product Sense & Metric Definition – This is often the differentiator for successful candidates. You need to show that you can translate a vague business goal (e.g., "increase rider retention") into concrete, measurable metrics. You will be tested on your ability to define primary metrics, guardrail metrics, and trade-offs within the marketplace ecosystem.

Strategic Problem Solving – Uber looks for candidates who can navigate ambiguity. You will face open-ended case studies where you must structure a problem, hypothesize root causes, and propose data-driven solutions. You need to demonstrate "systems thinking"—understanding how a change in the Rider app might impact Driver earnings or Eats delivery times.

Communication & Influence – As an analyst, your insights are only as good as your ability to communicate them. You will be assessed on how effectively you can present complex data findings to cross-functional stakeholders, including Product Managers, Designers, and Engineering leads, to drive decision-making.

4. Interview Process Overview

The interview process for the Product Growth Analyst role is rigorous and structured to test both your technical baseline and your analytical thinking. Typically, the process moves quickly once you pass the initial screening. Uber values speed and efficiency ("Go Get It" is a core cultural value), so expect a process that feels intense but focused.

You will generally start with a recruiter screen to align on your background and interest in the specific vertical (e.g., Rider Growth vs. Eats). This is followed by a technical screen, often involving a live coding session (SQL) or a "take-home" style analytics challenge discussed over a video call. If you succeed there, you will move to the "onsite" loop (virtual), which consists of 3–5 back-to-back interviews covering technical skills, product cases, and behavioral alignment.

Uber’s interviewing philosophy emphasizes practical application over theory. They want to see how you think in real-time. You will likely face a "Jam Session" or a collaborative case study where the interviewer acts as a peer, and you work together to solve a growth problem. This is designed to simulate the actual working environment at Uber.

The timeline above illustrates the typical flow from application to offer. Note the distinct separation between the Technical Screen (focusing on raw skills like SQL/Stats) and the Onsite Loop (focusing on application and strategy). Use the time between the screen and the onsite to shift your preparation from "how to code" to "how to solve business cases."

5. Deep Dive into Evaluation Areas

To secure an offer, you must excel in specific evaluation areas that reflect the day-to-day realities of the role. Based on candidate reports and job requirements, these are the critical pillars of the interview.

Analytics & SQL Execution

This is the non-negotiable baseline. Uber has one of the richest datasets in the world, and you need to prove you can navigate it independently. You will be asked to solve problems using SQL in a live environment (e.g., CoderPad).

Be ready to go over:

• Complex Joins & Filtering – Handling multiple tables (Riders, Trips, Eaters, Orders) and filtering for specific timeframes or segments.
• Window Functions – Using RANK, LEAD, LAG, and moving averages to analyze user behavior over time.
• Data Cleaning – Handling NULLs, duplicates, and messy timestamp formats.
• Advanced concepts – Self-joins for retention analysis and funnel conversion calculations.

Example questions or scenarios:

• "Write a query to calculate the 7-day rolling retention rate for new riders in NYC."
• "Identify the top 10% of drivers by earnings per hour for the last month."
• "Find the number of users who took a ride and ordered a meal on the same day."

Experimentation (A/B Testing)

Growth at Uber is driven by experimentation. You must understand the statistics behind the tests and the pitfalls of testing in a two-sided marketplace.

Be ready to go over:

• Hypothesis Formulation – Clearly stating what you are changing, what you expect to happen, and why.
• Metric Selection – Choosing the right primary metric (e.g., Conversion Rate) and secondary/guardrail metrics (e.g., Latency, Cancellation Rate).
• Significance & Power – Calculating sample sizes and understanding p-values and confidence intervals.
• Network Effects – Understanding how a treatment on the demand side (Riders) might affect the supply side (Drivers) and how to control for interference (e.g., using switchback testing or geo-based testing).

Example questions or scenarios:

• "We want to test a new push notification to re-activate dormant riders. How would you design this experiment?"
• "An A/B test shows a 5% increase in bookings but a 2% increase in cancellations. Do we launch?"
• "How do you handle interference in a marketplace experiment where the control group is affected by the treatment group?"

Product Sense & Metric Investigation

These interviews test your intuition. You will be given an open-ended scenario and asked to diagnose a problem or size an opportunity. This aligns closely with the "Growth Bets" and "Rider Growth" team missions.

Be ready to go over:

• Root Cause Analysis – Systematically breaking down a metric drop (e.g., Is it seasonal? Technical? Regional? A competitor move?).
• Funnel Optimization – Analyzing user flows (e.g., App Open -> Request Ride -> Trip Complete) to find drop-off points.
• Opportunity Sizing – Estimating the potential impact of a new feature (e.g., "Uber One" subscription) before building it.

Example questions or scenarios:

• "Ride requests have dropped by 10% in San Francisco week-over-week. How would you investigate?"
• "We are thinking of launching a loyalty program for Uber Eats. How would you decide if it’s a good idea?"
• "Define success metrics for the 'Schedule a Ride' feature."