Uber Data Analyst Interview Questions (2026)

1. 1Recruiter Screen30 minEasy

   Role targeting, level calibration and process expectations.

2. 2Technical Phone Screen60 minMedium

   One or two medium DSA problems (CodeSignal or live) with emphasis on correct, runnable code and edge cases.

3. 3Onsite Coding I60 minHard

   Practical problem such as building a rate limiter or an in-memory index, judged on working code and API cleanliness.

4. 4Onsite Coding II60 minHard

   Algorithmic problem often with a geospatial or streaming flavor, pushed to optimal complexity.

5. 5System Design60 minHard

   Design a real-time marketplace system (dispatch, ETA, surge) with hard follow-ups on scale, geo-sharding and failure modes.

6. 6Behavioral / Hiring Manager Round45 minMedium

   STAR stories mapped to Uber's cultural norms: ownership, bold bets, customer obsession and conflict handling.

1. Q1

   For Uber Reserve, should randomization happen at rider, session, device, driver, or city level? Explain the tradeoffs

   MediumStatistics & Experimentation RoundA/B TestingUber-specific

   Context: Consider cross-device behavior, interference, marketplace effects, and operational feasibility.

   How to answer: Randomization for Uber Reserve should primarily happen at the rider level to ensure independent observations and minimize bias, as the feature directly impacts individual rider behavior and booking patterns. Session or device level randomization could lead to contamination if a single rider uses multiple devices/sessions, impacting the same underlying user. Driver level randomization is less suitable as Reserve is a rider-initiated feature, and a driver might serve both experimental and control riders. City level randomization might be considered for market-wide network effects but significantly reduces statistical power and increases cost/time.

