What to remember
- Treat the prompt as an ambiguous decision, not a feature brainstorm.
- Prioritize one segment and one pain point with visible criteria.
- Describe the end-to-end user journey before listing capabilities.
- Use guardrails to show that growth is not the only definition of success.
Open with the product objective
Clarifying questions should change the answer. Ask about the objective, platform, geography, time horizon, and constraints only when each response would affect your choice.
A practical opening is: I want to clarify whether we are optimizing a company outcome such as retention, or solving the user problem as broadly as possible. If the interviewer leaves the choice to you, state a reasonable objective and proceed.
Do not spend five minutes collecting facts that never appear again. Summarize the assumptions you will use so the interviewer can correct them.
Segment users by behavior and need
Demographic labels are often weaker than differences in context, frequency, ability, motivation, or risk.
- Context: where and when does the task happen?
- Frequency: is this a daily workflow or an occasional high-stakes event?
- Ability: what knowledge, access, or equipment does the user have?
- Motivation: what outcome makes the user return?
- Risk: what happens if the product is wrong or unavailable?
Prioritize pain before features
Map the current journey and locate moments of uncertainty, delay, repeated effort, exclusion, or costly failure.
Rank pain points with three lenses: user severity, frequency, and the product's ability to create a differentiated improvement. A severe problem that the company cannot address responsibly may be a poor first bet. A frequent annoyance with no meaningful outcome may also be weak.
- State the current behavior and why it fails.
- Choose one primary pain point and acknowledge what you are not solving.
- Connect the pain to the objective established at the start.
Design a coherent first release
Describe a journey: trigger, key action, feedback, recovery, and return. This produces a product rather than a pile of features.
Measure value, not button taps
Your primary metric should represent progress toward the user's job. Supporting metrics explain the journey, while guardrails reveal costs.
- Primary: share of eligible tight connections reached before boarding closes.
- Supporting: route card activation, successful navigation completion, and recovery flow completion.
- Guardrails: incorrect route reports, notification opt-outs, battery impact, and accessibility failures.
Common weak-answer patterns
Most weak answers are not missing creativity. They are missing focus and evidence.
- Serving every possible user without choosing one.
- Naming features before defining the problem.
- Using a generic engagement metric that does not represent user value.
- Ignoring trust, safety, accessibility, privacy, or operational burden.
- Following a framework so rigidly that the interviewer cannot collaborate.
Common questions
How many solutions should I propose?
Generate several possibilities privately, then present a small set and choose one. The interview is usually stronger when you explain a focused recommendation and its tradeoffs.
What if I do not know the industry?
State assumptions, use first principles, and ask for missing constraints. You are being assessed on product judgment, not on pretending to have domain knowledge you do not possess.
Should I draw the user journey?
If a whiteboard or shared document is available, a simple journey can keep the discussion coherent. Use it to reveal pain points and dependencies, not as decoration.
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.