How to Answer Product Design Questions? A Framework for Big Tech Interviews

Product Design Questions: The Most Dreaded Interview Question Type

"Please design a social product for elderly people."

The interviewer says this, gives you 5 minutes to think, then asks you to present your solution in 15-20 minutes.

This is a product design question. It carries the highest weight in big tech PM interviews and is the most dreaded question type for candidates. There's no standard answer — it tests the combined expression of your product thinking, logical ability, and communication skills.

I spent three years as a product manager at ByteDance and interviewed over a hundred candidates. I noticed a pattern: 80% of candidates perform poorly on product design questions — not because they lack ideas, but because they lack a framework.

Answers without a framework tend to be stream-of-consciousness, logically chaotic, and lacking focus. Answers with a framework, even if the ideas aren't groundbreaking, convey professionalism and structured thinking to the interviewer.

In this article, I'll share a battle-tested framework for answering product design questions, demonstrated with 5 real interview questions.

1. Three Types of Product Design Questions

Type 1: Design a Product from Scratch

"Design a second-hand trading platform for college students" "Design a product to help elderly people learn to use smartphones"

These questions test your ability to plan a product from 0 to 1.

Type 2: Optimize an Existing Product

"How would you improve WeChat Read's user retention?" "How would you optimize Meituan's delivery experience?"

These questions test your understanding of existing products and ability to improve them.

Type 3: Design a Feature/Module

"Design a learning channel for Douyin" "Design an OKR management feature for Feishu"

These questions test your feature design ability within an existing product framework.

The framework for all three types is largely the same: Define users → Analyze scenarios → Extract needs → Design solutions.

2. Universal Framework: User-Scenario-Need-Solution

Step 1: Define Target Users (1-2 minutes)

Don't rush to present solutions — first clarify who you're designing for.

Use MECE principle to segment user groups:

Using "design a social product for elderly people" as an example:

• By age: 60-70 (active seniors) vs 70-80 (homebound seniors) vs 80+ (elderly seniors)
• By location: Tier-1 cities vs Tier-2/3 cities vs rural areas
• By digital literacy: Proficient smartphone users vs basic users vs barely able to use

After segmentation, choose one core user group for deep analysis. Selection criteria: large market size, strong pain points, insufficient competitor coverage.

For example, choose "Tier-1 city, 60-70 years old, active seniors who can basically use smartphones" as the core user.

Step 2: Analyze Usage Scenarios (2-3 minutes)

When, where, and in what context would users use your product?

Continuing with the elderly social product example:

• While exercising in the park in the morning, wanting to find nearby exercise partners
• Bored at home during the day, wanting to chat and pass time
• When children aren't around, wanting to confide in and communicate with peers
• When wanting to learn new skills (calligraphy, photography), looking for like-minded people to learn with
• When traveling, wanting to find same-age travel companions

Each scenario corresponds to a core need.

Step 3: Extract Core Needs (2-3 minutes)

Extract needs from scenarios and prioritize:

Step 4: Design the Product Solution (5-8 minutes)

This is the focus of your answer — be specific down to the feature level:

Core Feature Design:

1. Interest Matching System

   • Select interest tags during registration (Tai Chi, calligraphy, photography, travel, board games, etc.)
   • Recommend "people you might know" based on interest tags + location
   • Daily recommendation of 3-5 highly matched users to reduce choice pressure

2. Voice-First Communication

   • Default communication method is voice messages (elderly people type slowly)
   • One-tap voice calling support
   • Default large font size, clean interface

3. Nearby Activity Plaza

   • Display nearby offline activities (park Tai Chi, community calligraphy classes, etc.)
   • Allow users to create their own activities
   • Post-activity mutual reviews to build trust

4. Safety Measures

   • Real-name verification + facial recognition
   • Sensitive word filtering and reporting mechanism
   • Children can link accounts to view parents' social activity (with parental consent)

Product Form: WeChat Mini Program (lower download barrier; elderly people are familiar with WeChat)

Core Metrics: DAU, average daily messages per user, activity participation rate, next-day retention rate

Step 5: Summary and Extensions (1-2 minutes)

Briefly summarize your solution and proactively raise follow-up considerations:

• Which features should the MVP include?
• How to acquire the first batch of users during cold start?
• What's the business model?

3. Five Real Question Walkthroughs

Real Question 1: Design a Study Room Reservation Product for College Students

Users: College students, especially those preparing for graduate entrance exams, civil service exams, or final exams

Core Scenarios:

• Library seats are scarce — students queue at 6 AM to grab seats
• Want a quiet study environment but don't know where seats are available
• Arranged to study with classmates but can't find adjacent seats

