(a.k.a. ) is the most common question asked during PM interviews. It should not be confused with the UI-UX or system design challenges. Here, product design is a journey where you explore diverse questions and challenges pertaining to product discovery & development. The journey begins with the search for answers to and . However, all of these need to be investigated in a limited time frame of 30-45 mins during an interview. Product design problems can be either case studies or open ended questions on technology or physical products. Product design Product sense Why, Who, What, Where, When How PRODUCT DESIGN PROBLEMS: Design an app for the Louvre Museum Design Youtube for Concert Lovers Design a Travel app for Airport Layover Design an alarm clock for blind Design a solution for gardening Design an education product for Facebook How would you improve Instagram ? How would you a design a pen for Scuba Divers ? How would you monetize Whatsapp ? If you are FB PM, how will you design a product for people moving to a new city? As a startup, how would you build a product to combat climate change? The varying degree of vagueness in these problems is intentional. Some questions may have a specified goal (monetize Whatsapp), while others may have some specified users (Scuba Divers), product (Travel app), use case (Gardening) or a company (Facebook). The intent is to assess how a PM candidate organises the provided information and discovers the absent information while navigating the path of decision making. The thought process must reflect and . Goal clarity, Customer Empathy, Knack for details, Creativity Pragmatism 10 Steps to Crack Product Design/ Sense Interview Step 1. Situation Understanding - Ask Clarifying Questions First, narrow down the broad problem by gathering as much information as possible. PMs are expected to throughly understand the problem and the underlying context before moving to solutions. Reiterate the problem to avoid any misses.
E.g. “Let me make sure that I understood the problem clearly….[state the problem statement here]”.
Also, if it is an existing product, verify your understanding of the product with the interviewer.
E.g. “My understanding is that X product does…….” Else, clarify “What do you mean by ……. ? What is the product about ?” CLARIFYING QUESTIONS TO ASK :
Would it be safe to assume that it would be part of main App than a separate one? 
Would this be a web product or a stand-alone app?
Where is the product in its lifecycle  - new/growth/maturity? 
Is it an Existing or New? 0 to 1 product? Related products?
Is it going to be digital or physical product?
Do we have any particular customer segment or situation like Covid I should focus on?
What market/geography the product serves?
Are there any constraints in terms of cost, time or effort? Is there any urgency?
Should we focus on any platform like android, web, desktop in particular?
Do we have any data to focus on a particular user? any core flow or pain point?
Are there any specific goal(s) that you would want me to focus on? company goal? Interviewers generally allow you to make assumptions but it is best to ask and clarify. Assume wherever you can but just call it out. ASSUMPTION : 
"Scope is limited to Facebook.com both App and Web. We are not focusing on 
Instagram, Whatsapp or other Facebook owned properties" * For e.g. - Problem: How would you__improve Instagram__? Questions: What needs to be improved? UX? Monetization? Customer engagement? Are we talking about Instagram for regular users or influencers or advertisers? Mobile App or Advertisor tools?* Pro Tip : #Try underlining key words to better understand the problem. Step 2. Mission Determine how the product relates to the company’s or entrepreneur’s (or rather the interviewer’s) vision. Reiterate the mission and the synergies. MISSION  :
Facebook - Make world more connected and help people build communities.
Instagram - Allowing people to capture and share moments of their life. 
To bring you closer to the people and things you love.
Google - Organize the world's information & make it universally accessible & useful. For instance, if the given problem is around building a travel product, it does make sense for each of the above companies as per their mission statements, . In a way, travel as a use-case is an extension of their core missions. Step 3. Structure Lay down the steps of your problem solving approach. This will keep your thoughts organized and help the interviewer follow the conversation easily. FLOW :- 
Users-> Needs-> Solutions-> Prioritisation-> Recommendation-> Tradeoff-> Metrics Step 4. Users PMs represent the Voice of the Customer in Business. Designing a product is not possible PMs represent the Voice of the Customer in Business. Designing a product is not possible without thinking about its users/customers. Generally, PMs engage in a dialogue with users to better understand them and their needs. This involves research, customer interviews, FGDs and documentation of insights. However, you would proceed with user-thinking and assumptions while interviewing for PM role. Things to note: Consider all potential and current users Identify primary user and secondary user E.g. A product for kids will have kids as primary users, parents as customers/secondary users whereas teachers or coaches may be the other users. Group the product users into two or more segments (preferably three or four) based on some common traits, needs, and behaviours. It is recommended to use 3-4 characteristics to define each segment for clear segregation and representation. Example user segments could be: User Segments Young professionals (M/F) of age 20-25 years with above average income Millennials who are Information & content seekers, Socially conscious and Tech Savvy USER SEGMENTS :
Working professional, Student, Homemaker, Parents
Demographic - Age, sex, family status, Income, Profession
Millenials(25-40), GenZs (<24 yrs), Baby boomers (40+)  (timing)
High frequency, Medium frequency, Low frequency users based on usage
Innovators, Early Adopters, Early Majority, Late Majority, Laggards

