10 Product Design Questions for PMs (with Sample Answers)

Product design questions are common in product manager interviews at companies like Google, Meta, and Amazon. In fact, they made up 13% of the 600+ interview questions that we collected from these three companies.

Questions such as “How would you design a phone for people with hearing loss?” can really stump you if you have not prepared for them.

Worried? Don't be. This guide has everything you need to learn how to answer product design questions confidently and effectively. We'll cover:

• What is a product design question? 
• How to answer product design questions
• Example product design question with answer: Design a computer keyboard
• 10 product design interview questions with answer ideas
• More product design questions from top tech companies
• Product design mock interviews
• How to prepare for product design questions

Let’s get started.

Click here to practice 1-on-1 with FAANG ex-interviewers

1. What is a product design question?↑

Product design questions are one of the most common and important types of questions asked in product manager interviews. You’ll often be given 45–60 minutes to design a completely new product, such as “a fitness app for Meta” or “an umbrella for kids.”.

Product design questions are often part of a “product sense” interview round, as it is known at companies such as Meta, Lyft, Stripe, and others (Google has a “product insight” round). 

As part of this round, instead of a product design question, you might get a product improvement question (see our separate guide to product improvement questions).

Next, we’ll dive deep into a framework that will help you answer all product design questions, as well as a complete sample answer that uses that framework. If you’d like to skip straight to the list of questions, you can do so here. 

2. How to answer product design questions↑

We recommend using a three-step approach to answer product design questions in a product manager interview. This approach is also known as the BUS framework:

1. Business objective
2. User problems
3. Solutions

If you're preparing for a product manager interview, we strongly encourage you to learn that framework, as it can also be used for product improvement questions (e.g. "How would you improve YouTube?"). Let's go through each of the three steps, one by one. 

Step one: Business objective

Many candidates skip this step and start listing design ideas in an unstructured way. This is a big red flag for interviewers. 

Here are the things you need to do before starting to think about user problems and how to solve them:

• Outline how you will approach your answer.
• Define the business objective.

First, you should lay out your approach to solving the question. 

You could say something like, "First, I'm going to try to understand the business situation and our objective in more detail. Second, I will focus on defining the target user and brainstorming what problems we could solve for them. And third, I will generate solutions for these problems, prioritize them, and make a recommendation."

Outlining your answer shows you think clearly and strategically, and that you've got strong communication skills. If you jump straight in and answer the question in an unstructured way, it will be very hard for your interviewer to keep up with you.

Second, you need to clarify the business situation and objectives. Knowing the business context and what it's trying to achieve will help you make better design decisions later on. This is particularly important if the question your interviewer asks is vague.

For instance, let's imagine your interviewer wants you to "design a phone." 

Then you might want to ask what the specific business objective is that we are trying to fulfill (e.g., sell as many phones as possible with a low price point, go for the premium market, etc.) and whether we already have a user in mind for the phone (e.g., business users, teenagers, etc.).

You'll design completely different phones depending on the answer to these questions.

Step two: User problems

Now that you know more about the business situation and objectives, it's time to think about the users and their problems/pain points in greater detail. 

Here are the things you need to do in this step:

• Select a user type.
• List user problems/pain points.
• Prioritize user problems/pain points.

First, you should identify the different types of users for your product, and you should select one to focus on.

Going back to our phone example, if the business objective is to focus on an underserved market, you could suggest focusing on: hard of hearing users, visually impaired users, elderly users, users with mobility issues, etc. List these different users and select one with your interviewer.

Note that you can skip this part of the discussion if your interviewer has already specified a type of user they want to focus on in their initial question.

It's also helpful to remember that for some products, the user and the customer are not the same person. For example, this is the case for games that parents buy for their kids, or software (e.g., Jira) that managers buy for people in their teams.

Second, once you've got a target user, you should think through what problems you can solve for them. An easy way to do this is to imagine them using the existing product or service you're trying to replace.

