What does a product manager do?

A product manager decides what a product should do next and keeps the team building toward it. The work joins market and customer research, a clear goal, an ordered list of work, and steady contact with design, engineering, sales and support. In software teams the role often overlaps with what Scrum calls the Product Owner.

Government job profiles have no separate entry for this role. O*NET OnLine lists "Product Manager" as a reported job title under Marketing Managers (11-2021.00), whose tasks include using "sales forecasting or strategic planning to ensure the sale and profitability of products," developing pricing strategies, and starting or analyzing market research studies.

The Bureau of Labor Statistics page for advertising, promotions and marketing managers says marketing managers "estimate demand and identify potential markets for products and services." It gives a median annual wage for marketing managers of $166,790 in May 2025. That figure covers the whole marketing manager group, so treat it as a rough guide for product roles.

The 2020 Scrum Guide describes the Product Owner's work on the backlog in four parts: developing and communicating the Product Goal, creating and communicating backlog items, ordering them, and making sure the backlog is "transparent, visible and understood." Many product manager interviews probe each of those four parts.

How were these product manager questions chosen?

They come from the duties in the O*NET profile and the Scrum Guide, matched to the question each duty tends to produce. They are drawn from the job's published duties, not from a survey of real interviews. They make no claim to be the most asked, or to match what any named company asks.

Duty (O*NET and Scrum Guide)Question it tends to produceWhat the interviewer is checking
Start or analyze market research"How would you find out whether customers want this?"Whether you test a guess before you build
Develop and communicate the Product Goal"What would your goal be for this product next quarter?"A goal that is specific and measurable
Order backlog items"You have five requests and room for two. Which ones?"A clear rule for choosing, and what you say no to
Create and communicate backlog items"Write a user story for this feature"A user, a need and a reason, plus how you'd know it's done
Develop pricing strategies"How would you price this new tier?"Customer value, cost and the competition, in that order
Work with design, engineering and sales"Tell me about a launch that went wrong"Ownership, and how you kept people informed

Which behavioral questions should you expect?

Behavioral questions ask for real stories from past work, told in STAR order: situation, task, action, result. Interviewers listen for a decision you made, the evidence behind it, and what happened to customers. A product story without a user in it, or without a result you can explain, tends to score low.

The STAR method guide covers the structure. The page on influence without authority helps here too, because product managers usually lead people who do not report to them.

1. Tell me about a product decision you made with incomplete data.

What they listen for: what you knew, what you guessed, how you limited the risk, and how you checked afterwards. Saying you waited for perfect data rarely helps.

Made-up example answer. Situation: our support team kept hearing that customers wanted to export reports, but we had no usage data on it. Task: I had to decide whether export belonged in the next release. Action: I added a simple "Export" button that showed a short survey instead of a file, and ran it for two weeks with a note telling customers the feature was coming. Result: enough people clicked and answered that we built a basic CSV export first, and we dropped the PDF version the survey showed few people needed.

2. Tell me about a feature you shipped that didn't work.

What they listen for: how you found out, what you measured, and whether you rolled it back, changed it or kept it. The guide to tell me about a time you failed has a structure for this.

3. Tell me about a time you said no to a senior stakeholder.

What they listen for: respect, a reason tied to the goal, and an offer of what you could do instead. You should also explain how the relationship held up.

4. Describe how you work with engineers on a hard deadline.

What they listen for: honest scoping, early warnings about risk, and cutting scope before quality. The Agile Manifesto values "responding to change over following a plan," and interviewers often want to hear how you did that in practice.

What role-specific product manager questions come up?

Role-specific questions ask you to do product work live: improve a product, set a metric, order a backlog or write a requirement. Interviewers check that you start with the user and the goal, say your assumptions out loud, and end with a clear choice. Listing ten ideas without picking one is the most common way these answers fall short.

5. How would you improve a product you use every day?

What they listen for: a specific user, a problem that user has, two or three options, and one choice with a reason. Finish with how you would measure success.

Made-up example answer: "I'd pick a calendar app and focus on people who book meetings across time zones. Their problem is mistakes when they read times in other zones. I'd consider showing both time zones on every invite, warning when a meeting falls outside working hours, or suggesting times that suit both sides. I'd start with showing both zones, since it's simplest to build, and measure how often people reschedule meetings in the first week."

6. Which metric would you use to judge this feature?

What they listen for: one main metric tied to the user's goal, plus one or two that guard against harm. A metric that rises while users get worse off is a red flag to name.

7. Write a user story for a password reset feature.

What they listen for: the user, what they want, why, and what "done" means. The Agile Alliance user stories glossary notes that "a user story is not a document; the term encompasses all of the knowledge required," so mention the conversation and the acceptance checks too.

8. How would you order these five requests?

What they listen for: one rule for ordering, such as value to the goal against effort, applied the same way to each item. Say which request you would drop and how you would tell its owner.

9. How would you decide whether to build, buy or partner?

What they listen for: cost, time, how central the feature is to the product, and what you lose control of. Interviewers want a choice at the end.

Which situational questions test judgment?

Situational questions describe a problem you have not faced yet and ask what you would do first. Interviewers look for an order of steps: understand the problem, protect customers, tell the right people, then decide. Asking one or two good questions before you answer often scores better than a fast, confident plan.

The guide to situational interview questions explains the format.

10. Usage of your main feature drops 20 percent overnight. What do you do?

What they listen for: checking whether the data is broken before assuming users left, then looking for a release, an outage or a change outside the product. Then telling the team what you found.

Made-up example answer: "First I'd check whether the tracking itself broke, because a release can stop events from firing. If the data looks right, I'd check for an outage, a recent release or a change in one platform or region. I'd share what I knew with engineering and support within the hour, even if it was only a guess. Once we found the cause, I'd post a short note on what happened and how we'd catch it sooner."

11. Sales promised a customer a feature that isn't on the roadmap.

What they listen for: talking to sales and the customer, finding the real need behind the request, and making a clear decision. You should not quietly add it, and you should not ignore it.

12. Engineering says your top priority will take three times longer than planned.

What they listen for: asking why, looking for a smaller first version, and updating everyone who depends on the date.

What follow-up questions tend to come next?

Follow-ups test whether your answer survives a change. Expect the interviewer to remove your best option, cut your budget, or ask how you would explain the choice to an executive. Prepare by asking yourself what you would do if your first choice were impossible, and keep a second option ready.

  • "What would you do if engineering could only give you half the time?"
  • "How would you know in two weeks whether this was working?"
  • "Who would disagree with this choice, and what would you tell them?"
  • "What did you personally decide, and what did the team decide?"

How should you prepare for a product manager interview?

Write four or five STAR stories about real product decisions, including one that went wrong. Practise one product improvement question a day out loud, ending each with a single choice and a metric. Read the posting again and note which duties it stresses, such as research, pricing or delivery, then match a story to each.

The free interview question generator lets you paste the job and pick the round, and it returns likely questions, why they come up, and what the interviewer listens for. Product managers often sit in loops with engineers and analysts, so the pages for software engineer, data analyst and project manager interviews show what your partners are asked.

Prept's Mock room lets you practise these answers out loud on a clock, scores each answer out of 10 and checks it against your resume. It is included in the free plan.