Product Manager Interview (+ AI PM) · The PM Role & Interview Loop · Lesson 1 of 2
What a PM actually does
A product manager owns the why and the what of a product — the problems worth solving and the outcomes to hit — while engineering owns the how and design owns the experience. The PM has responsibility without authority: you drive outcomes through influence, clarity, and prioritization, not by giving orders.
The job is often framed as sitting at the intersection of business, technology, and user experience — making the call on what to build next so that user value and business value compound together.
- Discovery: find and validate the problem — talk to users, read data, size the opportunity.
- Definition: turn a problem into a crisp goal, success metric, and scoped solution.
- Delivery: partner with eng/design to ship, cut scope sanely, and unblock.
- Measurement: define success up front, then check whether the outcome moved.
Outcomes, not outputJunior PMs talk about features shipped. Strong PMs talk about problems solved and metrics moved. In every answer, anchor on the user problem and the outcome — the feature is just the means.
◆ Lock it in
- PM owns the why/what (problem + outcome); eng owns how, design owns experience.
- Responsibility without authority — you lead through influence and prioritization.
- Anchor on outcomes (metrics moved), not output (features shipped).
Feynman drill — say it out loudExplain what a PM is responsible for to someone who thinks the PM is 'the boss of the engineers'.
Step 1 rate your confidence · Step 2 pick your answer
What best captures the core of the PM role?
Step 1 — how sure are you?