For instance, let's imagine we are focusing on hard-of-hearing users. What are the problems they are facing with current phones? 

Here are some examples: 

1. Can't hear the phone ringing 
2. Can't hear the other person talking on the line
3. Can't listen to voicemails
4. Can't hear app notifications
5. Can't hear the sound of videos received from friends, etc.

Third, you should prioritize one to three items from the list of problems you have created. It's common to prioritize based on how painful that problem is for the user. 

For instance, you could say something like, "My suggestion is to focus on solving problems one and two because those are the two features that really define a phone and they are currently inaccessible to hard of hearing people."

Step three: Solutions

Many candidates don't spend enough time selecting a single target user and creating an organized set of solutions. Once you've defined the user problems you are trying to solve, it's time to generate some solutions. Here's how to do it:

• List solutions.
• Prioritize solutions.
• Summarize your answer.

First, for each of the user problems you have identified, you should generate potential solutions.

Let's do this for user problem 1: hard of hearing users can't hear their phone ringing. You could build a phone that does any of the following things when ringing:

• Rings for longer than standard phones to give more time to pick up
• Flashes bright colors on the screen
• Vibrates really strongly
• Is connected to a vibrating wristband or watch
• Sends visual notifications to other connected devices, such as laptops, TVs, connected light bulbs, etc.

At this stage, it's helpful to draw a table with two columns on a piece of paper or on a whiteboard. The first column should contain the user problems you have decided to focus on. The second column should contain solutions to solve each problem.

Second, once you've generated a few ideas, it's time to prioritize the ones you will recommend building. A common way of doing this is to grade each solution from 1 (low) to 3 (high) based on how much value they would deliver for the user and how easy they are to implement.

You will need to do this for each of the user problems that you identified in step 2. Don’t forget to address the trade-offs of your solution (e.g., a vibrating wristband would require users to pay for additional hardware).

Finally, after going through this exercise, it's a great idea to state the initial question again, and summarize what product you suggest building and why. 

This summary is a simple way of telling your interviewer that you are done answering the question. And again, it's an efficient way of showing you think clearly and strategically and communicate your thoughts effectively.

2 common mistakes to avoid when answering design questions

There are two common mistakes candidates make when answering product design questions that you can easily avoid.

First, a lot of candidates simply skip step one and start answering the question without first agreeing with their interviewer on a clear objective or target user. As mentioned above, this is a red flag.

Second, many candidates don't spend enough time selecting a single target user and creating a short list of user problems. In other words, they start working on step three too soon. 

Actually, the more work you do in steps one and two, the easier brainstorming and selecting solutions will become.

3. Example product design question with answer: Design a computer keyboard↑

Now that you know what approach to use to answer product design questions, let's apply it to a full example.

Try answering the question below following the BUS method we have described. Play both the role of the interviewer and candidate, and make decisions regarding what business objective and target user to focus on.

Answer:

1. Business objective

Let's start by outlining the approach we are going to take. First, we will discuss the business objective. Second, we will analyze users and the problems we could solve for them. And third, we will look into solutions and make a recommendation.

Here are the questions that immediately come up to clarify the business objective for this design question:

• What's the business objective? Maximize profits? Focus on an underserved niche?
• Do we already have a target user in mind, or is that something we should explore or discuss?
• Keyboards are often paired with a mouse. Do we just want to design a keyboard, or should we also design a mouse that goes with it?

Let's assume here that the interviewer wants us to design a keyboard for gamers but isn't interested in the mouse, and that the business objective is to maximize revenues.

2. User problems

Now that the business objective is clearer, let's start thinking about users and user problems in more detail.

There are different types of gamers we could focus on. An easy way to segment them is to split the market between casual and professional gamers. 

Given we want to maximize revenues, it makes sense to focus on casual gamers, as it's likely to be a much bigger market than the professional segment.

Let's now brainstorm typical problems casual gamers face when using standard computer keyboards. Here are seven that promptly come to mind:

