← Stripe Interview Insights

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

SeniorPrefer not to say
May 2026

Summary

Stripe PM interview, just one question but it's the kind that spirals fast if you're not careful. Felt like a diagnostic exercise more than a conversation.

Questions Asked (1)

Q1

You're a PM at Lyft. Ride requests in a particular city are down 5% compared to last period. What's going on?

Product Analytics & MetricsRoot Cause Analysis
Author's notes

Classic metrics drop question but I fumbled the structure early.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the metric definition and scope (e.g., 5% decline in what exactly, over what period, and in which city). Then systematically break down the metric into its components (supply, demand, and marketplace dynamics) and hypothesize potential root causes. Prioritize hypotheses based on data and validate with quick analyses before proposing solutions.

Pro tip: Always anchor your analysis in the context of Lyft's two-sided marketplace: a decline in ride requests could be due to demand-side factors (fewer riders) or supply-side factors (fewer drivers leading to longer wait times and lost requests). Also, consider external factors like seasonality, weather, or competitive actions.

1. Clarify the metric and scope

Ask clarifying questions to understand what 'ride requests' means (e.g., total requests, completed rides, or app opens), the time period, and the city. Confirm if the 5% decline is statistically significant and if it's a trend or a one-time drop.

2. Segment the data

Break down the decline by dimensions such as rider demographics, location (e.g., neighborhoods), time of day, day of week, ride type (e.g., Lyft Line, Lux), and acquisition channel. This helps identify if the decline is broad or concentrated.

3. Analyze supply and demand factors

Investigate both sides of the marketplace: demand (e.g., fewer app opens, lower conversion, increased cancellations) and supply (e.g., fewer active drivers, longer ETAs, higher prices). Check for changes in driver incentives, pricing, or product features.

4. Consider external and internal factors

Look at external factors like weather, local events, holidays, competitive promotions, or regulatory changes. Internally, review recent product updates, marketing campaigns, or pricing changes that could impact ride requests.

5. Prioritize and validate hypotheses

Rank hypotheses by likelihood and impact, then validate with data (e.g., A/B tests, cohort analysis, correlation studies). If data is inconclusive, propose further research or experiments.

Key Points to Mention

  • Two-sided marketplace dynamics: supply (drivers) and demand (riders) must be balanced; a decline in requests could be due to supply shortages causing longer wait times and lost demand.
  • Segmentation: break down by geography, time, user cohorts, and ride types to isolate the cause.
  • External factors: seasonality, weather, local events, competitor actions (e.g., Uber promotions), and regulatory changes.
  • Internal factors: recent product changes, pricing updates, marketing campaigns, or driver incentive programs.
  • Metric definition: clarify what 'ride requests' means (e.g., total requests vs. completed rides) and ensure data accuracy.
  • Hypothesis-driven approach: form hypotheses, prioritize, and validate with data before jumping to solutions.

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