Win My Interview
Library
🎯

Frameworks & Method · 8 min read

Product Manager Interview Frameworks: CIRCLES, RICE, AARRR & Metrics

Product sense, prioritization, and metrics — the frameworks PMs actually use.

PM interviews reward structure under ambiguity. The frameworks below are not scripts to recite — they are scaffolds that keep you organized while you show judgement. Use them lightly, adapt them to the prompt, and always tie every idea back to a user and a metric.

Product design: CIRCLES

Use CIRCLES for 'design a product for X' or 'improve Y' questions. The goal is to show you move from user to solution to measurement in a structured way.

ComprehendClarify the situation, goal, and constraints.
Identify userPick a specific segment; don't try to serve everyone.
Report needsList the segment's real pain points.
CutPrioritize the needs worth solving now.
List solutionsBrainstorm two or three distinct approaches.
EvaluateTrade off by impact and effort.
SummarizeRecommend one solution and the metric you'd track.

Prioritization: RICE

When asked to prioritize a roadmap or features, RICE gives a defensible score: (Reach × Impact × Confidence) ÷ Effort. Say the formula, then reason about the inputs rather than pretending to have exact numbers.

  • •Reach: how many users this affects in a period.
  • •Impact: how much it moves the goal per user.
  • •Confidence: how sure you are, as a discount on the estimate.
  • •Effort: person-months to build. Higher effort lowers the score.

Metrics: AARRR and HEART

For 'what metrics would you track' questions, structure before listing. AARRR (Acquisition, Activation, Retention, Referral, Revenue) organizes the funnel; HEART (Happiness, Engagement, Adoption, Retention, Task success) works for feature quality. Always name a north-star metric and one or two guardrails so you don't optimize a number that hurts the product.

Diagnosing a metric drop

'DAU dropped 5% — what do you do?' is an execution question. Never jump to a cause. Structure the space, then hunt.

ClarifyHow much, how fast, which metric exactly, and since when.
Internal vs externalA release, an outage, a pricing change — or seasonality, a competitor, the news.
SegmentBy platform, geography, cohort, and new vs existing users to localize it.
Hypothesize & validateForm the top one or two hypotheses and say how you'd confirm each.
💡 Interviewers are testing whether you're structured and data-driven under ambiguity, not whether you guess the 'right' cause fast.

Practice a PM mock

Run a product-sense or execution round and get an instant verdict with feedback.

Practice a PM mock →

Related guides

🧩Case Interview Frameworks: Profitability, Market Entry, Sizing, Pricing & M&A🏗️System Design Interview Primer: A Repeatable Approach🗣️How to Answer 'Tell Me About Yourself' (with a 60-Second Structure)