ChannelPulse
Product management
The PM loop is four different interviews wearing one job title, and each one scores something different. This track builds the method each round rewards — a product-sense answer that starts with a person instead of a feature list, metrics you can decompose and defend, and a diagnosis that localises a drop before it explains one.
Most PM answers fail by being reasonable. A structured, sensible, entirely generic answer is the modal rejection, so this track drills the specific moves that make an answer yours — segments sized out loud, metrics with a stated ceiling, and arithmetic that tells you when your own proposal cannot work.
The method — rounds, product sense, metrics, diagnosis
The four things that decide a PM loop before you reach any particular question: which round you are actually in and what it scores, how to open a product-sense answer so it stops sounding like everyone else's, how to choose a metric you can decompose and defend, and how to take apart a metric drop without guessing.
-
1
Four rounds, four rubrics
A PM loop is not one interview repeated. Product sense, execution, strategy and leadership score different things, and the answer that wins one round is the answer that loses another. This lesson is how to tell which room you are in, and what that room is grading. Free -
2
Product sense, without the generic answer
CIRCLES and its cousins are fine scaffolding and terrible answers. This lesson keeps the scaffolding, then does the two things that actually separate candidates: choosing one segment for a reason you can size, and generating solutions that differ in ambition rather than in wording. Free -
3
Metrics you can decompose and defend
Naming a north-star metric is the easy half. This lesson decomposes one into inputs a team can actually move, finds out which input is worth the quarter, and then does the arithmetic that tells you whether the experiment you just proposed could ever detect the effect you promised. Free -
4
Diagnosing a metric drop
"Signups fell 8% — go." The round is lost by candidates who start guessing causes and won by candidates who localise first. This lesson is the order of operations, the contribution arithmetic that finds the responsible segment, and the mix shift that makes a metric fall while every segment improves. Free
Execution — prioritising, reading results, and shipping
The execution round is where PM candidates who interview well and work badly get found out. Three lessons on the decisions that make up the job: prioritisation defended with arithmetic and opportunity cost rather than a scoring framework; reading an experiment result that is flat, mixed, or significant-but-meaningless; and the launch decision itself — rollout, guardrails, kill criteria, and what to do when the data says one thing and the deadline says another.
-
1
Prioritisation that survives scrutiny
RICE is not an answer, it is a spreadsheet. This lesson prioritises four real candidates by expected value per engineer-week, shows that the top item's lead is robust while the middle of the list is noise, then handles the parts a scoring framework cannot — opportunity cost, dependencies, the strategic item with no measurable value, and the stakeholder you have to say no to. 24 min · app -
2
Reading an experiment result
PMs are rarely asked to design a test and are constantly asked to act on one. This lesson works through the four results you actually get — flat, mixed, significant but tiny, and significant with a guardrail regression — shows what a flat result does and does not rule out at a given sample size, and ends with the ship decision when the evidence is genuinely ambiguous. 25 min · app -
3
The launch decision
Shipping is a decision with a shape — a rollout schedule, kill criteria written before launch, an owner for the call, and a plan for the week after. This lesson builds that shape, works through the two hard cases (a deadline that arrives before the evidence, and a regression found at 25% rollout), and covers the launch questions interviewers use to find out whether you have actually shipped anything. 23 min · app
Strategy and leadership — the other two rubrics
The two rounds that are hardest to prepare because they have no framework worth reciting. A strategy answer that commits to where to play and how to win, with the competitive response and the build/buy/partner call attached; the technical fluency to hold a real conversation about APIs, data models and latency without pretending to be an engineer; and the leadership round, where every question is about a decision you made with incomplete information and someone disagreeing with you.
-
1
Strategy questions — where to play, how to win
"Should we enter this market?" is answered badly by candidates who describe the market and well by candidates who commit to a wedge. This lesson builds the market-entry answer as a sequence of commitments, sizes the opportunity as a chain you can defend, works through competitive response and build/buy/partner, and separates a real moat from a list of advantages. 26 min · app -
2
Technical fluency for PMs
A PM does not need to write the code and does need to hold the conversation. This lesson covers the concepts that come up in real trade-off discussions — the shape of a request, why the data model constrains the roadmap, what latency budgets and caching actually cost you, why estimates are wrong in a predictable direction — and the questions to ask an engineer that get you a useful answer. 25 min · app -
3
The leadership round, for PMs
The fourth PM rubric is scored on influence without authority, and the stories that evidence it are specific. This lesson covers the four questions that carry the round — disagreeing with engineering, saying no upward, a launch that failed, and a decision made without data — and what makes a PM story read as leadership rather than as coordination. 23 min · app
Work through it with feedback
Reading the pattern is step one. The app runs you through it — editable code cells, the question bank, and a mock loop that grades your answer.
Open the curriculum in ChannelPulse