OTHER USERS :
Artists, Content creators, Advertisers, Young Adults, 
Parents, Kids, Elders, Students, College goers, Religious, 
Working professional, Traveler, Affluent, Price Conscious, 
Risk Averse, Influencer, Follower, Volunteers, Activists, 
Conversatives, Digital Nomad, Hiker-Traveler, Educators For more details, read . segmentation While building the product for a selected user group, design a detailed user persona if you have time. This will help to uncover the user’s lifestyle, behaviours, objectives - what/ why/ where/ how/ when? User Persona (Optional) Once you have derived user segments, the next step is to envision the use-cases in which the product will be used. A use case is a description of how a person uses the product to accomplish a goal. E.g. in payments product, the typical use-cases are Person-to-Person (P2P), Person-to-Business (P2B), Business-to-Person (B2P) and Business-to-Business (B2B). Use Cases USER SCENARIOUS : When, Where, Why, What, With Who ? At this juncture, it is recommended to prioritize or eliminate user segments/use-cases after giving a reasonable justifcation. It often makes sense to also define the product goal immediately if you have the goal clarity. * #Think of both supply and demand side when identifying users. For example - buyers, sellers #PMs especially interviewers love matrixes/grids. Try creating a matrix or table of User segments on one side and use-cases on the other or a grid of User demographics and their usage frequency #After identifying the users and use-cases, ask some clarifying questions to see if the interviewer wants you to focus on anything specific.* Pro Tips : Step 5. User Needs, Pain points & Goals After figuring out the right user segments and use cases, pivot to user needs, desires, motivations & objectives. User needs are often referred as “pain points”. Let’s say the problem is “To improve Instagram Stories” and the target user is “Gen Z, College goer, High Freq User”. The pain points here will be: Share updates with friends asap Stay updated about friends Engage socially through likes and comments Maintain privacy amongst network KEY PAINPOINTS :
Awareness, Discovery, Value, Selection, Creation, Ease, Clarity, Effectiveness, 
Privacy, Authenticity, Integrity, Fairness, Relevance, Poor Experience, Support, 
Community-social needs, Performance, Accessibility, Reach, Efficient To uncover more pain-points, put yourself in user/customer’s shoes. Envision the user journey User Journey USER JOURNEY :
Discover-> Reach-> Access-> Test-> Use-> Complete-> Validate-> Express-> Share E.g. User journey of a traveller: Decide the place -> Itinerary/route -> Activities/experiences -> Split expenses -> Share memories-photos/videos -> Review & Refer * #Think of edge cases and error scenarios while building use-cases* Pro Tip : It is best to get the goal clarity as soon as possible - when asking clarifying questions*(Step 1)*, or while discussing your/company’s mission or when identifying users . Before solutioning, you must specify the objective of the product which you are going to build. In order to identify the goal, it is recommended to first prioritize (or omit) user needs / pain points based on the following parameters: Objective/Goals (Step 2) (Step 4) Product lifecycle Users - Volume, Motivation Unique opportunity Competition Company mission Company Strengths Existing solutions * #For new products, the goal could be user adoption wherein the user group and use case could be selected based on market size or gap. #In a real world scenario, a PM will first check the data of the conversion funnel if the product is an existing one. It may be possible that the actionable issue is regarding the discovery of the product and not the usage or engagement.* Pro Tip : Step 6. Solutions Build a list of solutions or feature set based on key user needs, gaps and goals identified above. Take some time to brainstorm and show off your creativity. Ask the interviewer if s/he prefers a particular solution for detailing. It is recommended to have at least 3 solutions to be able to prioritize fairly. The proposed solutions must address the key user pain points. You can build a flat list of features/user stories e.g. - Features W (registration), X (booking) , Y (forum), Z (referral) which will be prioritized later Alternatively, you can build a list of solutions with a subset of features in each. e.g.- App with W, X, Z features as solution 1 and Website with W, X, Y features as solution 2 (and prioritize between App and Website later) IDEAS :- 
UI-UX improvements, New APP, Feature within App or Website,  AR-VR, AI-ML, 
Enable Messaging, NFT, Blockchain, IOT, Robots, Drones, Autonomous vehicles, 
Video conferencing, Virtual rooms, New channel/category Launches, 
New Experiences - learning, live, Payments, Pricing models- Subscription, post-paid
Manual Operations, 3rd Party Vendors, Tele-calls, Video walkthroughs. * #Use SCAMPER framework for creative ideas - Substitute, Combine, Adapt, Modify/Magnify/Minimise, Purpose/Put to another use, Eliminate and Rearrange/Reverse #Companies like Google love to hear moonshot ideas. Keep yourself upto date on new technologies* Pro Tip : Step 7. Prioritization Evaluate and prioritise the list of solutions based on the following factors: on the user could be assessed by determining whether the proposed solutions address a major pain point. The impact to business is analysed in terms of coherence with the mission or the selected goal. Impact in terms of time to implement, technology and, engineering resources required. Cost could be value risks, usability risks, feasibility risks or business viability risks. Risks PRIORITIZATION OF SOLUTIONS :-
Impact - to user & business
Cost - time, effort & feasibility 
Risk - confidence Step 8. Recommended Solution Now that you have put forward a constellation of propostions, it is time to finally recommend a solution and justify. Based on the prioritisation, recommend a solution with its set of features. The chosen solution should have relatively high value, low overall cost and low associated risks. RECOMMENDATION :
Why would people use it? Differentiator? What would you build as MVP? 
How would people use it? Is it a unique opportunity or have large target audience?  
Is it a Low Hanging fruit or a Quick win? * #Select a combination of features for your MVP and describe each to build an overall picture of the recommended product* Pro Tip : You can also share a contingency plan and chart a rough roadmap of the product. Based on the success of your MVP (i.e. recommended solution), you can include the rest of the features from your solution list in your roadmap*(Step 6)*. Have instrumentation, do A/B testing, take customer feedback and if possible share product vision. Roadmap (optional) Highlight pros/cons and the risks of the recommended solution. Think of the edge-cases and negative user flows. In real world, the biggest risk for any new product is the lack of data and customer research. Tradeoffs KEY TRADEOFFS :
Cannibalisation, customer satisfaction, overuse, safety, integrity, privacy, 
disparity, opportunity cost of another customer segment/ pain point/ geography Step 9. Success Metrics The primary expectation from the recommended solution is to acheive the goal described earlier but how would you quantify it? Measuring the product success is a vast area in itself and deserves another chapter. For the interview, it is recommended to specify 2-5 key metrics that relate best to your goals and the final product. Product Metrics are of the following types: Northstar (or Goal metrics) - Be top 10 app in its category, Traffic Product Tracking (or Product Health metrics) - #Users, Engagement Guard-Rail (or Counter metrics) - Measure of tradeoffs, cannibalisation KEY METRICS :
Adoption - Install/downloads, signups, # of users
Growth - %age Increase in New Users, DAU, MAU
Engagement metrics  -  DAU, MAU, session time, view, like, share, comment
Retention - Cohort activity D7, D30,  DAU per MAU
Monetisation - Revenue, CTR, ARPU, Subscriptions, Revenue per Ad
Customer Satisfaction - SUS, CSAT, NPS, User ratings, Referrals * #For new product, measure adoption as number of users using the product and active users #For measuring engagement use #active users as the base than just #users* Pro Tip : Step 10. Summarize Finally, outline your approach, beginning with the problem and ending with your recommendation based on the key criteria you selected. * #Use STAR to summarize - Situation, Task, Action, Results* Pro Tip : COMMON MISTAKES :
Not asking enough questions to ensure common ground on product, users
Lack of mission alignment between company and product
Lack of structure in problem solving
Incomplete or no user journey
Poor customer segmentation - overly detailed, just age-based
Prioritising users, pain points, or solutions without proper reasoning
No connection between Goal-User-Painpoint-Solution
No tradeoffs or counter metrics for the recommended solution
Not clarifying #events or #unique customers in metrics
Too long a summary * * Expert Tip : #Break the structure and pattern wherever you can. Customize it.

Flow

Discovery

Facebook

Google

Instagram

Target

YouTube

2022 - HackerNoon Contributor of the Year - Design

2022 - HackerNoon Contributor of the Year - Management

2022 - HackerNoon Contributor of the Year - Product Development

2022 - HackerNoon Contributor of the Year - Product Management

Checkout the Product Management journal

Nominated for 2022 - HackerNoon Contributor of the Year - Product

Nominated for 2022 - HackerNoon Contributor of the Year - Product Development

Nominated for 2022 - HackerNoon Contributor of the Year - Product Management

Nominated for 2022 - HackerNoon Contributor of the Year - Design

Nominated for 2022 - HackerNoon Contributor of the Year - Management

Too Long; Didn't Read

How to Solve Product Design Questions|The Great PM Interview

How to Solve Product Design Questions|The Great PM Interview

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

RCA for Tech Managers : How to approach a Product Issue

Building a RAG System That Runs Completely Offline

Brands, Find the Right HackerNoon Services for You

The TechBeat: The Paycheck Era is Dying (11/12/2025)

Court Finds OpenAI in Violation of German Copyright Law, Orders Damages

RCA for Tech Managers : How to approach a Product Issue

Building a RAG System That Runs Completely Offline

Brands, Find the Right HackerNoon Services for You

The TechBeat: The Paycheck Era is Dying (11/12/2025)

Court Finds OpenAI in Violation of German Copyright Law, Orders Damages

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps