The PM Interview Cheatsheet with Ashutosh Rai

Most PM interview prep teaches you what to say. This teaches you how to think.

The PM Interview Cheatsheet is a practical field guide for students preparing for their first Product Management interviews.

Instead of memorising frameworks and hoping the right question appears, learn the underlying thinking that shows up across different PM interviews.

Inside, you'll learn how to handle:

01 · Product Sense

Design products by starting with the user and their problem before jumping to features.

02 · Execution / Root Cause

Debug a metric drop by clarifying, checking whether the problem is real, segmenting the data and then forming hypotheses.

03 · Metrics

Think beyond a single "North Star" number with goal metrics, guardrails and counter-metrics.

04 · Estimation

Make sensible assumptions, do clean back-of-the-envelope maths and sanity-check the answer instead of chasing the "right" number.

05 · Strategy

Understand the goal, evaluate real options, recommend one and explain the risks.

06 · Behavioural

Build honest stories around influence, failure, prioritisation and disagreement rather than memorising polished answers.

The core idea

Almost every PM interview question is testing some version of:

Can you think clearly about users and trade-offs, out loud, under pressure?

The guide gives you scaffolding without turning your answers into robotic framework recitations.

Clarify → Narrow → Think → Decide

That's the skill.

Product Sense

A simple six-step structure:

Clarify & frame → Pick a user → Find the pain → Generate solutions → Prioritise → Metric + trade-off

The emphasis is deliberately on spending time with the user and problem before touching features.

Execution / Root Cause

When a metric suddenly drops, don't start throwing out ten possible reasons.

Instead:

Clarify → Is it real? → Internal vs external → Segment → Hypothesise → Confirm

The guide gives you a structure you can practise until it becomes instinctive.

Metrics & Estimation

Learn to think in:

Goal metric + Guardrail + Counter-metric

And for estimation:

Assumptions → Calculation → Sanity check

The number is often a decoy. Your reasoning is what matters.

Strategy, Behavioural & "Why Product?"

The guide also covers:

→ Ending strategy answers with an actual recommendation

→ Preparing genuine behavioural stories

→ Talking about failure and disagreement honestly

→ Building a specific answer to "Why Product?" from your own journey

The key lesson:

A specific ordinary story beats a polished generic one.

And the page you'll want the night before

A one-page Night-Before Card covering:

Product Sense → User & pain before feature

Execution → Segment before guessing

Metrics → Goal + guardrail + counter

Estimation → Clean assumptions + sanity check

Strategy → Options, then decide

Behavioural → True stories, told clearly

Plus three habits that apply everywhere:

Clarify before answering.

Narrow before broadening.

End on a trade-off or recommendation.

Why I made this

I'm Ashutosh, an IIT Guwahati student and Product Manager.

While preparing for Product interviews and assignments, one thing became increasingly clear to me:

Frameworks are useful scaffolding. They shouldn't become the answer.

The goal isn't to announce which framework you're using.

It's to make your thinking easy for the interviewer to follow.

This isn't a collection of memorised interview answers.

It's a compact guide to the thinking underneath them.

Read it before the interview. Then go practise on something real.