Product Manager Interview Flashcards

Question 1

What is a product roadmap?

Accepted Answer

A product roadmap is a strategic, time-oriented plan that communicates direction, priorities, and the rationale (the why) behind what a team intends to build. It aligns stakeholders on outcomes rather than a rigid feature schedule, and good ones tie initiatives to goals or themes and stay flexible as you learn, for example a now/next/later format.

Question 2

What does MVP stand for and mean?

Accepted Answer

An MVP is the smallest releasable version that delivers real value and tests a key hypothesis with actual users, maximizing validated learning per unit of effort. It is about reducing risk and learning fast, not shipping something low-quality; the aim is to validate desirability and viability before investing further.

Question 3

What is the standard format of a user story?

Accepted Answer

The standard format is 'As a [user role], I want [goal] so that [benefit]', keeping work centered on user value and the why, not just the what. Good stories follow INVEST (independent, negotiable, valuable, estimable, small, testable) and pair with acceptance criteria that define done.

Question 4

What is a product backlog?

Accepted Answer

The product backlog is the single ordered list of everything that might be built, features, fixes, tech debt, research, continuously refined and prioritized by the PM or product owner. Higher items are more detailed and ready; lower ones are coarser. It is a living artifact, not a fixed plan, and it feeds sprint planning.

Question 5

Who is a stakeholder in product management?

Accepted Answer

A stakeholder is anyone affected by or able to influence the product: customers, leadership, engineering, design, sales, support, legal, and partners. A PM identifies them, understands their goals and influence (for example via a power/interest map), and manages communication and alignment, since unmanaged stakeholders derail delivery.

Question 6

What are acceptance criteria?

Accepted Answer

Acceptance criteria are the specific, testable conditions a story must satisfy to be accepted, defining its scope and the boundary of done. Often written as Given/When/Then scenarios, they align PM, design, and engineering on expected behavior and edge cases and on how QA will verify it, reducing rework.

Question 7

What is a sprint in Agile?

Accepted Answer

A sprint is a fixed time-box, commonly two weeks, in Scrum during which the team delivers a potentially shippable increment from a committed set of backlog items. It includes planning, daily standups, a review or demo, and a retrospective, creating a regular cadence of delivery and feedback.

Question 8

What is a KPI?

Accepted Answer

A KPI is a quantifiable metric that tracks progress toward a specific objective, such as activation rate or monthly retention. Good KPIs are tied to goals, actionable, and few in number, and ideally paired with a counter-metric to catch unintended harm. They differ from vanity metrics that look good but do not drive decisions.

Question 9

What is a North Star metric?

Accepted Answer

The North Star metric is the one measure that best proxies the value customers get and that predicts sustainable growth, such as nights booked for Airbnb. It aligns the whole team on a shared outcome and is decomposed into input drivers teams can influence. It should reflect customer value, not just revenue.

Question 10

Why do product managers prioritize features?

Accepted Answer

PMs prioritize because demand for work always exceeds capacity, so sequencing for the most value relative to effort and risk maximizes impact. Frameworks like RICE, value-versus-effort, and MoSCoW make trade-offs explicit and defensible, and prioritization should map back to strategy and goals, not just the loudest request.

Question 11

What is an A/B test in product?

Accepted Answer

An A/B test randomly splits users between a control and one or more variants and measures a primary metric to learn which performs better, attributing the difference causally. It needs a hypothesis, enough sample size and power, and discipline against peeking; it de-risks decisions by replacing opinion with evidence.

Question 12

What is a user persona?

Accepted Answer

A persona is a research-based, semi-fictional archetype of a key user segment capturing their goals, behaviors, pain points, and context. It builds shared empathy and keeps decisions user-centered, helping prioritize features for whom they matter. Personas should be grounded in real research, not invented assumptions.

Question 13

What is customer churn?

Accepted Answer

Churn is the rate at which customers stop using or paying over a period: churn rate = customers lost in the period / customers at the start. It is the inverse of retention and directly caps growth, since a leaky bucket offsets new acquisition. Track logo churn (accounts) and revenue churn separately, and watch for negative net churn from expansion.

Question 14

What does retention measure?

Accepted Answer

