Interview Drills — Product Sense / Design

Open-ended interview questions. Each has a Framework (the structure a strong answer follows), a Model answer (a concise example), and a Rubric (what an interviewer listens for). Practice thinking aloud and always tie back to a user and a metric. The app can role-play these as mock interviews (see mock-interview.md).

The universal product-sense structure: Clarify the goal → pick a user segment → find their problems → brainstorm solutions → prioritize one or two → define a success metric. Use it on almost any "improve/design" question.

D1

difficulty: easy
concept: product-sense-interview How would you improve a product you use every day?
Framework: Name the product and its goal → pick one user segment → identify 2–3 real problems that segment faces → propose solutions → prioritize one (value vs. effort) → state the metric it should move.
Model answer: "Take a maps app; goal: get people where they're going easily. Segment: daily commuters. Problem: they repeat the same trips but re-enter them each time. Solution: one-tap saved commutes with live delay alerts. I'd prioritize this (high value, modest effort) and measure repeat-trip completion time and commuter week-4 retention."
Rubric: Strong answers clarify the goal, pick a specific user, ground improvements in real problems, prioritize with reasoning, and name a metric. Weak answers list random features with no user, no prioritization, and no metric.

D2

difficulty: medium
concept: product-sense-interview Design a product for a specific audience — e.g., helping elderly people stay connected with family.
Framework: Clarify scope/goal → deeply consider this audience's needs and constraints → prioritize the top problem → design a simple solution for it → success metric → note one accessibility/edge consideration.
Model answer: "Goal: reduce isolation for less tech-comfortable elderly users. Top problem: video calls are too fiddly. Solution: a one-button device/app that auto-connects to a pre-set family group, large UI, no logins. Metric: weekly successful calls per user. Accessibility: large text, voice prompts, works for low vision/dexterity."
Rubric: Strong answers show genuine empathy for the specific audience, pick one problem rather than boiling the ocean, keep the solution simple and usable, and consider accessibility. Weak answers ignore the audience's real constraints or design for a generic user.

D3

difficulty: medium
concept: product-sense-interview What's a product you love, and how would you improve it?
Framework: Briefly say why it's great (shows product taste) → pick the user segment you'll focus on → find a real unmet need → propose and prioritize an improvement → metric.
Model answer: "I love a note app for its speed. Segment: students. Unmet need: turning messy notes into study material. Improvement: auto-generate quiz questions from a note. Prioritize as a high-value differentiator; measure notes-converted-to-study and student retention."
Rubric: Strong answers articulate why it's good (taste), then improve based on a real user need with a metric. Weak answers gush without specifics or propose improvements unconnected to a user problem.

D4

difficulty: medium
concept: product-sense-interview How would you improve our product? (interviewing at a specific company)
Framework: Show you researched it (what it does, who for) → clarify the goal you'd optimize → pick a user segment → a real problem you (or reviews) noticed → a prioritized improvement → metric. Be humble ("I'm an outsider, so I'd validate this").
Model answer: "From using it, [product] helps small teams plan work; goal: faster onboarding. New admins seem to struggle setting up their first project. I'd add a guided setup with a template; measure time-to-first-project and team activation. I'd validate this with onboarding data and a few user chats first."
Rubric: Strong answers prove genuine research, pick a real problem, prioritize, name a metric, and stay appropriately humble about validating. Weak answers show no homework or criticize without a user/metric basis.

D5

difficulty: hard
concept: product-sense-interview Design an app for commuters.
Framework: Clarify (which commuters? car/transit? goal?) → pick a segment → enumerate their key problems → prioritize the most painful → design for it → metric → one risk to validate.
Model answer: "I'll focus on public-transit commuters; goal: reduce stress. Biggest problem: uncertainty about delays. Solution: a personalized live commute view with proactive delay alerts and alternatives. Metric: daily active commuters and reduction in missed connections. Risk to validate: that real-time data is reliable enough in their city."
Rubric: Strong answers narrow scope deliberately, prioritize among problems, design for the top one, name a metric, and flag a key risk. Weak answers stay generic ("an app with everything"), skip prioritization, or never define success.

D6

difficulty: hard
concept: product-sense-interview Pick a product you think is poorly designed and fix it.
Framework: Name it and the specific usability/value problem (be concrete, not "it's ugly") → who it hurts and why → the root cause → a prioritized fix → how you'd measure the fix worked → acknowledge a trade-off.
Model answer: "A parking-payment app: the biggest problem is that paying takes too many steps while you're standing in the cold. It hurts occasional users most. Root cause: it asks for full re-entry each time. Fix: remember the car and payment, enabling two-tap pay. Measure: time-to-pay and completion rate. Trade-off: storing details needs careful security and consent."
Rubric: Strong answers identify a specific problem (not taste), reason about who/why/root cause, propose a prioritized fix with a metric, and note a trade-off. Weak answers offer vague aesthetic complaints or fixes with no measurement.