Product Manager Interview Questions

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

Ankit C. - "I can use personalised announcement, something like speaking out loud the time in a more sublte way, instead of blaring sound of an alarm. We can put dynamic alarm tune, meaning one type of tune repeats itself only after a certain period of days. That should help the tune in not becoming the noise to the user, and so he doesn't get indifferent to same tune over time. Can add a voice assistant to set the alarm, pre-recorded with a fixed set of voice commands - to avoid reliance on internet. Can"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

Exponent - "This is one of the core behavioral questions that you should expect to cover in any interview. In particular, it asks you to justify why you want to work at a specific company that you've applied for. There's no right answer for this, however we do recommend you list at least three distinct reasons. Here's an example of what you might say: > That's a great question. There are three main reasons why I want to work at Twitch:Building a product I use > Working in marketplaces > Mentorship > I'll go"See full answer

Exponent - "This is an 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 interviewer are on the same page"See full answer

Andrei S. - "Follow up question was: what is your strategy to sell it?"See full answer

Lee F. - "If this is not a project, we should first establish a memorandum of understanding that gives us a sense of their availability, skills, minimum and maximum levels of support, and other parameters that would govern their involvement. With a project in hand, the same understandings need to be achieved or renewed before project commitment to see if tech/DS can fulfill the need. You owe it to your partners to provide them with as much clarity about the project as you can: its goals, scope and deadlin"See full answer

Exponent - "This is a Measure Success question with a slight twist. The twist here is we need to consider a hypothetical product rather that one already built. This changes our formula slightly - specifically we may not be able to apply a UX flow to drive analysis since we're unsure of the implementation. Instead, we'll look at core behaviors that are indicative of success. Here's the modified formula: Ask clarifying questions State the goal of the feature **Apply a UX flow to drive a"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