How to Answer: Favorite Product (Product Manager Interview Question)

Main ideas & lessons from the video

1) Why “favorite product” is asked

The interviewer uses this question to evaluate you in three dimensions:

• Product thinking:

  • Who the product is for
  • What problems it solves
  • How it solves them (its “first principles” / why it works)

• Strategic thinking:

  • What stage of the product life cycle it’s in
  • How success is measured
  • How you would move beyond incremental changes to the “next level”
  • How you prioritize

• Passion for great products:

  • Demonstrated understanding and enthusiasm, not generic hype

---

2) How to choose the right “favorite product”

Recommended preparation approach

Be prepared to discuss favorite products across categories:

• Software
• Hardware
• Non-tech products
• Products from the company interviewing you (if applicable)

If asked to choose multiple products

• Some interviewers ask for three
• Expect them to pick one and go deep on it

Two common traps when selecting a product

• Trap #1: Choose something too ordinary

  • Examples like iPhone or Spotify may have been discussed many times.
  • You don’t need something totally unknown, but it should enable unique insight.

• Trap #2: Choose something with low growth ceiling

  • Example mentioned: a Robo Vac
  • Limitation: there may be little room to discuss meaningful improvements, strategy, and growth.

---

3) How to answer “What is your favorite product?” (key structure)

After choosing a product, cover three points:

1. (1) Main problem it solves

   • Explain what user need/pain it addresses
   • You may use analogies to clarify
   • Example used: AllTrails helps people explore nature (like Yelp for hiking/biking/walking), including searching trails, reviews, photos, etc.

2. (2) Who uses it

   • Describe the primary audience realistically
   • Example used: AllTrails users are mainly intermediate or slightly serious hikers, not necessarily serious backpackers.

3. (3) How it solves that problem better than alternatives

   • Explain the user journey: how users search for, learn about, navigate to, record, and rate trails
   • Optionally address monetization
     • Example used: free + paid tiers
     • Paid tier: for more advanced users (offline access, more detailed maps)

Pitfalls to avoid while presenting

• Don’t over-focus on superficial benefits

  • UI/ease-of-use is not enough—go deeper into user value.

• Don’t just list features

  • Translate features into pain-point solutions for a specific user segment.

• Don’t spend too long on the intro

  • The interview depends on follow-up discussion—leave time for interviewer prompts and feedback.

---

4) How to answer the follow-up: “How would you improve it?”

Frame this as a mini product design / strategy question, not a full design project.

Avoid two extremes

• Don’t jump immediately to solutions
  • That’s a red flag.
• Don’t rush too quickly through segmentation/pain points
  • The video suggests people memorize structures, which can sound formulaic and bore/frustrate interviewers.

Step 1: Align on product goals and success (before solutions)

Discuss:

• Product goals / success definition

  • What defines success for users and the company
  • Where the product sits in its life cycle (early vs mature affects priorities)
    • Early stage: more likely growth focus
    • Mature stage: success may be framed differently

• Success indicators / North Star metric

  • What metrics the product primarily optimizes
  • Example used: AllTrails paid subscriptions:
    • MAU (Monthly Active Users): indicates retention/recurring usage
    • Paid signups: reflects how compelling paid value is

Step 2: Generate improvement ideas (3 considerations)

When proposing improvements, the video suggests:

1. Propose a strategic bet

   • Examples: new vertical, new audience, new partner
   • Example used: features targeting photo/social-media hikers
     • Identify Instagram-worthy spots using user-uploaded images
     • “Photo mode” during the hike
     • Route recommendations to get to the shot and return efficiently

2. Leverage the company’s strengths

   • Especially in larger companies: reuse assets across divisions
   • Look for: ecosystem advantages, data, flywheels, network effects
   • Example used: Kindle → broader Amazon ecosystem

3. Improve what happens before/after a key moment

   • With AllTrails: hiking day planning can extend into finding nearby restaurants after the hike

Common mistake when presenting ideas

• Over-focus on surface-level improvements (e.g., “more filters”) without linking to strategy.
• A “one-off feature” only becomes meaningful if tied to a holistic strategic plan and larger goal (e.g., increasing miles).

Also: don’t give only one idea

• Provide multiple options to show latitude and prioritization capability.

Growth strategy framing (conceptual guidance)

• Mentioning frameworks like the BCG growth-share matrix can help conceptually, but the exact structure isn’t required.
• Key idea: connect proposals to expanding market impact and strengthening leadership.

Step 3: Prioritize and recommend

Use a prioritization framework, such as:

• Impact vs. effort
  • Impact: how much the idea advances the agreed success metric
  • Effort: difficulty to build (tech readiness gaps, legal/political issues)

Then:

• Clearly state what you’re optimizing for (the success metric)
• Discuss:
  • The fastest way to test the hypothesis
  • How you would roll out iteratively over time (a phased approach)

Include risks and trade-offs

Discuss:

• Company suitability:
  • Do they have the technical skills?
  • Do they have distribution/partnership capability?
  • Any relevant macro trends?
• Justification:
  • Could competitors copy it?
• Risks/trade-offs that affect decision-making

---

Condensed “do this / avoid this” checklist

Choosing your product

• ✅ Choose something you can explain deeply and uniquely
• ✅ Ensure it has room for growth/improvement
• ❌ Avoid overly common picks (too many prior candidates)
• ❌ Avoid products with a low growth ceiling

Answering “favorite product”

• ✅ Problem it solves
• ✅ Who uses it (segment reality)
• ✅ How it solves it better than alternatives (tie features → pain points)
• ✅ Optional monetization mention
• ❌ Don’t focus on UI/ease-of-use only
• ❌ Don’t list features without user value
• ❌ Don’t overrun the intro—leave time for interviewer follow-ups

Answering “how would you improve it”

• ✅ Start with success/goals & North Star before solutions
• ✅ Propose improvement ideas using:
  • strategic bets
  • leveraging company strengths
  • enhancing before/after key moments
• ✅ Tie ideas to a larger strategy/metric (not surface tweaks)
• ✅ Provide multiple ideas, then prioritize with impact vs effort
• ✅ Discuss testing approach, phased rollout, and risks/trade-offs

---

Speakers / sources featured

• Kevin Way — Senior Product Manager at Amazon; interview coach (main speaker)
• Lift Off Product Sense — branded channel/lesson source (referenced)
• BCG growth-share matrix — named strategy framework (referenced conceptually)