Problem This Solves
Product questions are "the heart and soul of the PM interview" — they directly test what a PM does: design, build, and improve products. Candidates fail these questions not because they lack good ideas, but because they dive into features before understanding users and goals. The classic failure: Jessica listed feature ideas in an Apple/iTunes interview without a structured, user-focused approach and did not advance to the next round.
Key Principle
Start with users and goals — never features. Every proposed feature must be explicitly tied to a specific user use case or underlying motivation. "It's not about what you want the product to be. It's about what the user wants."
Product questions appear in three forms, all requiring the same user-centered discipline:
- "How would you design ___?"
- "What would you improve about ___?"
- "What is your favorite product and why?"
Good Examples
Design a Product (7-step framework):
- Ask clarifying questions about who the user is, what form the product takes, where it is used
- Announce your structure to the interviewer before executing it
- Identify all users (primary, secondary) and the customer — these may differ
- Identify use cases and underlying motivations (not just surface tasks)
- Assess how well the current product serves those use cases — find gaps
- Propose features tied explicitly to unmet use cases or goals
- Wrap up with a summary of the proposed solution
Example: Designing an alarm clock for the blind — the candidate identifies both the blind user (primary) and their sighted partner (secondary user who must also operate the device), then proposes features that serve both.
Improve a Product (5-step framework):
- What is the goal of the product? (Not its features — Facebook's goal is connecting people, not posting status updates)
- What problems does the product face? (Expand user base, boost engagement, increase revenue, improve conversion)
- How would you solve this? (Offer both bold/innovative and small/iterative options with pros/cons)
- How would you implement? (Discuss technical/business challenges; propose small rollouts to reduce risk)
- How would you validate? (Define specific metrics; anticipate side effects)
Favorite Product (4-step framework):
- What user problem does it solve? (underlying goal, not surface feature)
- What makes it uniquely powerful? (data advantage, interface, revenue model, emotional connection)
- How does it compare to alternatives? (direct and indirect)
- How would you improve it? (prepare for this follow-up)
Example answer on Quora: frames it around community learning (not Q&A), contrasts it against Google Search on three specific weaknesses (keyword-based search, unverified authorship, inaccessible non-web-creator knowledge), and signals genuine personal passion.
User vs. Customer distinction applied: For a children's calculator: the child is the primary user, the teacher is a secondary user, and the parent is both a user (during homework help) and the customer. A design that ignores the teacher or parent is incomplete.
Bad Examples
- Listing features immediately without identifying users or goals first (the Jessica/iTunes failure pattern)
- Designing for your own preferences rather than the target user's needs
- Neglecting secondary users (designing a blind person's alarm clock without considering the sighted partner who must also use it)
- Picking a "favorite product" that sounds impressive rather than one you genuinely love — lack of authentic passion is visible to interviewers
- Proposing solutions without discussing tradeoffs or validation metrics
- Treating features as goals: "Facebook allows you to post status updates" is not Facebook's goal
Key Quotes
- "The product question is the heart and soul of the PM interview. It directly gets at what a PM does: design, build, and improve products."
- "While these questions sound different, they have one very important aspect in common: You need to understand and focus on the goal."
- "Remember: it's not about what you want the product to be. It's about what the user wants."
- "The customer is the person paying for the product; the user is the one using it."
- "Ultimately, these design questions are getting at how well you can show user empathy."
- "A good PM knows he's not always right and that his suggestions are little more than an educated guess."
- "You want your passion for this product to come out. Don't pick something because it's the 'right' product if it's not the right one for you."
- "Simplicity is a good thing in design."
Rules of Thumb
- Signal your structure explicitly before executing it: "Let me start with the product's goals, then move to issues, then solutions."
- Tie every feature proposal to a named use case or user goal — make the connection explicit, not implied
- Prepare at least six products before any PM interview: one online, one offline/physical, one recently purchased, your favorite, a well-designed product, and the interviewing company's own product
- For each prepared product, know these seven metric categories: Users/Traffic, Conversion, Referral Rates, Engagement, Retention, Revenue, Costs
- Analyze each product on seven dimensions: Users and Goals, Strengths, Challenges, Why/Why/Why (root cause), Priorities and Values, Competitors, Tradeoffs
- Aim for at least one "wow" idea per answer — a major opportunity or killer feature — and call it out explicitly
- Always acknowledge tradeoffs; never present an idea as flawless
- Use the whiteboard to communicate designs more clearly during interviews
- Have a strong opinion and act like a product owner — interviewers want PMs with convictions
Related References
- Estimation and Market-Sizing Questions - Quantitative skills that complement product thinking
- Case and Strategy Questions - Business case questions that overlap with product strategy