72 Product & Project Manager interview questions with detailed answers, sorted from basic to advanced. Free to practice, with progress saved automatically.
Product and project managers guide work from idea to delivery, one focused on product value and the other on schedule and resources. The questions cover product discovery, prioritisation and roadmaps with RICE, metrics such as a North Star Metric, estimation and scheduling, Scrum, stakeholder and risk management, and situational scenarios.
and 6 more topics.
Changing requirements are normal; what is assessed is whether you turn change into a controlled decision or just complain about it. Four things worth saying: 1. Record the change somewhere official — update the ticket, comment on it, or confirm by email. A verbal request…
The most reliable method is to break the work down first, then estimate. Estimating a big task by gut feel is nearly always low, because the parts you have not thought of do not show up in the guess. Process: 1. Split until each piece…
Principle: raise it as soon as the signal appears, with options attached — do not grind silently and announce it on the due date. The value of slip information decays fast; three days of warning lets the team react, three hours does not. A structured…
The three differ in what each is ultimately accountable for. - Business Analyst owns requirement correctness and completeness. Central question: does this solution address the right business problem, and is the description clear enough to build? - Product Owner owns product value. They decide backlog…
General principle: prioritization is a business decision; the BA supplies the basis and facilitates rather than ranking on their behalf. Common techniques: MoSCoW — Must have, Should have, Could have, Will not have (this time). Easy to use, good for fixing the scope of a…
Scope creep is project scope growing during delivery without matching adjustments to time, cost, or resources. It differs from controlled scope change: an approved change is normal; the dangerous part is what slips in silently. Common causes: - Vague initial scope that never states what…
The familiar template: As a [role], I want [capability], so that [value]. Example: As a support agent, I want to look up an order by phone number, so that I do not have to ask callers for an order code. The three parts of a…
A persona is a profile of a typical user group, built from real survey and interview data rather than imagination. It usually covers work context, goals when using the product, current pain points, technical proficiency, and usage environment (device, physical setting, timing). BAs use personas…
Waterfall runs sequentially: analysis, then design, then development, then testing, then deployment. Requirements are fixed and signed off up front; later changes go through a change request process. Agile works in short cycles, each producing something usable and gathering feedback to adjust. Requirements are clarified…
The Agile Manifesto states four value pairs, each in the form "we value the left more than the right" — not that the right is discarded: 1. Individuals and interactions over processes and tools. 2. Working software over comprehensive documentation. 3. Customer collaboration over contract…
INVEST is a six-criterion checklist for user story quality: - I — Independent: buildable on its own, not forced to wait behind another story. Tangled dependencies remove freedom in prioritization. - N — Negotiable: states what is needed and leaves room to discuss how. A…
Acceptance Criteria (AC) are the conditions a user story must satisfy to count as done. They hold the detail the short story sentence cannot carry. Why write them: - To lock in one shared interpretation among BA, developer, tester, and business before work starts. -…
They differ by timing: a risk has not happened yet; an issue already has. Risk — an event that may occur and would affect the project if it did. Described by probability and impact, and handled with preventive or contingency plans. "The payment gateway vendor…
After identifying and ranking risks by probability and impact, there are four response directions: Avoid — change the plan so the risk can no longer occur. Drop the feature that depends on an unreliable third-party system, or choose technology the team already knows instead of…
This is the most common situational question for BA roles. Answer with a sequence and a real example. The sequence: 1. Clarify where the conflict actually lies. Often two parties use the same word with different meanings, or describe two solutions to the same need.…
Product Manager is a job; Product Owner is a role in Scrum. The PM answers "what should we build and why" for the whole product; the PO is accountable for keeping one Scrum team's backlog ordered by value. Product Manager Product Owner --------- Scope The…
A PRD describes what a release or feature must do and why, so design, engineering, QA, and stakeholders share one goal before work starts. A common outline: - Context and problem — who has what problem, with evidence from data or user interviews. - Goals…
An MVP is the smallest version that can test a hypothesis with real users. Eric Ries describes it as the way to collect the most validated learning with the least effort. The key word is viable: users must be able to use it for a…
I do not start from ideas but from problems: every idea has to answer "what problem does it solve, for whom, and what is the evidence". That is the job of product discovery — validating before paying the cost of building. The process I usually…
The core rule: ask about what they did in the past, not what they would do in the future. Interviewees want to be polite and tend to describe an idealized version of themselves, so hypothetical questions produce answers that sound good but are wrong. Question…
RICE is a prioritization score introduced by Intercom that reduces each idea to impact per unit of effort: - Reach — how many people are affected in a period (e.g. 2,000 users per quarter). - Impact — effect per person: 3 = massive, 2 =…
Kano groups features by how they affect user satisfaction, rather than by difficulty or cost: - Basic (must-be) — what users assume is there. Nobody praises it, but its absence causes immediate complaints. E.g. a banking app must support biometric login. - Performance — satisfaction…
A North Star Metric is a single metric that reflects the value users actually get from the product and predicts future revenue. The whole company watches it to see whether it is heading the right way. A good North Star meets three criteria (per Amplitude):…
AARRR, introduced by Dave McClure, splits the user journey into 5 stages to show where the funnel leaks: Stage Question Example metric --------- Acquisition Where do users come from? Installs by channel, CAC Activation Do they experience the core value the first time? % of…
Before choosing metrics, I restate what the feature exists to do — metrics only mean something when tied to the goal written in the PRD. Then I measure in three layers: 1. Adoption — who uses it and how much: % of eligible users who…
The goal is to reject the request without rejecting the person, and to base the decision on shared goals rather than the PM's personal opinion. How I do it: 1. Listen fully and ask for the underlying problem. "Help me understand: which customers are running…
The interviewer does not grade the final number but how you break the problem down and justify each assumption. The four steps: clarify → break down and estimate each piece → explain the biggest assumption → sanity check. 1. Clarify: count jeans owned (not sold…
The triple constraint is the set of three tightly linked constraints scope, time, and cost: change one side and at least one other side must change too, otherwise quality (sitting in the middle of the triangle) is what gets sacrificed. When a client asks for…
RACI is a role map for each task or decision: who is Responsible (does the work), who is Accountable (owns the final result and signs off), who is Consulted (asked for input beforehand), and who is Informed (told once it is done). An example for…
A project is successful when it delivers what was committed (scope, time, cost, quality) and produces the value it was started for. Meeting only the first half means "done", not "successful". Common groups of criteria: - Delivery: handed over on time or within an agreed…
Per the 2020 Scrum Guide, Scrum has 3 accountabilities, 5 events, and 3 artifacts. Accountabilities in the Scrum Team: - Product Owner — maximizes product value, manages and orders the Product Backlog. - Scrum Master — helps the team and the organization use Scrum effectively,…
The two roles differ in what they manage: a Project Manager manages the project (scope, schedule, budget, risk) and is personally accountable for the outcome; a Scrum Master manages how the team works, helping it become self-managing (the Scrum Guide 2020 term) and use Scrum…
Scrum works in a fixed cadence (sprints) with a commitment per sprint; Kanban is a continuous flow controlled by WIP limits (work in progress) on each board column. Scrum Kanban --------- Cadence 1–4 week sprints Continuous, no sprints Roles PO, Scrum Master, Developers No new…
Velocity is the total story points of items that meet the Definition of Done in a sprint. An item that is 90% done still counts as 0. Its main use is forecasting: average the last 3–5 sprints to estimate how much the team can take…
A burndown chart shows remaining work over time in a sprint or release: the horizontal axis is days, the vertical axis is story points (or hours) left, plus an ideal line going from the total down to 0 on the last day. Common shapes: -…
Story points measure the relative size of an item (effort, complexity, uncertainty) against other items, not hours. The reason: people compare "this is twice as big as that" far more accurately than they guess "this takes 13 hours". Benefits from the PM side: - Estimates…
A good status report lets the reader grasp in 30 seconds: is the project on track, why or why not, and what do stakeholders need to do. Details come after. A common structure: - Overall status (RAG) — Green: on plan; Amber: at risk but…
The PM does not answer "yes" or "no" on the spot but runs the request through change control: assess the impact on scope, schedule, cost, and risk, then let whoever has the authority decide based on the numbers. Process: - Log it in the change…
Handle it early, privately, and based on facts: hear each person first, separate the work problem from personal feelings, then have both agree on a way forward. The PM is a facilitator, not a referee picking a side. Steps: - Talk to each person separately:…
Jobs To Be Done looks at users through the "job" they are trying to get done in a specific circumstance, rather than through demographics. In Clayton Christensen's words, people do not simply buy products; they "hire" them to make progress in their lives, and "fire"…
A PM does not need to write code, but must understand enough to discuss trade-offs and make decisions with engineers. The most common trade-off: which parts of a feature are worth building, given how long each part takes and what risk it carries. The level…
The interviewer is not grading the best idea but how you get from users to a solution. A common frame is Lewis Lin's CIRCLES: 1. Comprehend — clarify goal and constraints: which company, is the goal growth or revenue, which platform. 2. Identify the customer…
OKRs (Objectives and Key Results) pair one qualitative Objective — where we want to go — with 3–5 measurable Key Results that answer "how will we know we got there". A team usually has only 1–3 Objectives per quarter. The most common mistake is writing…
I do not treat this as picking one side; I put technical debt on the same scale as features, in terms the business understands. 1. Ask engineering to quantify the impact of the debt — "the code is ugly" is not enough: - Slows features:…
A WBS decomposes the full project scope into a hierarchy of deliverables, down to work packages — the lowest level at which the PM can estimate cost and duration and hand it to one accountable person or team. It is the base for estimates, schedule,…
The Definition of Done (DoD) is the quality bar for a sprint's output; the Definition of Ready (DoR) is the criteria for input — how clear a backlog item must be before it enters a sprint. Definition of Done Definition of Ready --------- Applies to…
The power/interest grid places stakeholders in four boxes by their power over the project and their interest in it, so the PM knows how much communication effort each one needs. Low interest High interest --------- High power Keep satisfied — update enough to keep them…
Three-point estimation asks for three numbers instead of one: O (optimistic — everything goes well), M (most likely), and P (pessimistic — reasonable trouble). The estimate then carries its uncertainty, instead of a single number that looks certain but is really a guess. Two ways…
Risk management is a loop that runs through the whole project, not a kickoff meeting: identify → analyze → plan responses → monitor. 1. Identify: brainstorm with the team and leads, review lessons learned from similar projects, walk through every external dependency and every assumption…
The core difference is who carries the risk when effort overruns. Fixed Price: the vendor does. Time & Material (T&M): the client pays for actual effort, so the client does. Fixed Price Time & Material --------- Client pays One fixed price for the agreed scope…
A Project Manager is responsible for getting the project delivered within scope, on time, within budget and at the agreed quality. Their question is "how do we deliver"; a Product Manager answers "what do we build and why". Day-to-day work of a Project Manager at…
Split into two groups: secondary research (existing data) to get the big picture, then primary research (data you collect) to answer your specific questions. Each has a qualitative side (why) and a quantitative side (how many). Secondary — cheap, do it first: - Industry reports…
Draw the funnel step by step and find the step with the biggest drop compared with the category's own benchmark: product view → add to cart → start checkout → successful payment. Fix the biggest drop first; do not tweak the whole funnel evenly. For…
Initiation is when you settle "why we do it, how far it goes, who decides" before spending money on building. The output is usually a short document (project charter or kick-off deck) signed off by the sponsor and key parties. What to settle: - Measurable…
A good answer has three parts: a real experience that pulled you into product work → evidence you have already done PM-like work → why this role at this company. The interviewer is checking whether you understand what a PM really does, not looking for…
Resource management is matching the right people to the right work over time, so nobody is overloaded, nobody is idle, and you know in advance when you will be short. The basic tool is a resource plan (who works on what, at what % of…
The interviewer is not after a tool name; they want to know how you use the tool to make decisions. Structure the answer: main tool → how it is organised → what you look at to know whether the project is healthy. Common tools at…
A user journey map is a diagram that retells the whole experience of one type of user achieving one specific goal, stage by stage: what they do, think, feel, and where they get stuck. It lets the team see the product from the user's side…
Jakob Nielsen's 10 usability heuristics are 10 rules of thumb for judging whether an interface is easy to use. They are not absolute rules but a checklist for reviewing screens quickly, before paying for tests with real users. 1. Visibility of system status — always…