1. User can't perform at their best because keys are slow to respond, collect dust underneath over time, and aren’t easy to replace.
2. User can't easily create personalized shortcuts, as the software available to customize the keyboard is rudimentary.
3. User has to replace the keyboard frequently as keys that are repetitively used wear out or break (e.g., space, shift, etc.).
4. User is distracted by noisy keys.
5. User can't easily turn the game volume up or down from the keyboard.
6. User can't see keyboard keys when playing in the dark.
7. User's wrists and hands hurt as the keyboard is uncomfortable to use for long periods of time.

Let's now prioritize these problems by putting ourselves in the shoes of a gamer. Most gamers' primary #objective is probably to win the game they play. As a result, it makes sense to prioritize solving problems, which will help users significantly improve their performance.

Let's therefore focus on problems one and two, as these look like they could make the user faster and better if solved.

3. Solutions

Let's generate solutions now that we have selected a type of user (casual gamers) and a set of user problems (one and two above).

We'll rate the solutions from 1 to 3 directly inline. For technical simplicity, we'll give 1 to the hardest solutions to implement and 3 to the easiest. For value delivered to the user, we'll give 1 to the least valuable solutions and 3 to the most valuable. And then we’ll add up both numbers.

Here are some solutions that could help solve problem one, which is that users can’t perform at their best because keys are slow to respond, collect dust underneath over time, and are not easy to replace:

1. Build keys that don't need to be pressed as hard or deep for the user input to be registered (Simplicity = 3, Value = 3, Total = 6).
2. Build keys that register user input quicker thanks to alternative technologies (e.g., magnetic keys, mechanical keys, etc.) (S = 1, V = 3, T = 4).
3. Build keys that can easily be removed to clean the keyboard or that don't let dust settle under the keycaps (S = 2, V = 2, T = 4).

Here are some solutions that could help solve problem two, which is that users can’t easily create personalized shortcuts, as the software available for customization is basic:

1. Create software that lets users define different sets of shortcuts depending on what game they play (Simplicity = 2, Value = 3, Total = 5).
2. Create software that makes automated suggestions for shortcuts based on commonly used shortcuts by other players with similar keyboards (S = 1, Value = 2, T = 3).
3. Create software that lets users adjust how hard or deep they need to press the keys for their input to be registered (S = 1, V = 3, T = 4).
4. Add additional buttons to the keyboard that let users generate a combination of keystrokes (i.e., a "macro") in a single keystroke (S = 3, V = 3, T = 6).

Now that we have generated some solutions, let's prioritize them based on how easy they are to implement and how much value they bring to the user. 

For problem one, it therefore looks like prioritizing the first solution makes sense. One of the tradeoffs to bear in mind when implementing this solution is that we could make the keys so sensitive that the user might inadvertently press the wrong keys more often. We will therefore have to balance the sensitivity and control of the keyboard.

For problem two, the first and fourth solutions are promising options. Here, an important tradeoff is balancing customization and complexity. We're targeting casual gamers, so we want to give them a good level of customization but not make installing and personalizing the keyboard too complex and lengthy.

Finally, let's summarize. Our recommendation is to build a keyboard for casual gamers, as this is most likely to maximize revenues. We also recommend building features that will help the user maximize their performance while remaining simple to implement. Here are the three features to build:

• Keys that are more sensitive than standard
• Software that lets the user create shortcuts
• Additional buttons for "macro" shortcuts

4. 10 product design interview questions with answer ideas↑

Now that you’ve seen a framework to answer product design questions as well as a sample answer that illustrates it, let’s get into some other questions that you can use to practice. 

Below, we’ve listed ten product design interview questions that were asked in PM interviews at Google and Facebook, according to Glassdoor data.

For each question, we’ve included a few bullets and jumping-off points to consider as you craft your answers. 

You’ll find important questions and clarification points under each Business objective, three possible pain points under User problems, and three possible solutions under Solutions.

