PG Product Gym
Back to Library
Library rep  ·  Monday, May 25

Ben Erez on analytical thinking interviews: stop hunting for the right answer, start generating the right signals.

Kettlebell Coach
Read first. Then rep it.
Ready to apply this idea?
Five application reps based on what Ben Erez (via Lenny Rachitsky) discussed.
Practice this insight
Based on Lenny’s
Newsletter · Ben Erez (via Lenny Rachitsky) · Jul 1, 2025

The definitive guide to mastering analytical thinking interviews

Start from the original episode or newsletter, then use the ideas below in the reps.

Read on Lenny’s

Key ideas to remember

  1. 01 Before your next mock or real AT interview, write your standard 4-point game-plan sentence in advance. Open every interview with it. The first 60 seconds is where most candidates lose the loop.
  2. 02 Practice the assumptions step in isolation. Take three random products this week and write three scope-narrowing assumptions for each in under 90 seconds. This is the muscle.
  3. 03 Stop trying to find the 'right' North Star. Define a North Star *with guardrails*. The guardrails are where senior PMs are graded.
  4. 04 Run a 35-minute timer in your next mock and force a transition check-in at minute 7, 17, 27. The signal interviewers want is structure, not depth on any one section.
3-minute summary

Ben Erez — decade in product at Facebook, first PM at three startups, full-time PM-interview coach — argues that most candidates fail analytical thinking (AT) interviews not because their answer is wrong, but because they treat the interview as a casual conversation about a product instead of a structured game where the interviewer is trying to capture specific signals.

The AT interview's job: assess your ability to 'understand a product in the context of its broader company and its market, establish metrics to track success, identify team goals, and evaluate tradeoffs in a structured way.' Typical questions: 'How would you measure success for Spotify?' / 'Set a goal for Instagram Reels.' / 'What should be the North Star metric for DoorDash?'

Erez's framework — what to do, in order, in the 35 minutes you actually have:

  1. Assumptions and game plan (first minute). State a handful of assumptions that narrow scope without limiting the solution space. Then explicitly outline how you'll spend the time: 'I want to start by reviewing the product's landscape and reason for existing, then identify key stakeholders and ecosystem health metrics, define a North Star metric with guardrails, and finally set specific team goals.'
  2. Linear flow. Product rationale → stakeholders + ecosystem metrics → North Star + guardrails → team goals. Tradeoffs threaded throughout.
  3. Transition check-ins. At each section boundary, pause, gather your thoughts, and confirm the interviewer is following before proceeding.
  4. Inner time cop. 45-minute slot, 35 minutes of working time. Run your own clock.

The central reframe: 'the interviewer won't be looking for a 'correct' answer — rather, they're evaluating your thought process.' Most candidates jump to goals or metrics. The signal is in the structure, the assumptions, and the game plan.

For a mid-level PM preparing for the next interview loop: this is a week-by-week practice. Drill the assumptions step. Memorize the linear flow. Run mocks where you deliberately announce the game plan in the first 60 seconds.

Kettlebell Coach
This is where the reps count.
Practice the insight now
Turn the operator summary into five product decisions.
Practice this insight