How to Answer Product Design Questions

Product design questions ask you to design or improve a product. Common question types include:

• Design a product: “Design an app for job-seekers to match with employers.”
• Improve a product: “Improve headspace.”
• Design for a specific audience: “Design a vending machine for the blind.”
• “Moonshots”: A Google favorite — “Design X, assuming you have infinite resources.”

Overall, your goal is to come up with a feasible product given the constraints of the question. Feasible, in this context, means that your product solves a problem in a way that makes sense for the company and that users will like.

These typically take 25 minutes excluding follow-ups. Interviewers like to ask product design questions early on to filter out candidates who don’t have essential product skills, but they’re a popular question type during on-site interviews as well. Expect to answer several in a standard PM interview loop.

A framework for answering product design questions

A solid process is to first clarify the problem, gather relevant context until you understand users and their challenges, explore and select the best option, and finally, justify your answer. Follow this 7-step process.

• Step 1: Clarify and get context
• Step 2: Define users
• Step 3: Identify pain points and opportunity areas
• Step 4: Brainstorm possible solutions
• Step 5: Define a product vision
• Step 6: Prioritize features
• Step 7: Evaluate and recap

Let’s work through an example to illustrate.

Assume you’ve been asked the question “Design a better gym experience.”

Step 1: Clarify and get context

First, clarify any vagueness about the problem you’ve been given. After you’ve clarified ambiguous company names and keywords, gather context that will help you understand the problem space and define any strategic considerations that might influence your design.

Questions like “What’s the timeline?” or “Are there any constraints I should be aware of?” are fair game, but be prepared for an interviewer to give you a vague answer. In this case, make assumptions and state them to your interviewer so they have a chance to correct you if you’re veering off-track.

Step 2: Define users

Next, define subsets of users that would effectively partition the total user base and pick an interesting subset for a deep dive. There are many ways to segment users. To get started, you could consider:

• Demographics like age or income level
• Behavioral characteristics like frequency of use or users taking certain target actions
• Geographic location

Any of these is a good jumping-off point, but a great answer segments users in a way that is meaningful for the question at hand. One helpful tip is to segment users who might have very different needs. After choosing a segmentation scheme and listing a few basic user subsets, pick a segment that interests you and articulate why that segment is valuable to discuss. Consider:

• User subsets that may be strategic (for example, early adopters)
• Scale of impact, or the depth of pain that users feel
• How well you / your company can address these users in the context of your question

Step 3: Identify pain points and opportunity areas

Next, consider any goals your users might have. Any explicit obstacles are pain points. If nothing’s blocking users from achieving their goals but some point of friction clearly exists, you’ve uncovered an opportunity area. Take an empathetic position and focus on how to best serve these users and you will uncover both.

Take a moment to summarize the goals you think your user subset has, then brainstorm pain points and opportunity areas preventing them from achieving those goals.

Consider the circumstances users are in. Is the goal urgent? Are the decisions involved important or trivial? Asking yourself these questions and putting yourself in the user's shoes demonstrates user empathy, a key PM skill, so be sure to articulate your thought process to your interviewer.

Step 4: Brainstorm possible solutions

Now, brainstorm ideas that could solve the pain point you’ve identified.

One helpful tip for coming up with solutions is to think of products you like — especially anything solving a similar problem in another context. For example, Duolingo might be a good analogue for our gym example as it effectively removes barriers for people who want to improve themselves (by learning a language) but who have trouble with motivation, routine, or planning. The app is fun, easy to use, and the emphasis is on consistency rather than intensity. These are all characteristics you might incorporate into your design.

Aim to generate at least three solid ideas before moving on to the next step. It’s fine to brainstorm a bigger list and eliminate weak ideas. Check each idea against the pain point you identified and don't be afraid to get creative. Interviewers want to see excitement and passion for product.

Step 5: Come up with a forward-looking product vision

Pick the strongest solution from the previous section and take a moment or two to envision what that product will look like in five or ten years. Come up with a brief tagline that really emphasizes the point you're making. You want to leave the interviewer with a soundbite they’ll remember when they’re scoring your interview. Write it on the whiteboard (if you’re using one) and refer back to it as you continue.

Step 6: Prioritize features

Once you’ve crafted a compelling product vision, it’s time to prioritize features.