2. Q2

   The Airport Trips experiment is trending positive after two days. A PM wants to stop early and launch. How do you handle peeking and sequential testing?

   MediumStatistics & Experimentation RoundA/B TestingUber-specific

   Context: Discuss pre-specified stopping rules, alpha spending, business urgency, and risk.

   How to answer: A strong candidate would explain that peeking early in an A/B test without proper statistical correction inflates the Type I error rate, leading to false positives. They should discuss the need for pre-defined sample sizes and test durations based on power analysis to ensure statistical validity. If early stopping is considered, methods like Sequential Testing (e.g., using an O'Brien-Fleming boundary or a Bonferroni correction for multiple looks) or Bayesian approaches can be mentioned as ways to control error rates. The candidate should emphasize the importance of resisting the urge to stop early due to positive trends without statistical justification, as this can lead to launching features that don't actually provide a lift.

3. Q3

   A new Uber for Business feature shows a large week-1 lift in request-to-complete rate, but the effect fades by week 4. What could explain this and how would you design the test duration?

   MediumStatistics & Experimentation RoundA/B TestingUber-specific

   Context: Discuss novelty, learning effects, seasonality, and durable impact.

   How to answer: The fading effect could be due to novelty effect, where users initially engage more with a new feature before returning to baseline behavior. Another explanation is selection bias, if the feature was initially rolled out to early adopters who are more engaged, or if the initial lift was driven by a specific segment that completed their 'use case' quickly. External factors like seasonality or concurrent marketing campaigns could also confound results. To design test duration, consider the typical user lifecycle and business cycle for Uber for Business, aiming for at least 2-3 full cycles to capture long-term behavior and account for potential novelty effects or seasonality.

4. Q4

   Two overlapping experiments on Uber Reserve both affect net revenue per trip. How would you detect and manage interaction effects?

   HardStatistics & Experimentation RoundA/B TestingUber-specific

   Context: Discuss experiment registry, factorial design, exclusion rules, and interaction terms.

   How to answer: A strong candidate would first identify the need for a statistical test to detect interaction effects, such as a multi-factor ANOVA or regression model including an interaction term. They would then propose segmenting users into four groups (Control, Exp A only, Exp B only, Exp A+B) and analyzing the net revenue per trip for each group, comparing the observed combined effect to the sum of individual effects. To manage interactions, they would suggest either sequential deployment, mutually exclusive user populations, or a joint decision-making framework based on the magnitude and direction of the interaction. Finally, they would emphasize the importance of pre-experiment power analysis to detect expected interaction effects.

5. Q5

   Uber Reserve is preparing for a high-traffic event or sale. What metrics and analyses would you use to prevent a business-critical failure?

   HardProduct Analytics & Business CaseBusiness CasesUber-specific

   Context: Think capacity, inventory, payments, support load, latency, and real-time alerting.

   How to answer: To prevent business-critical failure during a high-traffic event for Uber Reserve, I would focus on proactive monitoring of operational capacity and demand forecasting accuracy. Key metrics include driver supply-to-demand ratio, predicted vs. actual booking volume, and system latency for booking confirmations. I would also track surge multiplier effectiveness and cancellation rates, analyzing these metrics in real-time against pre-event baselines and predefined thresholds to identify anomalies. Pre-event, I'd conduct stress tests and scenario planning to validate system resilience and operational readiness, ensuring sufficient driver incentives and support staff are in place.

6. Q6

   Uber wants to launch or expand an ads/merchant monetization product related to Airport Trips. What business metrics decide whether it is worth scaling?

   HardProduct Analytics & Business CaseBusiness CasesUber-specific

   Context: Balance advertiser/partner value, customer experience, organic conversion, and incremental profit.

   How to answer: A strong candidate would first identify the core objective: increasing revenue and/or engagement from airport trips. Key metrics to track include Merchant Adoption Rate (number of merchants onboarded and active at airports), Ad Impression Volume (total views of ads), Click-Through Rate (CTR) and Conversion Rate (CVR) for ads, and ultimately, Revenue Per Trip (RPT) or Gross Merchandise Value (GMV) generated from these ads. They should also consider the impact on rider experience, measured by rider satisfaction scores or complaint rates related to ads, and operational efficiency metrics like merchant onboarding time.

7. Q7

   Set alert thresholds for request-to-complete rate, net revenue per trip, and ETA and cancellation rate in Uber for Business. How would you distinguish noise from a real incident?

   MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingUber-specific

   Context: Use seasonality, baselines, statistical thresholds, and business severity.

   How to answer: A strong candidate would first define appropriate alert thresholds for each metric, considering historical data, business goals, and statistical methods (e.g., standard deviations, percentage change). For request-to-complete rate, net revenue per trip, and ETA, thresholds might be a significant percentage drop or increase from a baseline. For cancellation rate, a sustained increase beyond a historical norm is key. To distinguish noise from a real incident, the candidate should propose using statistical significance tests, trend analysis over time, correlation with other metrics, and segmenting data by relevant dimensions (e.g., city, time of day, user type) to localize the issue. They should also mention setting up a tiered alerting system and a runbook for incident response.

8. Q8

   Design a retention analysis for Uber Eats. Which cohorts, time windows, and segments would you use?

   EasyProduct Analytics & Business CaseProduct AnalyticsUber-specific

   Context: Make the cohort definition precise and explain how you would separate activation from retention.

   How to answer: To design a retention analysis for Uber Eats, I would primarily define cohorts by the user's acquisition date (first order date) to track their behavior over time. The time windows would typically be weekly or monthly, observing the percentage of users from each cohort who place at least one order in subsequent periods. Key segments for deeper analysis would include new vs. existing users, geographic location (city/region), order type (pickup vs. delivery), and promotional usage, to identify specific drivers or detractors of retention. The ultimate goal is to understand how different user groups engage with the platform over time and pinpoint areas for product or marketing intervention.

9. Q9

   Uber for Business has rising churn or inactivity among high-value riders. How would you quantify the problem and identify drivers?

   MediumProduct Analytics & Business CaseProduct AnalyticsUber-specific

   Context: Include cohort trends, leading indicators, competitor/substitution signals, and service quality.

   How to answer: Quantify the problem by defining 'high-value rider' (e.g., spend, frequency) and 'churn/inactivity' (e.g., no rides in X days, significant drop in spend). Calculate churn rates for this segment and compare to other segments or historical benchmarks. To identify drivers, conduct cohort analysis based on acquisition date or last activity, and perform a deep dive into rider behavior preceding churn. Analyze product usage (e.g., feature adoption, ride types, booking patterns), support interactions, and feedback for commonalities among churned high-value users, potentially using A/B test data or survey results.

10. Q10

    You own the weekly business review for Rides. What metrics go on the first page, and what drill-downs should be ready?

    HardProduct Analytics & Business CaseProduct AnalyticsUber-specific

    Context: Design for executive actionability rather than metric dumping.

    How to answer: A strong answer would prioritize top-line metrics reflecting Uber's core business health, starting with Gross Bookings and Trips, followed by Active Riders and Drivers. Key financial metrics like Take Rate and Contribution Margin (or similar profitability proxy) should also be present. For drill-downs, candidates should immediately consider geographic (city/region), product type (e.g., UberX, Uber Black, Pool), and cohort (new vs. existing riders/drivers) dimensions, along with supply-side metrics like driver utilization and online hours. The answer should emphasize actionable insights and the 'story' the metrics tell.

11. Q11

    You have resources for only one analysis on Driver App: improve conversion, reduce churn, improve ETA and cancellation rate, or expand monetization. How would you prioritize?

    HardProduct Analytics & Business CaseProduct AnalyticsUber-specific

    Context: Use impact, confidence, effort, risk, and strategic fit.

    How to answer: A strong candidate would prioritize based on Uber's current strategic goals, the potential impact of each analysis, and the feasibility/data availability. They would likely start by clarifying the 'current state' of the driver app and Uber's overarching business objectives (e.g., growth vs. profitability vs. market share). Then, they would evaluate each option against these objectives, considering the potential ROI, the scale of the problem/opportunity, and dependencies. For Uber, driver supply and efficiency are often critical, so improving ETA/cancellation rate or reducing churn might be prioritized if supply is constrained or inefficient.

12. Q12

    Using riders and trip_events, calculate 7-day new-user retention for Uber Eats by acquisition channel. Include a version that returns the denominator even when retained_users is zero

    MediumSQL Technical ScreenSQLUber-specific

    Context: Hypothetical Uber analytics case for Uber Eats; schemas may be simplified for an interview. Acquisition channel is stored on signup and events may be missing for retained users.

    How to answer: The candidate should first identify new users by finding the minimum `event_timestamp` for each `rider_id` in `trip_events` where `event_name` is 'eats_order_completed'. Then, they need to join this with `riders` to get the `acquisition_channel`. For retention, they'll count users who had another 'eats_order_completed' event between 1 and 7 days (inclusive) after their first order. The denominator for retention should be the total new users for each channel, which requires a `LEFT JOIN` or similar technique to ensure channels with zero retained users are still represented. Finally, group by `acquisition_channel` and calculate the retention rate.

13. Q13

    Calculate the number of distinct active days in each rider's first 30 days after signup for Airport Trips. Return the distribution by city

    MediumSQL Technical ScreenSQLUber-specific

    Context: Hypothetical Uber analytics case for Airport Trips; schemas may be simplified for an interview. Tie events to signup date and use the customer's local business date where possible.

    How to answer: A strong candidate would first identify airport trips by filtering on the `trip_type` or `destination_zone`. Next, they would calculate the `signup_date` for each rider and define a 30-day window using `DATE_ADD` or `INTERVAL`. Within this window, they would extract the distinct `trip_date` for each rider and count them. Finally, they would group the results by `city` and count the occurrences of each distinct active day count to show the distribution.

14. Q14

    Write SQL to identify where users drop in the Uber Eats funnel by app_version and device_type. Return step-to-step conversion and contribution to total drop-off

    HardAdvanced SQL & Data Modeling Deep DiveSQLUber-specific

    Context: Hypothetical Uber analytics case for Uber Eats; schemas may be simplified for an interview. The goal is to pinpoint whether a recent app release harmed the funnel.

    How to answer: The candidate should first define the Uber Eats funnel steps (e.g., App Open, Restaurant View, Cart Add, Order Place). Then, they need to calculate the count of users at each step, grouped by `app_version` and `device_type`. Step-to-step conversion is calculated as `(users_at_step_N / users_at_step_N-1) * 100`. Contribution to total drop-off requires calculating the total drop-off from the initial step to the final step, and then determining what percentage of that total drop-off occurs at each specific step for each `app_version` and `device_type` segment. This will likely involve using CTEs or subqueries to manage the step-wise calculations and aggregations.

15. Q15

    Events for Driver App are stored in UTC but business reporting uses local dates by city. Write SQL to calculate daily request-to-complete rate in local time and explain the edge cases

    HardAdvanced SQL & Data Modeling Deep DiveSQLUber-specific

    Context: Hypothetical Uber analytics case for Driver App; schemas may be simplified for an interview. Pay attention to daylight-saving changes, travel, and users without a reliable location.

    How to answer: The core of the solution involves converting the UTC `event_timestamp` to the local time of each city. This requires a mapping of `city_id` to its corresponding timezone. Once converted, the local date can be extracted to group events daily. The request-to-complete rate is then calculated as `COUNT(CASE WHEN event_type = 'completed' THEN 1 END) * 1.0 / COUNT(CASE WHEN event_type = 'requested' THEN 1 END)` per city and local date. Edge cases include handling cities with multiple timezones, daylight saving time (DST) transitions, and ensuring correct handling of `NULL` or missing `city_id` or `event_type` values.

Practice these with instant AI feedback in a live mock interview → Start a Uber Data Analyst mock

Strong DSA and scalable system design; prepare analytical/behavioral stories

Indicative Data Analyst pay in India: ~₹6–22 LPA (role-level range, not a Uber-specific figure).

Other roles at Uber

Data Analyst interviews at other companies