product-sense-interview-answer

Solid

Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.

Web & Frontend 5,079 stars 645 forks Updated 3 weeks ago NOASSERTION

Install

View on GitHub

Quality Score: 87/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Purpose Help PM candidates and interview coaches structure product-sense answers that sound strong out loud, not just on paper. Use this when practicing prompts like "How would you improve X?", "Design a product for Y", or "What would you build next for Z?" This is not a memorize-and-recite script. It is a reasoning scaffold that prevents solution-jumping, forces real prioritization, and leaves the interviewer with a clean story they can follow. ## Key Concepts ### What Product Sense Interviews Actually Test Strong product-sense answers do more than generate ideas. Interviewers are usually testing whether you can: - Clarify ambiguous prompts without getting stuck - Tie user value to market or business logic - Segment thoughtfully instead of talking about "everyone" - Prioritize one pain point instead of describing ten equally - Make tradeoffs explicit when choosing an MVP - Communicate clearly under time pressure ### The Six-Part Answer Spine 1. **Clarify** - Reduce ambiguity, define scope, and state assumptions. 2. **Rationale** - Explain why the problem matters now for the market and, if relevant, the company. 3. **Product Goal** - Define the user outcome you want to create before talking about features. 4. **Segmentation** - Choose who to serve first and show why that target wins. 5. **Pain Points** - Map the journey, name the main frictions, and pick the one worth solving first. 6. **Solution** - Generate distinct options, compare them, and commit to one MVP wi...

Details

Author
deanpeters
Repository
deanpeters/Product-Manager-Skills
Created
4 months ago
Last Updated
3 weeks ago
Language
Shell
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category