AI HR
Prova

Interview questions

Product manager interview questions

PM interviews test how you think out loud. Interviewers care less about the final answer than about how you frame the user, choose a metric and make a trade-off. Below are the questions that show up across most PM loops and how to land them.

Rehearse this interview by voice2 minutes without an account, 3 more after sign-up. No card.

Questions by stage and what a strong answer includes

  1. 01

    Tell me about a product you shipped and what you owned.

    Strong answer: The problem, your part versus the team's, the launch and a metric that moved. Recruiters screen for real ownership, not coordination of someone else's roadmap.

  2. 02

    What kind of products have you worked on: B2B, consumer, platform?

    Strong answer: The type, the user, the scale (users or revenue range) and your stage: zero to one, growth or mature. It lets the recruiter place you against the team.

  1. 03

    Tell me about a time you disagreed with engineering on scope.

    Strong answer: The disagreement, how you separated must-haves from nice-to-haves using user evidence, the compromise and what shipped. Respect for engineering constraints is what they listen for.

  2. 04

    Describe a feature that failed after launch.

    Strong answer: What you expected, what the data showed, how quickly you noticed and what you did: iterate, roll back or kill it. A clear lesson, not excuses.

  3. 05

    How did you say no to a powerful stakeholder?

    Strong answer: The request, why it did not fit the strategy or the data, how you explained it and what you offered instead. Saying no with a reason and an alternative is the core PM skill.

  1. 06

    How would you improve our product?

    Strong answer: Pick one user segment, name a specific pain backed by something you observed, propose a solution and how you would measure it. Generic feature lists without a user score poorly.

  2. 07

    Daily active users dropped 8% last week. How do you investigate?

    Strong answer: Check data first (tracking, release, seasonality), then segment by platform, region, cohort and funnel step, form hypotheses and decide what to look at next. Structure beats speed.

  3. 08

    You have five requests and capacity for two. How do you prioritize?

    Strong answer: A framework such as RICE or impact versus effort, applied to the actual options, plus the judgment call the framework does not capture, such as strategic fit or a contractual commitment.

  4. 09

    What would your north star metric be for this product?

    Strong answer: A metric that reflects user value, not only revenue, with two or three supporting metrics and one counter-metric that guards against gaming it.

  1. 10

    Design a product for a specific user, for example commuters who cycle.

    Strong answer: Clarify the goal, choose a segment, list their pains, prioritize one, sketch a solution, define success metrics and name risks. Keep talking through the trade-offs.

  2. 11

    Where do you see this market going in three years?

    Strong answer: A view with reasoning: shifts in user behavior, technology, regulation or competitors, and what the company should do about it. Opinions are welcome if you can defend them.

  1. 12

    What matters to you in this offer beyond salary?

    Strong answer: Scope of the area you would own, the team you would work with, equity and level. Asking about the product area is often more useful than negotiating base by a small amount.

One answer, before and after

Describe a feature that failed after launch.

Weak answer

We launched a feature that users didn't really adopt. We learned that we needed to talk to users more before building. Now I always do user research first.

Strong answer in STAR

Situation
At a B2B invoicing tool I launched recurring invoice templates, expecting them to cut time to send an invoice for our small business users.
Task
The goal was 25% of active accounts using templates within two months. After six weeks adoption was 6%.
Action
I watched session recordings and ran eight calls with users who had tried the feature once. Most expected templates to live inside the client record, not a separate menu. With design we moved the entry point to the client page and added a prompt after the second manual invoice to the same client.
Result
Adoption reached 22% four weeks after the change, and median time to send a repeat invoice fell from four minutes to under one. I now ship placement experiments before a full launch.

Why it works

The weak answer jumps to a lesson without evidence. The strong one shows a target, honest numbers, a diagnosis grounded in user behavior and a measured fix. Numbers in the example are illustrative: use your own.

How a practice session works

  1. 01

    Pick a stage, paste the job posting

    Recruiter screen, HR interview, hiring manager, final round or offer talk. Add the posting and your resume so the questions are about your role, not generic.

  2. 02

    Talk it through by voice

    The interviewer speaks the language you chose, interrupts, follows up and digs into details like on a real call. If the connection drops, you pick up where you stopped.

  3. 03

    Get the review and drills

    A score, 7 skills, what you said next to a stronger way to say it, plus pace, filler words and talk share. Weak spots turn into short drills.

Rehearse this interview by voice

Related roles