Retention measures the share of users still active after some time from signup, often shown as a cohort retention curve over days or weeks. A curve that flattens rather than decaying to zero signals product-market fit and a sticky core. Retention is usually more valuable than acquisition because retained users compound in value.

Question 15

What is a wireframe?

Accepted Answer

A wireframe is a low-fidelity blueprint of a screen's structure, content, and layout, deliberately skipping color and polish so discussion focuses on flow and hierarchy rather than aesthetics. It is cheap to iterate, aligns the team early, and precedes higher-fidelity mockups and prototypes.

Question 16

What is the difference between a roadmap and a backlog?

Accepted Answer

A roadmap communicates strategy, the direction, themes, and outcomes over time horizons, to align stakeholders, while the backlog is the granular prioritized list of specific items the team executes. The roadmap answers why and what-direction; the backlog answers exactly what is next. They connect, but mixing them turns a roadmap into a brittle release schedule.

Question 17

What is a PRD?

Accepted Answer

A PRD captures the problem, target users, goals and success metrics, scope, requirements, and constraints for a feature, creating shared understanding across design and engineering. Modern PRDs are lean and living, focusing on the problem and outcomes over exhaustive specs, and they link to designs and open questions.

Question 18

What is a go-to-market (GTM) strategy?

Accepted Answer

A GTM strategy defines how you bring a product to market: target segment and positioning, pricing and packaging, messaging, channels (sales-led, product-led, partnerships), and launch plan, aligning product, marketing, sales, and support. A great product still fails without a GTM that reaches and converts the right customers.

Question 19

What is the difference between a feature and a benefit?

Accepted Answer

A feature is a capability or attribute, what the product does, while a benefit is the outcome or value the user gets, why they care. Customers buy benefits, so messaging and prioritization should translate features into benefits, for example 'one-click checkout' (feature) means 'buy faster with less friction' (benefit).

Question 20

What does DAU measure?

Accepted Answer

DAU counts unique users who perform a meaningful action on a given day, and the definition of active must be chosen deliberately to reflect real value rather than trivial opens. Paired with MAU, the DAU/MAU ratio (stickiness) shows how many monthly users return daily, a quick engagement gauge.

Question 21

What does MAU stand for?

Accepted Answer

MAU counts unique users active within a 30-day window by a chosen activity definition. It is a top-line engagement and reach metric, and DAU/MAU gives stickiness, the fraction of monthly users active on an average day. Be wary of treating logins as active if they do not reflect value received.

Question 22

What is a conversion rate?

Accepted Answer

Conversion rate = (users who complete the action / users who had the opportunity) x 100, for example visitors who sign up or trials that become paid. It is measured per funnel step to find drop-off, and improving it is often cheaper than buying more traffic. Always define the numerator and denominator precisely.

Question 23

What is product discovery?

Accepted Answer

Product discovery is the work of deciding what is worth building, validating that a problem is real and a solution is desirable, viable, and feasible, before heavy investment in delivery. It blends customer interviews, data, and rapid experiments or prototypes to reduce the risk of building the wrong thing, ideally as a continuous activity.

Question 24

What is the difference between qualitative and quantitative research?

Accepted Answer

Qualitative research, through interviews, usability tests, and observation, explores the why and how behind behavior with rich, small-sample insight, great for generating hypotheses. Quantitative research, through analytics, surveys, and A/B tests, measures how much or how many at scale to validate them. Strong PMs triangulate: qual to find problems, quant to size and confirm them.

Question 25

Why is user feedback important for a PM?

Accepted Answer

User feedback grounds decisions in reality, validating or refuting assumptions and surfacing unmet needs, friction, and opportunities a PM cannot see from inside. It should be gathered continuously through interviews, support tickets, surveys, and usage data, and weighed against data, since users describe problems well but proposed solutions less reliably.

Question 26

What is scope creep?

Accepted Answer

Scope creep is the gradual, unmanaged addition of requirements beyond what was agreed, which inflates timelines, dilutes focus, and risks missing the goal. PMs manage it by defining clear scope and success criteria, saying no or trading off explicitly, and routing new ideas to the backlog rather than into the current commitment.

Question 27

What is a product release?

Accepted Answer