Of course, these lists are not exhaustive, and you should add your own insight as you work through them. They’re designed to get your wheels turning and offer some hints if you’re stuck. 

If you'd like to learn about the other types of questions you may face, you can also visit our ultimate guide to product manager interview questions.

Now that you have a list of sample questions to work with, it’s important to consider how you will practice with these questions, as well as some specific product design questions from top tech companies.

5. More product design questions from top tech companies↑

We researched more product design questions from these top tech companies to give you more in-depth information on the specific questions they ask.

Meta:

Apple:

Amazon:

Netflix:

Google:

Microsoft:

TikTok:

6. Product design mock interviews↑

It’s also useful to watch mock interviews of other candidates or experts answering product design questions. You can see how it plays out in a real-life interview setting. You can also watch experts answer questions and see how it should be done.

We’ve reviewed product design mock interview videos and compiled the 10 best examples of how to answer product design questions here. You can watch and learn from them:

If you only watch one product design mock interview, we recommend the one below - it's a great example of how to approach these kind of questions, complete with interviewer feedback.

7. How to prepare for product design questions↑

With a lot to cover, it’s best to take a systematic approach to make the most of your practice time.

You’ll also find links to free resources and the four key steps that you can take to prepare for product design questions.

7.1 Study the company you're applying to

Get acquainted with the company you’ve applied to. In many cases, the product questions you’ll be presented with will be based on real-life cases the company is facing. If you’re applying to a specific team, study up on their products, the user, etc.

Take the time to find out which products you’ll most likely be working with, based on the job description, and research them. Look up relevant press releases, product descriptions, product reviews, and other resources in order to discuss what’s most important to the role: the company’s product.

If you'd like to learn more about a specific company's PM interviews, then we'd encourage you to check out our guide for that company below

• Google product manager interview guide
• Meta product manager interview guide
• Amazon product manager interview guide
• Microsoft product manager interview guide
• LinkedIn product manager interview guide
• Uber product manager interview guide
• Stripe product manager interview guide
• Lyft product manager interview guide
• Apple product manager interview guide
• TikTok product manager interview guide
• Coinbase product manager interview guide
• Airbnb product manager interview guide
• DoorDash product manager interview guide
• Netflix product manager interview guide
• Nvidia product manager interview guide
• Capital One product manager interview guide

7.2 Learn a consistent method for answering product design questions.

In this article, we’ve outlined a step-by-step method you can use to solve product design questions. We’d encourage you to first memorize the basic steps, and then try solving a couple of the sample questions on paper.

This will help you understand the structure of a good answer. This is a good first step, BUT just knowing the method is not enough; you also need to be able to apply the steps in interview conditions. 

Once you’re in command of the subject matter, you’ll want to practice answering questions.

But by yourself, you can’t simulate thinking on your feet or the pressure of performing in front of a stranger. Plus, there are no unexpected follow-up questions and no feedback.

That’s why many candidates try to practice with friends or peers.

7.3 Practice with peers

If you have friends or peers who can do mock interviews with you, that's an option worth trying. It’s free, but be warned, you may come up against the following problems:

• It’s hard to know if the feedback you get is accurate
• They’re unlikely to have insider knowledge of interviews at your target company
• On peer platforms, people often waste your time by not showing up

For those reasons, many candidates skip peer mock interviews and go straight to mock interviews with an expert. 

7.4 Practice with experienced PM interviewers

In our experience, practicing real interviews with experts who can give you company-specific feedback makes a huge difference.

Find a product manager interview coach so you can:

• Test yourself under real interview conditions
• Get accurate feedback from a real expert
• Build your confidence
• Get company-specific insights
• Learn how to tell the right stories, better.
• Save time by focusing your preparation

Landing a job at a big tech company often results in a $50,000 per year or more increase in total compensation. In our experience, three or four coaching sessions worth ~$500 make a significant difference in your ability to land the job. That’s an ROI of 100x!