We recommend walking the interviewer through a quick user journey where a user interacts with your product. This will help you concretely identify how your product fits into the existing user flow which will help you prioritize features. It’ll also help you stay user-centric instead of over-defining an idea that appeals to you personally.

Then, brainstorm a short list of features based on your use case(s) and prioritize according to which features best support your product vision. Be sure to tie the discussion back to user pain points. Here are a few helpful dimensions to consider:

• Scale: How many users does this help?
• Ease of expansion: How easily will this feature expand to other user subsets? Will it attract new users?
• Strategic impact: How well does this feature support the company vision?

You don’t need to describe every part of the feature in detail, but interviewers do expect you to describe what the user sees and interacts with and how that delivers on the product goals and vision you defined.

Step 7: Evaluate and recap

As you wrap up, summarize your insights and your overall design for your interviewer, then spend a few minutes evaluating your design and discussing next steps. Consider:

• Tradeoffs you made
• Alternate use cases and edge cases
• What you’d do differently given more time

Common follow-up questions from interviewers include: “Can you see any risks with this design?” and “What challenges do you anticipate in implementing this product?” Discussing risks and challenges preemptively signals to interviewers that your ideas are grounded in reality.

Tips for answering product design questions

Consider company strategy

Bringing strategic concerns into the mix can help you reach a broader and deeper understanding of the problem at hand. Here are some prompts to consider:

• Company mission: What’s the company mission? Why does the company care about this space? How could this product support the mission?
• Company strategy: What are the relevant strategic goals the company might have? How could this tie into those or open up a new strategy? What products make sense strategically?
• Market understanding: What alternatives already exist in the market? Where are the gaps? What’s valuable in this market?

Ace moonshot questions by abstracting the problem

Moonshots are bold ideas that go beyond incremental changes. They’re frequently associated with Google interviews, but you can “moonshot” any design question by digging deep until you’ve uncovered the root of an important problem in a way that feels transformative.

You’re on the right track if you’ve found a way to solve the problem completely and simply for the user. If you’re able to eliminate the conditions that cause the problem in the first place, even better.

We've found two different strategies helpful for candidates practicing moonshots. One is to think of the product as a black box. The input is the user’s current state, and the output is the user as they want to be. By eliminating all assumptions about how to get users from where they are to where they want to be and exploring what could happen in that space, really transformative solutions can sometimes become clear.

Another strategy is to use something like the 5 Whys technique to dig deeper and deeper until you uncover the root of the problem.

You could also consider what the user’s actual goals are. For instance, if you’re asked to build an alarm clock for deaf users, consider that the user’s goal is to wake up at a certain time. Rather than limiting yourself to modifying how existing alarm clocks work, this framing allows for new options that rethink what an alarm clock is. Our best advice is to focus on the user and their needs — this approach will never steer you wrong.

Consider existing users, strategic goals, and market context when answering product improvement questions

Sometimes, you’ll be asked to improve an existing product. Questions like “Improve Instagram’s home tab” are similar to “design X” questions, but you’ll have to consider established users, goals, and market dynamics. Keep these in mind, and consider addressing under-served users, supporting new use cases, or adapting a product to open new strategic opportunities - these are all common areas for improvement.

Common pitfalls

• Jumping straight to a solution: make sure you explain your thought process so the interviewer can understand how you think and why your idea is a good solution. Also, don’t decide on a solution immediately after hearing the question. Keep an open mind, because you’ll usually find better ideas as you explore the problem.
• Forgetting to segment users: In some design questions, you’ll be given a subgroup of users or a constraint to design for, For instance, if you were asked: “Design Gmail for kids.” A very common mistake is to assume you don’t have to segment users because you’re given a constraint up front. For the Gmail question, kids are a broad group. You could segment out a particular age range or level of school to focus on. If you wanted to go deeper, we recommend discussing capabilities and constraints relevant to your segment. For instance, if your segment is early elementary school kids, some notable constraints would be that they’re not great at writing, they may not be very technically savvy, and their safety is extremely important. These will all influence the way you build your product, and they’re easy to miss them if you don’t explicitly consider them.
• Trying to design for everybody: If you try to design for everybody, you usually end up with something that nobody actually cares about. If you don’t narrow your scope, you’ll have trouble getting meaningful insights about your users and their pain points.
• Checking off the boxes: It’s okay to use a framework to keep yourself on track. However, the steps of a framework are recommendations to help you find insights, not a checklist you have to get through. Make sure you consider your answer holistically at every stage.