Product Manager Interview (+ AI PM) · Product Sense & Design · Lesson 1 of 3
Start from the user & the problem
Every product-sense answer starts the same way: who is the user, and what problem are they trying to solve? Candidates who jump straight to features fail; candidates who pick a user segment and a real, prioritized pain point pass.
- Clarify the goal: is this for growth, engagement, revenue, a mission? Ask, don't assume.
- Pick a user segment: name 2–3 segments, then choose one and justify it. Breadth then focus.
- List their needs / pain points: what do they struggle with today? Prioritize the sharpest one.
- Then brainstorm solutions for that user + that pain — not a random feature grab-bag.
The feature-first trapLeading with 'I'd add stories and a feed and dark mode' signals no user empathy. Always go user → need → solution. The interviewer is grading the reasoning path, not the feature count.
Job to be donePeople don't want a quarter-inch drill, they want a quarter-inch hole. Anchor on the job the user is hiring your product to do, and the right features fall out of it.
◆ Lock it in
- Open with who is the user and what problem — never features first.
- Name several segments, then pick one and justify; prioritize the sharpest pain.
- Frame around the job to be done, not the feature.
Feynman drill — say it out loudExplain why 'user → need → solution' beats jumping straight to a feature list in a product-design question.
Step 1 rate your confidence · Step 2 pick your answer
In a 'design a product for X' question, what should you establish before brainstorming features?
Step 1 — how sure are you?