A release makes new functionality available to users; modern practice separates deploy (shipping code) from release (exposing it), so feature flags enable gradual or targeted rollouts, canaries, and instant rollback. This de-risks launches and lets PMs control exposure independently of engineering's deploy cadence.

Question 28

What is a 'definition of done'?

Accepted Answer

The Definition of Done is a team-wide standard of quality, for example coded, tested, reviewed, documented, and deployable, that every item must meet to be done, preventing hidden incomplete work. Unlike acceptance criteria, which are specific to one story, the DoD applies to all work, ensuring consistent quality and a truly shippable increment.

Question 29

What is a roadmap theme?

Accepted Answer

A roadmap theme is a strategic area of focus, for example reducing onboarding friction, that groups related initiatives under a shared outcome, letting the roadmap communicate intent and value rather than a list of features and dates. Themes keep teams aligned on goals while leaving flexibility in how to achieve them.

Question 30

What does OKR stand for?

Accepted Answer

OKRs pair a qualitative, ambitious Objective (where you want to go) with a few measurable Key Results (how you know you got there). They align and focus teams on outcomes, cascade across the org, and are typically set quarterly. Key Results should be outcome metrics, not task lists, and with stretch goals around 70% attainment is healthy.

Question 31

What is a customer segment?

Accepted Answer

A customer segment is a group sharing meaningful characteristics, demographics, firmographics, behaviors, or jobs-to-be-done, so they respond similarly to a product or message. Segmentation lets PMs target, prioritize, and tailor for the highest-value or most underserved groups instead of treating all users as one.

Question 32

What is a value proposition?

Accepted Answer

A value proposition concisely states who it is for, the problem it solves, the benefit delivered, and why it is better than alternatives. It anchors positioning, messaging, and prioritization. Strong value propositions are specific and customer-outcome-focused (jobs, pains, gains), not a list of features.

Question 33

What is a user journey?

Accepted Answer

A user journey maps the end-to-end steps, touchpoints, thoughts, and emotions a user experiences to accomplish a goal, often across channels and over time. Journey mapping reveals friction, drop-off, and moments that matter, helping PMs prioritize improvements where they most affect the experience and conversion.

Question 34

What is a beta release?

Accepted Answer

A beta exposes a near-complete product to a limited, often opt-in audience to gather real-world feedback, surface bugs, and validate value before general availability. Betas can be closed (invite-only) or open, and clear goals, success criteria, and feedback channels make them a learning step, not just a soft launch.

Question 35

What does user engagement measure?

Accepted Answer

Engagement captures how actively and frequently users derive value, measured by frequency (DAU/MAU), depth (key actions per session), and breadth (features used). It is a leading indicator of retention and value, but it should track meaningful actions tied to the product's core value, not vanity interactions.

Question 36

What is 'time to value'?

Accepted Answer

Time to value (TTV) is how long from signup until a user first experiences the core benefit, the aha moment. Shorter TTV strongly predicts activation and retention, so PMs streamline onboarding to reach that moment. It pairs with defining the activation event that correlates with long-term retention.

Question 37

Why is stakeholder buy-in important for a roadmap?

Accepted Answer

Buy-in means stakeholders understand and support the roadmap's priorities and rationale, which secures funding, resources, and cross-team cooperation and prevents later derailment or reprioritization churn. PMs earn it by involving stakeholders early, tying the roadmap to shared goals, and being transparent about trade-offs.

Question 38

What is the difference between a bug and a feature request?

Accepted Answer

A bug is a defect where the product behaves differently from its intended or expected behavior, while a feature request asks for new capability that does not exist yet. The distinction affects prioritization and SLAs, since bugs are weighed by severity and impact against feature value, and ambiguous cases hinge on what expected behavior was specified.

Question 39

What does NPS stand for?

Accepted Answer

NPS asks how likely you are to recommend us on a 0-to-10 scale; it equals percent promoters (9-10) minus percent detractors (0-6), ranging from -100 to +100. It is a simple loyalty benchmark and trend indicator, but a lagging, blunt signal, so pair it with the open-text why and product metrics for actionable insight.

Question 40

Name one common prioritization framework.

Accepted Answer

