Product manager interview questions, by type

Most PM interview questions fall into a few types: product sense and design, metrics, estimation, execution, strategy, technical and behavioral, with AI product questions now common too. Below are 40 to practice, each with a note on what a strong answer does. We build Soreno, an AI voice interview practice app. For the estimation questions, our free market sizing builder works a size top-down and bottom-up so you can see where the two routes differ, no sign-up needed.

Updated

Questions
40
Grouped into 8 types
Product sense
8
Improve or design a product
Behavioral
7
Have stories ready
Estimation
4
Rough numbers, said out loud

What interviewers listen for

Google and Meta both publish what their PM interviews assess. The overlap is a good guide for any company.

  • A clear user

    Meta scores how you choose a target audience. Google's APM page asks you to understand users and their needs.

  • A ranked problem

    Meta scores identifying and prioritizing the problem. Ideas come after that.

  • Goals and metrics

    Meta's Analytical Thinking interview scores measurable, prioritized goals and the metrics that show impact.

  • Reasoning you can follow

    Google tells APM candidates to outline the answer first, think out loud and treat it as a conversation.

  • Specific stories

    Meta suggests STAR for behavioral questions. Google asks for data: accomplished X, as measured by Y, by doing Z.

From Meta's PM interview prep guide, Google: APM application process and Google: interview tips.

40 product manager interview questions

Soreno's own questions. Some are written in the style of Google, Meta and Amazon interviews and name their products. None are those companies' own questions, and Soreno is not affiliated with them.

Product sense and design

Improve a product or design one from a blank page.

  1. What is your favorite product, and how would you improve it?

    Interviewers sometimes ask what you'd remove from the product. Having a view on that shows you see its trade-offs.

  2. Google: How would you improve Google Maps for tourists?

    A likely follow-up: a tourist who can't read the local language. Have a sense of how your idea works for them.

  3. Meta: How would you help new creators grow on Instagram?

    What does growing mean to a new creator: reach, income or simply getting replies? Each leads to a different product.

  4. How would you improve Spotify's onboarding for new users?

    New users arrive from different places, such as a friend's playlist, a free trial or a new phone. Where they came from shapes what onboarding should do.

  5. How would you improve LinkedIn for people looking for their first job?

    Many first-job seekers are students on a school calendar. What they need in September differs from what they need in April, and timing can be part of the design.

  6. Design an alarm clock for heavy sleepers.

    Decide early whether this is an app, a device or both. That choice sets what's possible and what a first version costs.

  7. Design a product that helps elderly people stay connected with their families.

    Health and hearing change from day to day. Think about how the product behaves on a day the older person isn't feeling well.

  8. Design an expense reporting tool for employees at a 500-person company.

    Companies buy these tools, and a pilot team usually tries one first. A good answer says how the design wins that team over before the whole company sees it.

Metrics and analytical

Define success, set goals and find out why a number moved.

  1. You just launched one-click checkout in a shopping app. How would you measure whether it's a success?

    Some users already had a fast checkout through saved cards. The feature may change little for them and a lot for others, which affects how you read the results.

  2. Instagram Reels watch time dropped 10% week over week. How would you investigate?

    Interviewers often add facts mid-answer, such as "it's only on Android". Showing how each new fact changes your next step is the point of the exercise.

  3. Meta: How would you define and measure a healthy Facebook Group?

    A group that looks quiet can still work well, like a neighborhood group that posts once a week. A good measure doesn't punish it.

  4. Airbnb: What would you choose as Airbnb's north star metric, and why?

    Some stays last one night and some last a month. Whether your metric treats them the same way, and whether it should, is worth raising.

  5. Your A/B test raised checkout conversion by 3%, but average order value fell 4%. Do you ship it?

    Ask what the company is chasing this quarter. A team focused on first purchases reads this result differently from one focused on margin.

  6. Your team wants to send more push notifications to raise daily active users. What guardrail metrics would you set before launching?

    Light users and heavy users react differently to extra messages. A guardrail averaged over everyone can hide damage in one group.

Estimation

Rough numbers with the logic said out loud.

  1. How many rides does Uber do in New York City on a typical weekday?

    Small scope choices, like what a typical weekday is and whether airport trips count, move the answer more than the arithmetic does.

  2. How many smartphones are sold in the US each year?

    Say your plan in one sentence before the first number, so the interviewer can follow it and correct you early.

  3. Estimate how much new storage YouTube needs every day.

    If you know little about video files, say so and reason from something you do know, like the size of a video on your phone.

  4. Estimate the yearly revenue opportunity for a dog-walking app in the US.

    Dog walking is mostly a city service. Adjusting for where people live is what makes the estimate believable.

Execution and prioritization

Trade-offs, deadlines and saying no.

  1. You have three features your stakeholders want and engineering capacity for only one this quarter. How do you decide?

    A cheap way to learn about the two you didn't pick, such as a quick test or a few customer calls, makes next quarter's choice easier. Mention it.

  2. Two weeks before launch, engineering tells you the launch will slip six weeks. What do you do?

    A follow-up to expect: what if the date is tied to a public event you can't move? Have an answer for that version too.

  3. Your biggest customer says they'll leave unless you build a feature that doesn't fit your roadmap. What do you do?

    What you tell the customer this week, before anything is decided, is part of the answer. Holding the relationship while you work it out takes skill.

  4. You've just joined as the PM of an existing team. How would you set its goals for next quarter?

    The team already had goals before you arrived. Interviewers notice whether you'd keep what works instead of resetting everything in month one.

  5. Tell me about a time you had to prioritize between requests from several important stakeholders.

    Pick a story where every stakeholder was senior and had a fair case. It's harder to tell, and better, than one with an obvious winner.

