What this round tests
- User segmentation: who you'd build for first and why
- Pain-point prioritisation: which job-to-be-done is hottest
- Success metrics: how you'd know it worked
What interviewers are listening for
- Concrete user picture, not generic personas
- A defended trade-off — what you'd intentionally not do
- Honest uncertainty about your riskiest assumption
Common mistakes
- Listing every feature instead of picking a wedge
- Skipping the user and jumping straight to solutions
- Vague metrics like 'engagement' without specifying inputs vs outputs
Concepts tested in product sense
Practice questions (58)
- Improve activation for a new personal finance app
- Design a product for new parents returning to work
- Design a product to prepare for a citizenship test
- Improve content discovery for a streaming service
- Build trust signals for first-time marketplace buyers
- Diagnose day-1 churn in a meditation app
- Order frequency drops in week 4 for grocery delivery
- Design a product for small landlords screening tenants
- Onboard switchers from a competitor
- Should a fitness app remove its free tier?
- Telehealth scheduling drop-off
- Design a college-application companion for high schoolers
- Reduce no-shows for at-home services
- Design a product for nurses changing hospitals
- Design a product for households tracking shared finances
- Design invoicing for freelancers
- Design a tool for renters disputing repairs
- Design investor updates for solo founders
- Help retirees stay socially connected
- Design for first-generation college applicants
- Recovery tracking for amateur athletes
- Bookkeeping for owner-operators
- Coordinate childcare across households
- Onboarding for prosumer creators
- Design a climate impact tracker for households
+ 33 more in the full bank.
Practice this round in PrepOS
Calibrate your target level, set the practice category to product sense, and the adaptive queue will surface the highest-impact reps first.
Practice product sense →