In a product manager interview, ask questions that reveal how much product authority the role really has: whether the team is given problems to solve or features to build, who sets the goals and the roadmap, which decisions you could make yourself, what data you can get without waiting for an analyst, and how launches and failures are reviewed. The answers tell you whether you would be a product manager or a project coordinator with a PM title.
Below are 28 questions in four groups, what each answer tells you, who to ask what across a PM loop, what to skip, and a worked follow-up. For the questions you will be asked, see our product manager interview questions.
Three things decide what a PM job really is
The PM title covers very different jobs. Three things decide which one you would have: your scope (problems or features), your decision rights, and your access to users, data and engineers. Marty Cagan's book Empowered (2020) gives a useful way to frame the first: “feature teams” are handed a roadmap of features to build, while “empowered product teams” are given problems to solve and are judged on outcomes.
| Signal | Problem-focused team | Feature-focused team |
|---|---|---|
| The roadmap | Outcomes and problems, with features chosen by the team | A list of features with dates |
| Success | A metric moved | Shipped on time |
| Discovery | PM, designer and engineers talk to users regularly | Requirements arrive from sales or executives |
| Data | The PM can query it directly | Requests go to a queue |
| Saying no | The PM can, with reasons | Rarely, and only by escalating |
Neither is automatically wrong; a feature team at a well-run company can be a good job. But you should know which one you are joining, and the questions below are how you find out.
1. Scope and decision rights
Why this group works: these go straight to the question above. Hiring managers who give specific examples usually run teams with real ownership.
- “Is the team given problems to solve or a list of features to build?” The single most revealing PM question.
- “Who sets the goals for this product area each quarter, and how much does the PM shape them?” Tells you whether you'd set direction or receive it.
- “When a big customer asks sales for a feature, how is that decided?” Shows who really controls the roadmap.
- “Which decisions could I make without escalating: experiments, scope cuts, small pricing changes?” Your real autonomy, in concrete terms.
- “Who does this role report to: a product leader, engineering, or a general manager?” The reporting line changes your influence.
- “How many engineers and designers would I work with, and are they shared with other PMs?” Shared teams mean constant negotiation.
- “What does this PM own that another team might think it owns?” Surfaces turf overlaps before they surprise you.
2. Discovery and data
Why this group works: how a team learns decides how good its product decisions are. Specific answers about user research and data access are a strong sign. Our product sense interview guide covers the thinking interviewers look for on the other side.
- “How often do PMs here talk to users, and who sets up those conversations?” Monthly or more, with help from research, is healthy.
- “Can I query product data myself, or do requests go through an analyst?” Waiting days for every number slows everything.
- “Can the team run A/B tests, and how long does a typical test take to read?” Tells you whether you can learn quickly.
- “Which metric does this team report to leadership, and has it moved this year?” Shows what you'd be judged on.
- “Is there a written spec or press-release document before building, and who reviews it?” Amazon's “working backwards” press release and FAQ, described in the 2021 book Working Backwards, is one well-known version.
- “How is feedback from support and sales collected and shared?” Shows whether customer signal reaches the team.
- “What's a recent decision the data didn't settle, and how was it made?” Reveals how judgment works when evidence runs out.
3. Working with engineering and design
Why this group works: a PM's day is mostly collaboration. Ask these of the engineers and designers in your loop; their answers are usually more candid than the manager's.
- “Who sketches the first version of a solution: the PM, the designer, or the three of you together?” Joint problem solving is a good sign.
- “How does the team plan: sprints, longer cycles, or continuous flow?” Longer cycles, like the six-week cycles in Basecamp's Shape Up (2019), change how scope is managed.
- “How is technical debt weighed against new features?” Shows whether engineers trust the PM.
- “When a date slips, who tells stakeholders and how?” Tells you who carries the bad news.
- “How are design reviews run, and who has the final say on the user experience?” Clarifies decision rights with design.
- “What do engineers here wish PMs did more of?” An honest answer is a gift.
- “What happens at launch: who handles marketing, sales enablement and support?” Tells you how much go-to-market work falls on you.
4. Outcomes, failure and growth
Why this group works: how a company handles a failed bet tells you how safe it is to take risks there. The growth questions tell you how PMs are judged.
- “How are launches reviewed afterward: is there a written review with metrics?” Written reviews mean the team learns.
- “What's a product bet the team stopped, and how did it decide to stop?” Stopping well is a sign of a mature team.
- “How are PMs evaluated: outcomes, execution, or stakeholder feedback?” Tells you what to optimize for.
- “What does the PM career ladder look like, and where does this role sit?” Clarifies level and next steps.
- “What did the last PM promoted on this team do to earn it?” A real example beats a framework.
- “Would I inherit an existing product with users, or start something new?” Very different first years.
- “By the end of my first year, what would you want this PM to have changed?” Gives you the target in the manager's words.
Questions to skip in a PM interview
| Skip | Why | Ask instead |
|---|---|---|
| “What does your product do?” | Use the product before the interview | Ask about something you noticed using it |
| “Will I get to set the vision?” | Abstract, and the answer is always yes | “Which decisions could I make without escalating?” |
| A long pitch for your own feature idea, framed as a question | Sounds like you've decided before learning | Share one idea briefly, then ask what they've tried |
| Business metrics questions to an engineer | They may not own them | Ask engineers about collaboration and planning |
| Salary and level with the hiring manager | Usually the recruiter's area | Ask the recruiter |
How many to ask, and when
- Hiring manager: scope and decision rights (group 1) and outcomes (group 4).
- Engineer or tech lead: collaboration and planning (group 3).
- Designer: design reviews and who sketches solutions.
- Data scientist or analyst: data access and experiments (group 2).
- Executive: one question about which product bets matter most this year.
- Ask two or three per interview. PM loops are long, with several interviews in a day; our PM onsite guide shows how they are usually structured. For AI product roles, see our AI product manager questions.
Turning an answer into a follow-up
An example we wrote to show the move:
You: “Is the team given problems to solve or a list of features to build?”
Hiring manager: “A mix. Leadership sets themes each quarter, and we fill in the features.”
Your follow-up: “Could you give me an example of a theme from this quarter and how the team chose what to build for it? Did anything get dropped after you talked to users?”
Why it works: it tests whether “we fill in the features” means real discovery or just breaking down a list. An example of something dropped is the strongest evidence that the PM has room to decide.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant whose free AI mock interview builds product questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10, so you can rehearse product sense and execution answers out loud. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included, and the browser demo has 145 practice questions in 10 tracks with typed answers scored out of 10 and no signup. If you ever consider live help in a real interview, follow your employer's rules.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What questions should I ask in a product manager interview?
Ask whether the team gets problems or features, who sets the goals, which decisions you could make yourself, how you would get data, how PMs work with engineering and design, and how launches and failures are reviewed.
What should I ask a hiring manager for a PM role?
Ask about scope and decision rights: who sets the quarterly goals, what you could decide without escalating, who the role reports to, and what they would want you to have changed by the end of the first year.
What questions show product sense?
Questions about users and outcomes: how often PMs talk to users, which metric the team reports, and how a recent decision was made when the data didn't settle it.
What should I ask an engineer in a PM interview?
Ask how the team plans, how technical debt is weighed against features, what engineers wish PMs did more of, and who sketches the first version of a solution.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview