Interview Questions

Exponent - "This is a Design a Product question. For this, we'll want to follow the formula for success: Ask clarifying questions Identify user types, behaviors, and pain points State the goal and use cases List current solutions Improvements / net new solutions Evaluate and select solutions Measure Success Summarize Ask clarifying questions The PM interview isn't about your ability to come up with the best solution right away — it's about bein"See full answer

Exponent - "This is a classic Favorite Product question with a constrained product type. For this, we want to make sure it's an enterprise product. Let's go over the Favorite Product formula before diving in: Choose a product and briefly explain what it is Who are the users? What are their pain points? How did competitors solve it in the past? How does this product address these pain points differently and better? How would you improve it/make it better? **Su"See full answer

Exponent - "Before we begin, it's important to understand what the interviewer is testing with this type of question. This is a Strategy Question that tests an interviewee's ability to create compelling arguments from high level information, discern motive, and think strategically. We can split this question into two views: is Spotify's high churn rate okay or not? Let's see the argument that is bad, and then the opposing side. High churn is bad We'll first give the naive argument here — that churn i"See full answer

Exponent - "You should identify this type of interview question as an Expansion problem, since we're expanding to a new market. This is similar to a growth problem, with a few additional components. This is the formula you should use when tackling these types of interview questions: Ask clarifying questions Perform user analysis Market risk analysis State goals Perform channel analysis Prioritize growth channels Strategy Summarize Without further"See full answer

Exponent - "This is a pretty straightforward Improve a Product question. Let's first go over the Improve a Product formula: Ask clarifying questions Identify users, behaviors, and pain points State product goal Brainstorm small improvements Brainstorm bolder improvements Measure success Summarize Now, let's begin! Ask clarifying questions Before we begin listing off recommendations, it's important you ask questions to ensure you and the interviewe"See full answer

Exponent - "This is a Favorite Product question with a slight twist. We have a constraint: picking a physical product. This should be relatively easy since you use physical products personally every day. Let's go over the Favorite Product formula before we begin: Choose a product and briefly explain what it is Who are the users? What are their pain points? How did competitors solve it in the past? How does this product address these pain points differently and better? "See full answer

Pablo S. - "1) Product, the value and the users this business has Product: Yelp is a platform that connects local businesses with people looking for those services. Value: Yelpers can connect with them / book appointments or make reservations with a good amount and quality of reviews per business. For businesses, it is a way to get visibility and find new demand with an easy setup. Users: Local businesses (offering): successful when they are booked. Searchers / demand: successful when"See full answer

Exponent - "This is another Fermi problem — an estimation or approximation problem with limited information and back-of-the-envelope calculations. There's no right answer: interviewers want to understand how you think and how well you can explain your reasoning, rather than what you already know. Recall the formula for Fermi problems: Ask clarifying questions Catalog what you know Make equation(s) Think about edge cases to add to equation **Breakdown components of your"See full answer

Exponent - "The key to this is to be concise and specific. You won't need to code as a product manager, but understanding technology is important. Only give enough information to validate your knowledge. By speaking too much, you may make a mistake (if you're not technical). > Sure! I'll list the first five I can think of off the top of my head. There's a login endpoint that logs a user in, a signup endpoint to sign up a user, there's likely an endpoint to grab a list of songs to display in a playlist, a su"See full answer

Exponent - "This is a Technical question. It tests your ability to understand high level technical concepts. Even though your job won't have any coding involved, you'll still need to understand these concepts. Being able to cover all these topics with clarity communicates confidence in your interviewer. Unfortunately, there's no formula for technical questions, but some general tips are: Use analogies when you can Break your solution into clear, bite-size steps Don't be afraid to use examples to b"See full answer

Sachin P. - "My approach to open ended prompts is to gather as much information as possible to: A) Clarify the issue -> b) Identify various possible root causes -> C) Narrow down on the most likely cause ->D) Set up a recommendation and how to track whether the proposed solution will work. A) CLARIFY 1) Clarify the metric Ensure that we fully understand this metric. Does uploads refer specifically to the individual files that someone uploads to their account? Does it include both manual uploads whe"See full answer

Exponent - "This is another Diagnosis problem. To answer this question, we suggest you use our framework (along with the TROPIC method) to be as thorough as possible. The framework is as follows: Ask clarifying questions List potential high level reasons Gather Context (TROPIC)Time Region Other features / products (internal) Platform Industry / Competition Cannibalization Establish a theory of probable cause Test theories Propose solutions Summarize "See full answer

Exponent - "This is a classic Favorite Product question with a constrained product type. For this, we want to make sure it's a SaaS product. Let's go over the Favorite Product formula before diving in: Choose a product and briefly explain what it is Who are the users? What are their pain points? How did competitors solve it in the past? How does this product address these pain points differently and better? How would you improve it/make it better? **Summarize"See full answer

Exponent - "This is a Technical question. It tests your ability to understand high level technical concepts. Even though your job won't have any coding involved, you'll still need to understand these concepts. Being able to cover all these topics with clarity communicates confidence in your interviewer. Unfortunately, there's no formula for technical questions, but some general tips are: Use analogies when you can Break your solution into clear, bite-size steps Don't be afraid to use examples to b"See full answer

Exponent - "This is another Fermi problem — an estimation or approximation problem with limited information and back-of-the-envelope calculations. There's no right answer: interviewers want to understand how you think and how well you can explain your reasoning, rather than what you already know. Recall the formula for Fermi problems: Ask clarifying questions Catalog what you know Make equation(s) Think about edge cases to add to equation **Breakdown components of your"See full answer

Exponent - "This is a Design a Product question. For this, we'll want to follow the formula for success: Ask clarifying questions Identify user types, behaviors, and pain points State the goal and use cases List current solutions Improvements / net new solutions Evaluate and select solutions Measure Success Summarize Ask clarifying questions It's important to get clarity on anything if things are unclear. Since this ask is quite straightforward"See full answer

Exponent - "This is a Design a Product question. For this, we'll want to follow the formula for success: Ask clarifying questions Identify user types, behaviors, and pain points State the goal and use cases List current solutions Improvements / net new solutions Evaluate and select solutions Measure Success Summarize Ask clarifying questions It's important to get clarity on anything if things are unclear. Since this ask is quite straightforward"See full answer

Exponent - "You should be able to easily identify this as a Measure Success question. These kinds of questions are used to test your analytical skills, as well as your ability to track project progress post-launch. Here's the strategy for tackling these: Ask clarifying questions State the goal of the feature / product Behavior Mapping / UX Flow Mapping Provide criteria to prioritize metrics Prioritize metrics Summarize Without further ado, let's dive in! Ask"See full answer

Exponent - "This is another Fermi problem — an estimation or approximation problem with limited information and back-of-the-envelope calculations. There's no right answer: interviewers want to understand how you think and how well you can explain your reasoning, rather than what you already know. Recall the formula for Fermi problems: Ask clarifying questions Catalog what you know Make equation(s) Think about edge cases to add to equation **Breakdown components of your"See full answer

Exponent - "This is a Fermi problem — an estimation or approximation problem with limited information and back-of-the-envelope calculations. There's no right answer: interviewers want to understand how you think and how well you can explain your reasoning, rather than what you already know. Recall the formula for Fermi problems: Ask clarifying questions Catalog what you know Make equation(s) Think about edge cases to add to equation **Breakdown components of your equat"See full answer