PayPal·Product Manager·Onsite - Product Sense / Strategy·Senior

Senior

Jun 2026

Summary

PM interview at PayPal with a product analytics case set in the Uber Eats context. One question, pretty focused on diagnosing a metric drop.

Questions Asked (1)

You're a PM for Uber Eats. Cart conversion has dropped by 10% over the last 3 months. How would you go about finding the root cause?

Root Cause AnalysisProduct Analytics & Metrics

Author's notes

I started with segmentation which felt right but I jumped to hypotheses way too fast without really confirming the metric definition first.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the metric definition and confirming the drop is real and not a data artifact. Then segment the funnel and user cohorts to localize where and for whom the drop occurs, and finally generate and test hypotheses about root causes using both quantitative and qualitative data.

Pro tip: Acknowledge that a 10% drop over 3 months is significant and likely due to multiple factors; prioritize the biggest drivers first rather than trying to fix everything at once. Also, consider external factors like seasonality, competitor launches, or app store changes.

1. Clarify and Validate the Metric

Define exactly what 'cart conversion' means (e.g., from cart view to order completion) and ensure the 10% drop is accurate by checking data pipelines, tracking, and definitions.

2. Segment and Localize the Drop

Break down the metric by dimensions like platform (iOS/Android), geography, user tenure (new vs. existing), restaurant type, and time to identify where the drop is concentrated.

3. Analyze the Funnel and User Journey

Examine each step of the cart-to-order funnel (e.g., cart view, checkout initiation, payment, order confirmation) to pinpoint the stage(s) with the largest decline.

4. Generate and Prioritize Hypotheses

Brainstorm potential root causes based on internal changes (e.g., product updates, pricing, promotions) and external factors (e.g., seasonality, competition), then prioritize by impact and likelihood.

5. Test and Validate Root Causes

Use quantitative analysis (e.g., cohort analysis, regression) and qualitative methods (e.g., user surveys, session replays) to confirm or refute hypotheses, and quantify the impact of each cause.

Key Points to Mention

Define the metric precisely and check for data quality issues before diving in.
Segment the data by user cohorts, platform, geography, and time to isolate the problem.
Map the full funnel to identify which step(s) are causing the drop.
Consider both internal changes (e.g., new features, pricing changes) and external factors (e.g., seasonality, competitor actions).
Use a mix of quantitative (e.g., funnel analysis, A/B tests) and qualitative (e.g., user feedback, interviews) methods.
Prioritize hypotheses by potential impact and ease of validation, and propose next steps for deeper investigation.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.