gitGood.dev
← Product cases
Product DesignFoundationalFree

What's Your Favorite Product, and How Would You Improve It?

Deceptively open. They're testing product judgment, user empathy, and prioritization - not your taste.

Interview prompt

What is your favorite product, and how would you improve it?

What interviewers evaluate

  • Can you articulate WHY a product is good (for whom, what job, what makes it work)?
  • Do you identify a real user pain, not a cosmetic nitpick?
  • Do you propose improvements tied to user/business value and prioritize them?
  • Do you reason about tradeoffs and how you'd measure the improvement?

A framework to structure your answer

  1. Pick & justify - choose a product you know deeply; state who it's for and the core job it nails.
  2. Mission lens - what is the product/company trying to achieve? Frame improvements against that mission.
  3. Identify gaps - find 2-3 genuine user pain points or unserved segments (not pixel tweaks).
  4. Prioritize - pick the highest impact-vs-effort improvement and justify the choice.
  5. Detail & measure - describe the improvement and the metric that would prove it worked.

Strong sample answer

Try structuring your own answer first, then reveal a strong worked example.

Common variants

  • What product do you think is poorly designed, and how would you fix it?
  • If you were the PM for [our product], what would you change first?
  • What's a product you use daily that could be 10x better?

Pitfalls to avoid

  • Praising a product without explaining who it's for or what job it does.
  • Suggesting cosmetic changes instead of addressing a real user need.
  • Listing improvements without prioritizing or justifying.
  • Picking a product you don't actually understand deeply (follow-ups expose this).
  • Ignoring the business: an improvement users love but that hurts the model is a weak answer unless you address the tradeoff.

Likely follow-ups

  • How would you convince leadership to fund this over other roadmap items?
  • What would make you kill this feature after launch?
  • Who is the one user segment that benefits most, and why start there?