Common frameworks include RICE (Reach x Impact x Confidence / Effort), value-versus-effort (favor high-value, low-effort quick wins), MoSCoW (Must, Should, Could, Won't), and Kano (basic, performance, delighter). They make trade-offs explicit and comparable, but the scores are estimates, so use them to structure judgment, not replace it.

Question 41

What is user onboarding?

Accepted Answer

Onboarding guides new users from signup to their first meaningful value (activation) as quickly and smoothly as possible, through setup, education, and reducing friction. Good onboarding focuses on the shortest path to the aha moment rather than feature tours, and it strongly drives activation and downstream retention.

Question 42

What is a product hypothesis?

Accepted Answer

A product hypothesis is a falsifiable statement linking a change to an expected outcome, for example 'if we simplify signup, then activation will rise because friction drops'. Framing work as hypotheses with a metric and threshold turns building into learning, so you can validate or kill ideas with evidence.

Question 43

Why send regular stakeholder updates?

Accepted Answer

Regular updates keep stakeholders aligned on progress, upcoming work, risks, and decisions, preempting surprises and building the trust that smooths future trade-offs and resourcing. Effective updates are concise and tailored, outcomes and risks for executives, detail for the team, and they create a reliable cadence of transparency.

Question 44

What is a feature flag in product terms?

Accepted Answer

A feature flag is a runtime switch that decouples release from deploy, letting you ship code disabled and turn it on gradually by percentage or cohort, run experiments, and instantly roll back a problem feature without redeploying. The trade-off is added complexity and the need to retire stale flags.

Question 45

What is a 'now/next/later' roadmap?

Accepted Answer

A now/next/later roadmap organizes work by time horizon and confidence rather than precise dates: now is committed and detailed, next is likely, and later is directional. This communicates direction while honestly reflecting decreasing certainty over time, reducing the false precision and pressure of date-based roadmaps.

Question 46

What is the goal of a customer interview?

Accepted Answer

A customer interview aims to deeply understand the user's problems, context, and behavior, so the goal is to listen and learn, not to sell or seek validation. Best practice favors open, non-leading questions about past real behavior over hypothetical or leading ones, as in The Mom Test, to get unbiased insight.

Question 47

What does feature adoption measure?

Accepted Answer

Feature adoption measures the share of eligible users who try and continue using a new feature, often split into breadth (how many adopt) and depth (how much they use it). Low adoption may signal poor discoverability, weak value, or a mismatched audience, guiding whether to iterate, promote, or sunset the feature.

Question 48

What does a sprint burndown chart show?

Accepted Answer

A burndown chart plots remaining work, story points or tasks, against time in a sprint, with an ideal line to the end date. Comparing actual to ideal reveals whether the team is on track, ahead, or behind, and a flat line warns of blockers or scope issues, supporting daily inspection and adaptation.

Question 49

Why must a PM make trade-offs?

Accepted Answer

PMs make trade-offs because capacity is finite, so every yes is an implicit no to something else; choices weigh value and impact, cost and effort, risk, and timing against strategy. Making trade-offs explicit, with the reasoning visible, builds trust and keeps the team focused on the highest-leverage work rather than pleasing everyone.

Question 50

Why define a success metric before building a feature?

Accepted Answer

Defining a success metric and target before building forces clarity on the intended outcome and lets you objectively evaluate impact afterward instead of rationalizing. It also exposes whether the feature is worth doing, and pairing it with a counter-metric guards against winning one number while harming another.

Question 51

What four factors make up the RICE prioritization score?

Accepted Answer

RICE scores each initiative as (Reach x Impact x Confidence) / Effort. Reach is users affected per period, Impact is the effect size per user (often a 0.25-to-3 scale), Confidence is a percentage discount for uncertainty, and Effort is person-time. Dividing by effort yields value-per-effort to rank items. It structures judgment but relies on estimates, so keep inputs consistent.

Question 52

What do the categories in MoSCoW prioritization mean?

Accepted Answer

MoSCoW buckets requirements into Must (non-negotiable for this release), Should (important but not vital), Could (nice-to-have if time allows), and Won't (explicitly out of scope this time). It is fast and great for scoping a release and managing expectations, but it is qualitative, so guard against everything becoming a Must.

Question 53

How does opportunity cost apply to roadmap decisions?

Accepted Answer

Opportunity cost is the value of the best alternative you give up by committing finite capacity to a given initiative. Sound prioritization compares each option not just to doing nothing but to the next-best use of the same resources, which is why a good idea can still be the wrong one if something better is available.

Question 54

What does the Kano model classify?

Accepted Answer

The Kano model classifies features by their effect on satisfaction: basic (must-haves whose absence frustrates but presence does not delight), performance (more is better, satisfaction scales roughly linearly), and delighters (unexpected features that drive outsized satisfaction). It guides balancing table-stakes with differentiators, and notes that delighters become expected over time.

Question 55

What is the Jobs To Be Done framework?

Accepted Answer

JTBD reframes products around the progress a customer is trying to make, the functional, emotional, and social job they hire a solution for, rather than demographics or features. Famously people hire a milkshake for a boring commute. It surfaces the real competition and unmet outcomes, guiding innovation toward what customers actually want done.

Question 56

What is the difference between a leading and lagging indicator?

Accepted Answer

A leading indicator is an early, predictive signal you can influence now, such as activation rate or trial starts, that precedes results, while a lagging indicator measures the outcome after the fact, such as revenue or churn. PMs steer with leading indicators because lagging ones confirm too late, while tracking both to verify the leading metric truly drives the outcome.

Question 57

What does activation mean in the AARRR funnel?

Accepted Answer

Activation is the moment a new user first realizes the product's core value, the aha, operationalized as a measurable event correlated with retention, for example sent first message or invited a teammate. Defining and optimizing the activation event, and the time to reach it, is one of the highest-leverage levers on retention and growth.

Question 58

What are the stages of the AARRR pirate-metrics funnel?

Accepted Answer

AARRR, or pirate metrics, frames the user lifecycle as Acquisition (find you), Activation (first value), Retention (keep coming back), Referral (tell others), and Revenue (monetize). It gives a shared funnel to instrument and diagnose where users drop off, focusing effort on the weakest stage rather than only top-of-funnel growth.

Question 59

What does a cohort analysis reveal?

Accepted Answer

Cohort analysis groups users by a shared start point, such as signup month, and tracks their behavior over time, separating the effect of tenure from calendar-time changes. It reveals whether retention is improving across newer cohorts and isolates the impact of product changes, which blended all-user metrics mask.

Question 60

Why wait for statistical significance before calling an A/B test?

Accepted Answer

Waiting for statistical significance, a low p-value at a pre-set threshold, reduces the risk of acting on random noise as if it were a real effect. But significance is not enough: predefine the sample size and duration to avoid peeking and false positives, check the practical effect size, and account for novelty effects and multiple metrics.

Question 61

Why does an A/B test need a sufficient sample size?

Accepted Answer

Adequate sample size gives the test enough statistical power to detect a real effect of the size you care about and to keep false positives in check; with too few users, results swing on noise. Required sample size grows with smaller expected effects, higher baseline variance, and stricter alpha and power, so estimate it up front via a power calculation.

Question 62

What is a guardrail metric in experimentation?

Accepted Answer

A guardrail or counter metric protects against tunnel vision: while optimizing a primary metric, you monitor guardrails like latency, churn, support tickets, or revenue to ensure the change does not cause harm elsewhere. A win on the target that breaches a guardrail is not a real win, so guardrails keep local optimizations globally healthy.

Question 63

What does customer lifetime value (LTV) represent?

Accepted Answer

Customer lifetime value estimates the total, often gross-margin, value a customer generates over their relationship. A simple form is LTV = ARPU x gross margin x average lifetime, or ARPU x margin / churn rate. It bounds how much you can profitably spend to acquire and retain, and improving retention raises LTV super-linearly.

Question 64

What is customer acquisition cost (CAC)?

Accepted Answer

Customer acquisition cost = total sales and marketing spend in a period / new customers acquired in that period. It should be measured per channel and fully loaded, including salaries and tools. CAC is only meaningful against LTV and payback period; a low-CAC channel that attracts poorly-retaining users can still be unprofitable.

Ready to practice the full interview?