PM Interview Cheat Sheet
Every PM interview round on one page: the method to use, one line per step, a short example and the mistake that costs the most points. Free to read, no sign-up. Each round links to a free lesson and practice questions.
Updated November 10, 2026 · From the PMInterviewKit course
Print it: the two-page PDF
The same sheet, laid out for paper. Read it the night before your interview.
Every round
Eight habits every strong answer shares
Whatever the round, interviewers score how you think: structure, judgment, rigor and how clearly you say it. These eight moves show all of it.
- Clarify. Ask two or three questions whose answers would change what you say. No more.
- Assume. Say everything else out loud as an assumption the interviewer can correct.
- Announce. Tell the interviewer your route before you take it.
- Choose. Pick one option and give the reason, every time.
- Trade off. Name what your choice costs.
- Quantify. Put a rough number on size, impact or the goal.
- Check in. Pause at the joints so the interviewer can steer you.
- Land. Finish with a short summary of the choices you made.
Module 1
Product sense: the Design Ladder
- FrameAsk what would change the design, state the rest, set a goal for the company and the user, and say your route.
- PersonList two to four user groups by what they are trying to do. Pick one and say why.
- PainWalk through before, during and after the task. Rank pains by how often they happen and how much they hurt.
- OptionsOffer three kinds of fix: near (the obvious one), far (ambitious) and sideways (a different angle).
- BetScore the options on value, effort and risk. Pick one and say what you give up.
- ProofOne headline metric, two helpers that explain it, one guardrail you refuse to harm.
- Walk downRead your six commitment sentences back in order. That is your summary.
Example
Solo night runners: design for people who run before dawn; the pain is that nobody knows if something goes wrong; bet on an automatic check-in that alerts a friend when a run overruns, accepting some false alarms.
Most common mistake
Naming features in the first minute, before a user or a pain. Nothing was chosen, so there is no judgment to score.
Module 2
Metrics: pick the metric: Value Moment
- Name the valueWho gets what from the product, in one sentence. Name both sides of a marketplace.
- Find the momentThe action that shows a user just got that value, not that they opened the app.
- Make it a numberDecide what you count, over what window and with what qualifier. Match the window to how often the value happens.
- Stress-test itDoes it rise only with real value? Can a team game it? Does it lead revenue and retention? Will it move within weeks?
- Guard itAdd one to three guardrails that catch the damage if a team chases it too hard.
Example
A recipe app: a saved recipe is a promise and a cooked one is the value, so steer by recipes cooked per week, guarded by unsubscribes from its reminder emails.
Most common mistake
Reaching for revenue, sign-ups or plain daily users by reflex. They lag, only ever go up, or count opens that gave nobody anything.
Module 2
Metrics: diagnose a change: Change Drill
- Check it’s realRule out logging, pipeline and definition changes before you hunt for causes.
- Size itMeasure how large it is, when it started, whether it was a step or a slide, and which other numbers moved.
- Slice itSplit by platform, region, user type and the metric’s parts until you find where the change lives.
- Line up suspectsInternal changes (releases, experiments, prices) and external ones (season, competitors, OS updates) that fit the timing and the slice. Rank them.
- Settle itName the likeliest cause, how you would prove it, what you would do, and whom you would tell.
Example
Sign-ups down 12% since Tuesday: logging is unchanged, the drop is all on Android, and Tuesday’s release changed the sign-up screen, so roll it back behind a flag and confirm with tomorrow’s numbers.
Most common mistake
Guessing at causes (a competitor, the weather) before checking the drop is real and finding where it lives.
Module 3
Estimation: the five-step estimate
- ClarifyPin down the unit, the place, the time period and what counts.
- StructureSay and write the equation before any number goes in.
- AssumeA round number for each part, each with a one-line reason.
- CalculateMultiply out loud, round as you go, and give the answer to one or two significant figures.
- CheckTest it from a second route (supply side, per person, an analogy) and name the assumption that moves it most.
Example
Weekday bike-share rides in a fictional city of 1 million: 1 million × 2% who ride × 2 rides each ≈ 40,000; check: 5,000 bikes × 8 rides a day ≈ 40,000. All round numbers, chosen for easy arithmetic.
Most common mistake
Multiplying numbers as they occur to you before the equation is set, then skipping the check, so a tenfold error goes unnoticed.
Module 4
Behavioral: the five-beat story
- HeadlineAnswer the question and give away the ending in one or two sentences.
- StakesTwo or three sentences: your role, the situation and what was on the line.
- MovesThe two to four decisions you made and why, plus one path you chose not to take.
- ResultWhat changed, with a number, and what didn’t work.
- LessonThe takeaway, and a later moment when you put it to use.
Example
Headline: “I pushed back on a launch date our VP had announced, and we shipped two weeks later with half the support tickets we had forecast.”
Most common mistake
A minute of company background before anything happens, then “we” all the way through, so the interviewer can’t tell which decisions were yours.
Module 5
Product strategy: the Spoken Memo
- DecisionRestate the prompt as a decision with a goal, a time frame and constraints.
- GroundLook through three lenses (customers, market, us) and label your assumptions.
- OptionsThree or four real options, always including a baseline such as staying the course.
- CallCompare them on customer value, right to win, and prize versus cost and risk. Pick one.
- ProofThe top risks, a cheap test for each, and the result that would make you stop.
Example
Should a fictional e-bike brand sell a monthly subscription? Goal: more riders within two years. Call: a one-city pilot with repairs included, stopped if cancellations pass a line agreed up front.
Most common mistake
A tour of everything you know (market size, a SWOT grid, five competitors) with no decision at the end.
Module 6
Technical: Goal, Path, Pressure, Call
- GoalWhat the system is for, in user terms, plus one or two questions about scale or scope.
- PathTrace the main flow from the user’s action to the result, in boxes and arrows, not code.
- PressureWhere it strains. Pick the two or three of scale, speed, failure, cost, abuse and privacy that matter here.
- CallDecide the key trade-off, say what you give up and how you would know it worked.
Example
Photo upload in a social app: the phone shrinks the image and sends it in the background while the post appears at once marked “sending”, trading a rare failed post for an app that feels instant.
Most common mistake
A jargon dump (microservices, queues, a named database) with no user, no flow and no decision. Know everything you say one level deeper than you say it.
Module 7
AI product: the Five Gates
- JobWho the user is, the task, and what a good outcome looks like for them.
- FitIs AI the best tool here? Which capability: generate, summarize, extract, classify, search or act?
- FailureWhen the model is wrong, what happens, and how the design catches, shows or recovers from it.
- ProofWhat you test before launch and what you measure once real users arrive.
- ShipCost, speed, what could go badly wrong, and how you roll it out. For a metric drop, walk the gates in reverse.
Example
AI replies to customer reviews for small restaurants: it drafts, the owner approves every reply, and reviews that mention illness or refunds never get a draft.
Most common mistake
Designing only the happy path: talking about metrics before saying what happens when the model gets it wrong.
Module 8
Company research: the loop map
- RowsOne row per stage: recruiter screen, any exercise, each interview in the loop.
- What I knowFormat, length, who you meet and what it tests.
- Source and confidenceTrust your recruiter first, the company’s own pages second, the job description third, forums last.
- What I’ll prepareTurn every row into a concrete practice task.
- GapsEvery low-confidence cell becomes a question for your recruiter.
Example
“Loop: execution | metrics case | job description says data-driven | medium | one metric-drop case and one goal-setting case.”
Most common mistake
Memorizing a forum list of a company’s supposed questions and practicing only those.
Module 9
Practice: the self-grading rubric
- Out loud, timedSpeak every rep, on a timer that matches the round.
- RecordRecord it on your phone and listen back within the hour.
- Score five thingsFraming, structure, depth, judgment and communication, each 1 to 4, for a total out of 20.
- Quote yourselfBack each score with what you actually said, so scores don’t drift upward.
- One focusWork on your lowest dimension next session. Watch the lowest score, not only the total.
Example
“Judgment: 2. Listed three options at 14:30 and never picked one.”
Most common mistake
Rehearsing in your head on a walk. Interviews test speaking under time pressure, and silent practice hides the gaps.
Module 10
Resume and offer: Lead with evidence, then ask
- Resume bulletLead with the result, add a number, say what you did, and show the scale.
- Recruiter screenA 90-second background, short answers backed by evidence, and your own questions about the process.
- ReferralGive the person a specific reason to vouch for you, then one easy request.
- NegotiationShow you want the job, state your evidence (market data or a competing offer), make a specific ask, then stop talking.
Example
“Cut checkout drop-off from 38% to 29% by replacing a five-step form with one page, across 60,000 orders a month.” (fictional)
Most common mistake
Bullets that list responsibilities, and vague asks such as “Is there any flexibility?” that get small answers.
CIRCLES method vs the Design Ladder
The CIRCLES method is a framework for product design questions from Lewis Lin’s book Decode and Conquer. Its seven letters stand for comprehend the situation, identify the customer, report the customer’s needs, cut through prioritization, list solutions, evaluate trade-offs and summarize your recommendation. It is popular for a good reason: it walks you from the prompt to a recommendation in an order interviewers can follow.
The Design Ladder, the method our product sense module teaches, follows the same arc in six rungs. Here is how the two line up.
| CIRCLES step | What it asks of you | Design Ladder rung |
|---|---|---|
| Comprehend the situation | Clarify the prompt, the goal and the constraints | Frame |
| Identify the customer | Choose who you are designing for | Person |
| Report the customer’s needs | Lay out what that customer needs | Pain |
| Cut through prioritization | Decide which needs matter most | Pain (the ranking) |
| List solutions | Come up with ways to meet the top need | Options |
| Evaluate trade-offs | Weigh the pros and cons of each | Bet |
| Summarize your recommendation | Close with what you would build | Walk down |
| (no letter) | How you would measure success | Proof |
What the Design Ladder adds
- A sentence you commit to at every rung, such as “I’ll design for first-time owners because…”. You jot each one down, so your summary is a read-back, not something you compose under pressure.
- Three kinds of options: near, far and sideways. It stops you offering three versions of the same idea.
- The trade-off said out loud. The Bet rung always names what you give up by choosing.
- Measurement as its own rung. None of the CIRCLES letters is about metrics, so many candidates tack them on at the end. Proof asks for one headline metric, two helpers and one guardrail.
- A time budget for a 30-minute question, so you don’t run out of time before the choice.
Already fluent in CIRCLES? Keep it and borrow the habits above. Starting fresh? Six rungs are fewer to hold in your head under pressure. Either way, the free Design Ladder lesson shows the whole method on a worked example.
CIRCLES is Lewis Lin’s framework. PMInterviewKit is not affiliated with Lewis Lin or Decode and Conquer.
STAR vs the five-beat story
STAR stands for situation, task, action, result. It is the most widely used shape for behavioral answers, and some large companies recommend it by name on their own careers pages (see what four large companies publish). It is a sound base. In practice it tends to cause three problems: the situation and task become a minute of background, the action drifts from “I” to “we”, and the answer stops at the result, so the interviewer has to ask what you learned.
The five-beat story builds on the same context, action and result, but reorders them and adds a beat at each end.
| STAR | Five-beat story (about two minutes) |
|---|---|
| (no step) | Headline: answer the question and give away the ending first |
| Situation and Task | Stakes: two or three sentences on your role and what was on the line |
| Action | Moves: the decisions you made and why, plus one path you chose not to take |
| Result | Result: a number, plus what didn’t work |
| (no step) | Lesson: the takeaway, and a later moment when you put it to use |
If an interviewer asks for STAR, give them STAR: the beats map straight onto it. Still open with a one-line headline, keep the situation and task to three sentences, say “I” for your own decisions, and finish with the lesson. The free behavioral lesson shows a weak and a strong answer to the same prompt.
Questions
Is the PM interview cheat sheet free?
Yes. The whole sheet is on this page, free to read and share. The printable two-page PDF is free too; we ask for your email so we can send occasional PM interview tips, and you can unsubscribe anytime.
What is the CIRCLES method?
CIRCLES is a seven-step framework for product design questions from Lewis Lin’s book Decode and Conquer: comprehend the situation, identify the customer, report the customer’s needs, cut through prioritization, list solutions, evaluate trade-offs and summarize your recommendation. Our Design Ladder follows the same arc and adds a commitment sentence at each step, three kinds of options and a measurement step.
Is the STAR method enough for PM behavioral interviews?
STAR (situation, task, action, result) is a sound base and some companies ask for it by name. In practice it invites long setups, drifts into “we”, and stops before reflection. The five-beat story keeps STAR’s core and fixes those three gaps: lead with the ending, name an option you rejected, and close with the lesson.
How should I use this cheat sheet before an interview?
Read the eight habits, then the round you are about to face. Pick one practice question, answer it out loud on a timer, and grade yourself with the five-dimension rubric. The night before, read only the method lines.
Practice it out loud
200 free questions, each with a first move and an answer outline.