Product sense is the round that decides it. Interviewers want a framework you actually use, a user you can name specifically, and a metric you can define precisely enough to argue about.
Product loops are conversations with structure hidden inside them. The product-sense round wants a framework you actually use rather than one you have memorised, and the behavioral round wants metrics you can define precisely.
The most common failure is answering as a user rather than as an owner: describing what would be nice, with no reference to who it is for, what it costs, or how you would know it worked.
Each round is run by the interviewer built for it, with its own scoring axes — not one generic interviewer asked to change subject.
Relentless STAR structure, metric definitions, and edge cases.
Scored on Structured communication · Product & metrics rigor · Ownership & confidence
Relentless STAR structure, metric definitions, and edge cases.
Scored on Structured communication · Product & metrics rigor · Ownership & confidence
Customer insight, prioritization, product judgment, and execution trade-offs.
Scored on User-first framing · Prioritization & execution · Product judgment & influence
Structured cases — framework, math, and a crisp recommendation.
Scored on Structure & communication · Analytical rigor · Business judgment & poise
Customer insight, prioritization, product judgment, and execution trade-offs.
Scored on User-first framing · Prioritization & execution · Product judgment & influence
Six you can expect, in the register interviewers actually use. Answer them out loud before you read the next section — reading a question and answering one are different skills, and only the second is marked.
The gap between these two is most of your score, and it is easier to see than to be told.
“Pick a product you use daily and tell me what you would change.”
A list of features that would be nice, with no user named and no metric attached. It is the single most common failure in the product-sense round.
Name the specific user and the job they are hiring the product for, the friction you have actually observed, one change, the metric that would move, and what would tell you within two weeks that you were wrong. Owner, not user.
The post-mortem nobody sends you. These are specific to this loop rather than general interview advice.
For Product Manager, a general round runs with Maya — relentless star structure, metric definitions, and edge cases. It is the fastest way to find out which round you actually need to work on. The first session is free.
Practise a Product Manager interview →Before you practise, it is worth reading how the common rounds are marked: tell me about yourself, behavioral questions and STAR, and system design.