Core Need: Real-time seat availability → Online reservation → Timely reminders

Solution Highlights:

• Real-time seat map (similar to movie theater seat selection)
• QR code check-in/check-out; auto-release if no-show after timeout
• "Adjacent seats" option when booking for study partners
• Study time tracking and leaderboards (increase motivation)
• Integration with university academic systems; auto-extend hours during exam weeks

Real Question 2: How to Improve WeChat Read's User Activity?

Current Analysis: WeChat Read's core issue is low open frequency — many users only use it occasionally during fragmented time after downloading.

User Segmentation:

• Heavy users: Read 30+ minutes daily (maintain activity)
• Medium users: Read 2-3 times weekly (increase frequency)
• Light users: Read 1-2 times monthly (activate and awaken)
• Silent users: Haven't opened in 30+ days (recall)

Solutions for Medium Users (greatest improvement potential):

• Daily reading check-in + consecutive check-in rewards (free reading time)
• Social interaction based on reading progress ("Your friend has read to Chapter X")
• Smart daily must-read articles (5-minute short articles to lower the reading barrier)
• Reading goal setting (finish one book per week; earn badges upon completion)

Real Question 3: Design a Local Life Channel for Douyin

Users: Active Douyin users with local consumption needs

Core Scenarios:

• Want to find good nearby restaurants on weekends
• Want to know about fun local activities
• See a store review video and want to order directly

Solution Highlights:

• Independent "Local" Tab showing nearby food, drink, and entertainment content based on LBS
• In-video POI cards — tap to view merchant details, reviews, and deals
• Local influencer leaderboard encouraging local content creation
• Limited-time deals aggregation page, similar to Meituan's "Deals" channel
• Integration with Douyin Pay for content-to-transaction closed loop

Real Question 4: Design an Internal Knowledge Management Product

Users: Enterprise employees, especially new hires and cross-department collaborators

Core Pain Points:

• New employees can't find relevant documents; have to ask around to locate them
• Same questions asked repeatedly by different people with no knowledge accumulation
• Documents scattered across Feishu, Confluence, and local folders — impossible to find

Solution Highlights:

• Unified knowledge search portal (connecting all document platforms)
• AI Q&A assistant (input questions, automatically find answers from the knowledge base)
• Knowledge graph (visual display of relationships between knowledge items)
• Expert recommendations (recommend internal experts based on question domain)
• Knowledge contribution incentives (earn points for writing documents; points redeemable for perks)

Real Question 5: Design a Financial Management Product for Freelancers

Users: Freelancers (designers, programmers, writers, photographers, etc.)

Core Pain Points:

• Unstable income — don't know how much they actually earn each month
• Income from multiple platforms needs manual consolidation
• Don't know how to do tax planning; scramble during year-end tax filing
• Don't know how much to save vs. spend

Solution Highlights:

• Multi-platform income auto-sync (connect Alipay, WeChat Pay, bank cards)
• Income/expense dashboard (monthly/quarterly/annual income trend charts)
• Smart bookkeeping (photo-scan invoices, auto-categorize)
• Tax calculator (automatically calculate tax owed based on income)
• Financial health score (based on income-expense ratio, savings rate, etc.)
• Budget recommendations (suggest minimum monthly savings based on historical income fluctuations)

4. Scoring Criteria: What Are Interviewers Looking For?

5. Common Mistakes

Mistake 1: Jumping Straight to Solutions

Skipping user and scenario analysis to say "I think we should build XXX feature." This is the most common mistake and signals a lack of systematic thinking.

Mistake 2: User Analysis Too Broad

"My target user is everyone" — this equals having no target user. You must segment users and select a core user group.

Mistake 3: Feature Dumping

Listing a dozen features but only scratching the surface of each. Interviewers prefer seeing deep thinking about 3-5 core features rather than a feature checklist.

Mistake 4: Ignoring Competitors

Before designing a product, consider whether similar products exist, how they're performing, and how your solution differs.

Mistake 5: No Data Thinking

A good product design solution should include core metric definitions. "After this feature launches, I'll monitor XXX metrics to validate effectiveness" — this statement alone can significantly boost your score.

Summary

The essence of product design questions isn't testing whether you can come up with a brilliant solution — it's testing whether you can think about problems in a structured way.

Remember this framework: Users → Scenarios → Needs → Solutions.

Before interviews, practice 10-15 questions using this framework, completing each within 20 minutes. Once the framework becomes second nature, you won't panic during interviews.

Product design has no standard answers, but there is a standard way of thinking. Master the thinking approach, and you can handle any question with confidence.