Product Manager Interview Copilot Execution, sense, strategy — one frame.

1. 01

   Execution rounds — improve / launch / metrics

   "How would you improve Instagram Stories?" — the copilot does not start with CIRCLES. It starts with: who is the user, what is their job-to-be-done, what is the metric this would move, what is the priority frame. The framework comes second, the user empathy first.
2. 02

   Product-sense rounds — persona-anchored

   Generic "design a product for X" answers fail at FAANG PM loops because they skip persona depth. The copilot enforces the persona anchor — name, context, jobs-to-be-done, anti-jobs, current alternatives, switching cost — before any solutioning.
3. 03

   Strategic / market-sizing rounds

   When the interviewer says "size the market for X", the copilot walks the structured estimate: top-down vs bottom-up, the population anchor, the adoption rate, the monetisation, the sensitivity check. Without leading you into a math-only answer that misses the strategy.
4. 04

   Analytical rounds — SQL + metric definition

   PM loops increasingly include SQL. The copilot recognises the editor (Mode, Hex, generic SQL pad) and surfaces hints for the canonical analytics patterns: cohort retention, funnel conversion, attribution, anomaly detection — and the metric-definition decisions sitting under each query.
5. 05

   Behavioral STAR — PM-specific

   Stakeholder conflict, scope cut, prioritisation against the CEO, post-launch failure — these are the four PM-specific behavioral prompts. The copilot has scaffolds for each, calibrated to the seniority you are interviewing at.
6. 06

   Level-calibrated scoping

   APM answers focus on user empathy + clear thinking. Senior PM answers add team coordination + metric instinct. GPM / Director answers add cross-team strategy + business judgement. The copilot adjusts the scope of the answer to the level you target.

PM loops score on framing, not framework recall.

User-first scaffolds. Calibrated APM → GPM.