# Product Management Interview Questions (2026) > 30 Product management interview questions from junior to senior, each with what a strong answer shows. Practise, then prove the skill with evidence. Source: https://getlemma.io/skills/product-management/interview-questions Product management interviews test how you choose problems, measure outcomes and lead people you do not manage. Expect product sense cases, metrics and experiment questions, estimation, prioritisation and behavioural stories. The 30 questions below run from junior to senior. Each one notes what a strong answer covers and the trap that weak answers fall into. [How Lemma tests product management](https://getlemma.io/skills/product-management) ## Junior Product management interview questions 1. ### 1.What does a product manager do, and how is that different from a project manager? What a strong answer shows A strong answer says the PM owns which problems get solved and why, and is judged on outcomes such as retention or revenue. A project manager owns delivery: scope, schedule and dependencies. The weak answer describes a PM as a backlog administrator who writes tickets and runs meetings. 2. ### 2.Pick a product you use often. How would you improve it? What a strong answer shows Strong candidates name who the product serves and pick one user segment and one painful moment. They propose a few options and choose one with a reason. They close with how they would measure whether it worked. The trap is listing features you personally want without saying who has the problem or why it matters to the business. 3. ### 3.What is a north star metric, and what would you pick for a product you know well? What a strong answer shows A north star captures the value users get, not just activity, and it should lead to revenue over time. A strong answer picks something like weekly listeners who finish a playlist, then explains why raw sign-ups or page views would mislead. Weak answers choose revenue itself, which lags and says little about user value. 4. ### 4.You have ten feature requests and capacity for three. How do you decide? What a strong answer shows Start from the team's goal, then judge each request by expected impact on that goal, confidence in the evidence and effort. A strong answer groups requests that solve the same underlying problem and says what will be told to the people who asked. The trap is ranking by who shouted loudest or by a scoring sheet nobody questions. 5. ### 5.How would you run a user interview, and what questions would you avoid? What a strong answer shows Ask about specific past behaviour, such as the last time they did the task, and let them talk. Avoid leading questions and hypotheticals like 'would you use this?', because people are poor at predicting their own behaviour. A strong answer also mentions recruiting the right users and taking notes that separate quotes from interpretation. 6. ### 6.How do you write a good user story or requirement for engineers? What a strong answer shows A good requirement states the user, the problem, the outcome wanted and clear acceptance criteria, including edge cases and error states. It leaves the solution open where engineers know better. Weak answers either dictate implementation detail or hand over a vague one-liner and expect the team to fill the gaps. 7. ### 7.Estimate how many people in your country order from a food delivery app in a typical week. What a strong answer shows The interviewer is grading structure, not the final number. A strong answer states assumptions out loud and segments the population, for example by age or by city versus rural. It then sanity-checks the result against something known. The trap is silent maths or one giant guess with no way to test which assumption drives the answer. 8. ### 8.We launched a feature and very few people use it. What do you do? What a strong answer shows First check the basics: is it discoverable, is tracking correct, and did the right users see it? Then look at the funnel from exposure to first use to repeat use, and talk to users who tried it and stopped. A weak answer jumps straight to a redesign or a marketing push without finding where people drop off. 9. ### 9.What is an A/B test, and when would you choose not to run one? What a strong answer shows An A/B test randomly splits users between versions so a difference in a chosen metric can be attributed to the change. Skip it when traffic is too low, when the change is a clear fix, or when testing would be unethical. Weak answers treat every decision as needing a test. 10. ### 10.How do you work with designers and engineers day to day? What a strong answer shows A strong answer shows the PM bringing the problem and evidence early, then deciding the solution together rather than handing over a spec. It mentions joint discovery, quick trade-off calls during the build and shared ownership of the result. The trap is describing a relay where the PM writes, design draws and engineering builds. ## Mid-level Product management interview questions 1. ### 11.Weekly active users dropped sharply last week. How would you investigate? What a strong answer shows First rule out data problems such as a broken tracking event or a definition change. Then segment by platform, region, app version, channel and new versus returning users, and check releases, outages, seasonality and competitor moves. A strong answer forms hypotheses before slicing data and says what it would do once the cause is found. 2. ### 12.Design a product that helps older adults manage their medication. What a strong answer shows Strong answers clarify the goal, then split users: the older adult, a family carer and perhaps a pharmacist. They pick one segment and one core problem, such as missed doses, and design for real constraints like eyesight and low smartphone confidence. Weak answers rush to an app with many features and never define success. 3. ### 13.Your A/B test shows a significant lift in conversion, but retention fell in the treatment group. What do you do? What a strong answer shows Do not ship on the primary metric alone. Check whether the retention drop is real, then ask whether the change pulled in lower-intent users or created a worse experience after conversion. A strong answer weighs long-term value per user against the short-term lift and may propose a variant that keeps the gain without the harm. 4. ### 14.What guardrail metrics would you set for a change to the checkout flow? What a strong answer shows Guardrails are metrics that must not get worse while you chase the main one. For checkout, good picks include refund and chargeback rates, support contacts, page load time, payment errors and repeat purchase. Weak answers list only conversion and average order value, which a manipulative design could raise while hurting customers. 5. ### 15.Which prioritisation frameworks have you used, and where do they break down? What a strong answer shows A strong answer names one or two, such as RICE or a value-versus-effort grid, and explains how they were used in practice. It then names the limits: scores hide shaky estimates, they ignore strategy and dependencies, and teams can game them. The trap is presenting a framework as the decision rather than as a way to structure the debate. 6. ### 16.A senior stakeholder insists on a feature you think is the wrong call. How do you handle it? What a strong answer shows Start by understanding the goal behind the request, because the real need is often valid even if the solution is not. Then share the evidence and the trade-off, such as what would be delayed. A strong answer offers an alternative or a cheap test, and knows when to disagree and commit. 7. ### 17.How do you build a roadmap, and how do you communicate changes to it? What a strong answer shows A strong roadmap is organised around outcomes and problems, with firm commitments near term and looser themes further out. Changes are explained with the new evidence that caused them and what moves as a result. The weak answer is a dated feature list that is treated as a promise and quietly slips. 8. ### 18.At the level a PM needs, explain what happens when a user taps 'Pay' in a mobile app. What a strong answer shows The app calls your backend API, which creates a payment with a payment provider and gets a result back, often asynchronously through a webhook. A strong answer mentions failure cases such as timeouts, retries and avoiding double charges. The trap is either hand-waving or diving into detail that never connects to product decisions. 9. ### 19.How would you plan the launch of a significant new feature for existing customers? What a strong answer shows Cover who it is for, the message, the channels and the rollout, such as a beta group before a staged release. A strong answer prepares support and sales, sets success and guardrail metrics, and has a rollback plan. The trap is treating launch as a single announcement on release day. 10. ### 20.Tell me about a time you influenced a decision without having authority over the people involved. What a strong answer shows Use a real situation with stakes, then show how you learned what the other side cared about and built a case in their terms. Strong answers name what you actually did, such as sharing user evidence or running a small test, and the result. Weak answers describe persuading everyone in one meeting or getting a manager to overrule them. 11. ### 21.Tell me about a product decision you made that turned out to be wrong. What a strong answer shows Pick a real mistake with consequences, explain the reasoning at the time, and say how you noticed it was wrong. The strong part is what you changed afterwards in how you decide. The trap is a disguised strength, such as caring too much, or a story where the failure was someone else's. 12. ### 22.How do you decide a problem is worth solving before anything gets built? What a strong answer shows Look for evidence that the problem is frequent, painful and tied to a goal the business cares about. Combine interviews, support tickets and usage data, then test the riskiest assumption cheaply, for example with a prototype or a fake door. Weak answers treat a few enthusiastic interviews or a competitor's feature as proof. ## Senior Product management interview questions 1. ### 23.How would you decide whether to add an AI feature to a product? What a strong answer shows Start from a user problem where the task is costly or slow and an imperfect answer is still useful. Weigh accuracy needs, the cost per request, latency, data and privacy constraints, and what happens when the model is wrong. The trap is starting from the technology because a competitor shipped something with AI in the name. 2. ### 24.How would you measure whether an AI assistant feature is working? What a strong answer shows Combine offline evaluation, grading a fixed set of real cases against clear criteria, with online signals. Useful ones include task completion, edits to the output and repeat use. A strong answer tracks harmful or wrong answers as a guardrail and samples outputs for human review. Weak answers rely on thumbs-up ratings or on demos that looked impressive. 3. ### 25.How would you price a new product or a new paid tier? What a strong answer shows Anchor on the value customers get and what they would otherwise pay. Then choose a value metric that grows with that value, such as seats or usage. A strong answer segments customers, considers how the tier affects existing plans and tests willingness to pay. The trap is cost-plus pricing or copying a competitor's price page. 4. ### 26.A competitor just launched the feature you planned for next quarter. What do you do? What a strong answer shows Do not panic or rush a copy. Look at how their customers respond, whether your target users actually overlap, and whether the feature still supports your strategy. A strong answer may keep the plan, change the angle to differentiate, or drop it, and explains the reasoning to the team and leadership. 5. ### 27.Should our company expand into an adjacent market? How would you decide? What a strong answer shows Assess the size and growth of the opportunity, the advantage you bring such as existing customers, data or distribution, and the competitive response. Strong answers name the cost of focus taken from the core product and define a small first step with clear exit criteria. Weak answers argue from market size alone. 6. ### 28.Two senior leaders want opposite things from your team. How do you resolve it? What a strong answer shows Make the conflict explicit and frame it against the company goal, with the trade-offs laid out in writing. Try to find an option that meets both underlying needs, and if there is none, get the decision made at the right level. The trap is quietly splitting the team between both asks so neither succeeds. 7. ### 29.How would you test a change in a two-sided marketplace where users in different groups affect each other? What a strong answer shows A strong answer explains interference: treatment users can take supply from control users, so a simple user-level split overstates the effect. Options include splitting by geography or time, switchback tests and measuring both sides of the market. Weak answers run a normal A/B test and trust the result. 8. ### 30.How do you decide to retire a feature or product, and how do you carry it out? What a strong answer shows Weigh usage and the value it delivers against maintenance cost, complexity and what the team could build instead. A strong answer studies who depends on it, offers a migration path, gives notice and watches churn and support load during the wind-down. The trap is either never removing anything or switching it off without warning. ![Painting of an olive grove in soft sunlight with hills beyond](https://cdn.sanity.io/images/islu4peo/production/613eb3f93566423c9adf45246f2cf1a61437c04c-1680x1120.jpg?w=1080&fm=webp&q=68&fit=max) ## Prove it instead of claiming it. Answers show you can talk about product management. A dated test result and live sessions on a Skills Passport show you can do it. Lemma is in early access. ## Product management interviews: common questions ### How should I prepare for a product sense interview? Practise a repeatable structure: clarify the goal, choose a user segment and pick one painful problem. Then compare a few solutions and define how you would measure success. Rehearse out loud on products you use, with a timer. Interviewers care more about clear reasoning and trade-offs than about the idea itself. ### Do product managers need coding skills to pass interviews? Most PM roles do not ask you to write code. You should still explain how systems work at a high level, such as APIs, databases and the cost of a change. Technical or platform PM roles go deeper, so read the job description closely. ### Which examples should I bring to a product manager interview? Prepare a handful of stories you can reuse: a launch, a hard prioritisation call, a conflict, a failure and a decision backed by data. Each should cover the problem, your evidence, what you decided and what changed. Work from side projects or another role counts if you can show the outcome. On Lemma, a completed live session with a practitioner counts as evidence of the skill; the call itself is not recorded. ## More interview questions [Browse the skills directory](https://getlemma.io/skills) - [SQL interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/sql/interview-questions) - [Python interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/python/interview-questions) - [React interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/react/interview-questions) - [System design interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/system-design/interview-questions) - [JavaScript interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/javascript/interview-questions) - [AWS interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/aws/interview-questions) - [Node.js interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/nodejs/interview-questions) - [TypeScript interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/typescript/interview-questions) - [Docker interview questionsJunior to senior, with what a strong answer shows](https://getlemma.io/skills/docker/interview-questions) Practising answers is half of it; the other half is showing the skill. See [how Lemma tests product management](https://getlemma.io/skills/product-management), how [adaptive skills tests](https://getlemma.io/product/assessments) work, or [how interviewers assess technical skills](https://getlemma.io/blog/assess-technical-skills-in-interview).