TOUGH TONGUE AI
  • Home
    LogoTOUGH TONGUE AI

    RESOURCES

    Loading...

    HomeLibraryPM Interview: Root Cause Analysis - Reddit Traffic Drop

    PM Interview: Root Cause Analysis - Reddit Traffic Drop

    Practice root cause analysis with a senior PM interviewer - investigate why Reddit's traffic dropped 5% and demonstrate your systematic problem-solving and data-driven investigation skills.

    Start practice

    Covers: Product Manager, Execution, Root Cause Analysis

    Your instructions

    You're in a product management root cause analysis interview. Here's your scenario:

    "You're a PM at Reddit. Traffic is down by 5% this week compared to last week. How would you investigate?"

    Key Interview Dynamics:

    • This is a role-play interview - the interviewer acts as a data analyst
    • You must ask SPECIFIC questions to get data (e.g., "What's the week-over-week change in Google search traffic?" not "Is something wrong with search?")
    • There IS a correct root cause, but your systematic approach matters more than getting it perfectly

    Recommended 6-Step Framework:

    1. Clarify the problem (3-5 min)

      • How is "traffic" defined? (visits, unique users, pageviews?)
      • What's the exact timeframe and pattern? (sudden drop or gradual?)
      • What's the scope? (all platforms, geographies, user segments?)
      • Any historical context? (seasonal patterns, past incidents?)
    2. Form hypotheses (3-4 min)

      • Technical issues (bugs, site performance, tracking)
      • Product changes (new features, UI updates, algorithm changes)
      • Operational factors (content moderation, policy changes)
      • External events (competitors, market shifts, user behavior)
    3. Test systematically (10-12 min)

      • Start broad: Which hypothesis category seems most likely?
      • Ask for specific metrics to rule options in/out
      • Follow the data trail - if web is down but mobile is up, dig into web traffic sources
      • Look for patterns: timing, user segments, acquisition channels
    4. Refine and repeat

      • Adjust hypotheses based on data
      • Drill deeper into promising leads
      • Don't get stuck - if one path is dead, try another
    5. Identify root cause (2-3 min)

      • Synthesize your findings into a clear story
      • Explain the chain of causation
    6. Propose next steps (3-4 min)

      • Should Reddit act? Consider tradeoffs
      • Short-term vs long-term solutions
      • Stakeholder implications

    Pro Tips:

    • Think like a detective using process of elimination
    • If stuck, ask yourself: "What data would help me rule this in or out?"

    More in Product Manager Interview Prep

    • PM Interview Coach: Metrics Questions
    • PM Interview: Strategy Questions - Google Maps
    • Google PM Interview: Smell Teleportation API
    • PM Interview: Pricing Strategy - Uber Autonomous Vehicles
    • PM Interview: Growth Strategy - YouTube Watch Time
    • PM Interview: GTM Strategy - Spotify Podcasts Launch
    • A/B Testing: Google Homepage
    • PM Interview: Facebook Watch Redesign Decision
    • PM Interview: Metrics - Instagram Stories
    • PM Interview: Estimation - Google Photos Storage
    • PM Interview: Estimate Self-driving cars in US
  1. Common investigation paths: traffic sources → acquisition channels → specific segments
  2. The interviewer will guide you if you're way off track, but show your thinking first
  3. PM Interview: Favorite Product Question
  4. View the full course (60 sessions) →