Product strategy

Where to play and whether to build at all.

  1. Should Netflix launch a live sports tier?

    Live sports bring a fixed schedule and a different kind of viewer. What Netflix would have to build to run live events well belongs next to what it would pay.

  2. A US ride-sharing company wants to launch in India. How would you decide whether and how to enter?

    Expect follow-ups on drivers as much as riders. In a new country, supply is often the harder side.

  3. How would you think about a restaurant delivery app expanding into grocery delivery?

    Think about the customer's week: when they'd order groceries and when dinner, and whether they want one app for both.

  4. You lead product at a meditation app. Should you build your own sleep-tracking wearable?

    A useful follow-up to prepare: what would you do if a large rival launched a similar device next month?

AI product

Quality, cost, speed and safety of AI features.

  1. An AI assistant in your app gives a confidently wrong answer in about 3% of responses. What do you do?

    Can users tell when the assistant is wrong? Confident wrong answers do more harm than ones that sound unsure, so start from what the user sees.

  2. Users love your new AI feature, but each request costs you $0.40. How do you decide what to do?

    Model prices change quickly. A strong answer says what you'd do now and what would make you revisit it in six months.

  3. Your AI feature takes 8 seconds to respond. Users say it's too slow, but the faster model gives worse answers. How do you decide?

    How would you hear that it's too slow: complaints, people leaving mid-answer or a survey? Each tells you something different.

  4. You're building a support bot for a software company's help center. Would you use prompting, retrieval, or fine-tuning?

    Define each option in one plain sentence before comparing them. Interviewers check that you know what each one changes, then how you'd decide.

Technical

Enough depth to work with engineers.

  1. Explain what happens when you type a website address into a browser, the way you'd explain it to a non-technical executive.

    This tests whether you can switch levels on demand. Try it at three lengths: one sentence, one minute and five minutes.

  2. At a PM level, how would you design the system behind a "people you may know" feature on a social network?

    The awkward cases, like suggesting an ex or a coworker someone avoids, say a lot about your product judgment.

Behavioral and leadership

Stories from your own work.

  1. Tell me about yourself.

    A PM and a recruiter listen for different things. Have a version ready for each.

  2. Why product management?

    Say why now as well as why PM. Interviewers want to know what changed that makes this the right moment.

  3. Tell me about a product you shipped that you're proud of.

    Choose a launch you can discuss for twenty minutes, since follow-ups will dig into design, data and people.

  4. Tell me about a time you disagreed with an engineer on your team. How did you resolve it?

    Choose a recent story with real stakes, and say how long it took to settle. A disagreement resolved in one meeting can sound too easy.

  5. Tell me about a time you had to get a team to do something when you had no authority over them.

    Influence usually builds over several conversations, so how long it took belongs in the story and makes it easier to believe.

  6. Tell me about a launch that failed. What did you learn?

    Interviewers often ask what you'd do differently with only the information you had then. Separating bad luck from a bad call shows judgment.

  7. Amazon: Tell me about a time a metric looked wrong and you dug into the details yourself to find out why.

    Dive Deep is one of the Leadership Principles Amazon publishes. Read its short description on Amazon's site and choose a story that matches it closely.

Mistakes that cost candidates

  • Features before users

    Jumping to ideas in the first minute skips the part Meta and Google both say they assess: who it's for and what problem comes first.

  • Metrics with no reason

    A list of numbers isn't an answer. Each metric should follow from what the product is for.

  • Silent thinking

    Google tells candidates to think out loud and show how they got there.

  • Team stories with no "I"

    Behavioral answers need your own actions and a result, told as one specific example.

Answer these out loud, get scored

Pick any of these 40 and say your answer to Soreno's AI interviewer. It follows up where the answer is thin and scores it out of 100, quoting your own words.

Questions people ask

What are the most common product manager interview questions?

Product sense questions such as improving a product for a user group, metrics questions about measuring success or a drop in a number, and behavioral questions about conflict, failure and influence. Estimation, strategy, technical and AI questions come up depending on the company and role.

How do I answer a product sense question?

Clarify the goal, choose one user group, rank its problems, offer a few different solutions, pick one and say how you'd measure it. Our PM interview guide lays this out step by step. Meta's guide adds that you should lead and may be asked to sketch.

How should I answer behavioral PM questions?

With one specific story each. Meta suggests the STAR format, and Google suggests showing impact as accomplished X, as measured by Y, by doing Z.

Do PM interviews include technical questions?

Often at a high level. Google's APM page says PMs need to understand how software gets built, and says APM candidates typically have a technical background.

Are these the real questions Google or Meta ask?

No. They are Soreno's own questions in the style of those interviews. Meta's guide says Product Sense questions may use a real Meta product, such as Facebook Groups.

Keep going