What to remember
- Choose an objective before choosing a user or feature.
- Segment by behavior, motivation, or constraint rather than demographics alone.
- Prioritize one consequential problem and show the end-to-end journey.
- Define success and guardrails that match the user value you promised.
What product sense actually tests
The interviewer is testing a sequence of judgments, not whether you can recite a framework.
A framework can keep you from skipping a decision, but it cannot make the decision for you. If two candidates use the same headings, the stronger candidate explains why this user, this problem, this scope, and this metric deserve priority under the stated objective.
- Can you turn a broad prompt into a clear objective?
- Can you identify meaningfully different users and choose one?
- Can you distinguish a root problem from a visible symptom?
- Can you design a focused journey instead of unrelated features?
- Can you explain tradeoffs, risks, and evidence that would change your mind?
Use a seven-decision answer structure
Move through objective, users, pain points, priority, journey, tradeoffs, and measurement. Keep the discussion collaborative and summarize each choice.
- Objective: define the user and business outcome, time horizon, and important constraint.
- Users: identify segments whose needs or behavior would produce different products.
- Pain points: map the journey and identify where the goal fails today.
- Priority: choose with explicit criteria such as severity, frequency, reach, and strategic fit.
- Journey: describe how the user discovers, adopts, receives value, and recovers from failure.
- Tradeoffs: state what version one excludes and why.
- Measurement: choose one value metric and relevant guardrails.
Worked answer: improve a public-library experience
The prompt is deliberately broad. Watch how the answer narrows it before designing.
Make tradeoffs visible in the solution
A feature list hides judgment. A product concept explains what belongs together, what is delayed, and what could invalidate the idea.
Describe the core promise in one sentence, then walk through the user's first successful journey. Compare two or three plausible approaches against your objective and constraints. A strong version one tests the riskiest assumption with enough quality to create real value.
- State which segment or use case you are not serving yet.
- Separate the core value mechanism from convenience features.
- Include discovery, trust, failure recovery, and repeat use.
- Name a cheaper or manual way to test the assumption.
- Explain the condition for expanding, revising, or stopping.
Product sense questions to practice
Practice across consumer, enterprise, marketplace, platform, and public-service contexts so the method stays flexible.
After every attempt, review whether your chosen user was meaningfully different, your prioritized problem was supported, and your solution formed one journey. Repeat the same prompt with a different objective to learn how early assumptions change the product.
- Design a better planning product for families caring for an older relative.
- Improve onboarding for first-time sellers in a local marketplace.
- Build a product that helps small restaurants reduce food waste.
- Improve a developer platform for teams adopting a new API.
- Design a trustworthy AI assistant for university students.
- Improve public transport for riders with unpredictable schedules.
Common questions
How long should I spend clarifying the prompt?
Ask only questions that could change your answer. Establish the objective and major constraints quickly, then state reasonable assumptions and move into user and problem choices.
How many user segments should I list?
Three or four meaningful segments are usually enough. The point is to show distinct needs, then choose one using clear criteria, not to create an exhaustive taxonomy.
Should I draw a wireframe?
Only if the format invites it and the visual clarifies the journey. Product sense is primarily about the problem and decision. A polished screen cannot rescue weak prioritization.
What if the interviewer challenges my choice?
Treat the challenge as new evidence. Clarify the concern, test whether it changes your objective or assumptions, and either revise the choice or explain why your current priority still holds.
Research sources
Primary and institutional sources lead. Supporting reports are used only for clearly qualified patterns or changes and are labelled in their notes.
A general guide gets you started. Your dossier gets specific.
Build a cited preparation brief for your company, role, seniority, and interview stage.