Product Strategy Interview Questions: A Framework, a Worked Example and 15 to Practise
Strategy answers are judged on reasoning, not conclusions. Five questions, one grid and a full worked example to structure any of them.
Product strategy questions test whether you can think above the level of a single feature. Answer them with five questions: where are we, where can we play, how do we win, what do we give up, and how will we know. Weigh market attractiveness against your ability to win, name the advantage you rely on, and prefer a staged pilot with stop rules over an all-in bet.
- What interviewers are really checking
- Five questions that structure any strategy answer
- Should we enter this market? A simple grid
- What creates an edge that lasts
- Worked example: a food delivery app considers groceries
- Fifteen strategy questions to practise
- Pricing questions: a simple way to answer
- Build, buy or partner
- Second worked example: a big player copies your core feature
- How answers change with seniority
- Common mistakes
- How to practise
Strategy questions feel abstract because they move you from "what should we build" to "where should this company compete". They show up more in senior PM interviews, but even for a first PM role you will hear a version of them: "Should we enter this market?", "How would you respond to this competitor?", "How would you price this?". The good news is that a small set of ideas covers almost every one.
What interviewers are really checking
They want to see that you can lift your view above a single feature. Do you understand what makes a business win? Can you weigh a big decision with incomplete information? Can you say no to attractive options? A strategy answer is judged less on the conclusion and more on whether your reasoning would still hold up if the interviewer changed one fact.
Five questions that structure any strategy answer
Where are we? Honest starting point: users, strengths, weaknesses. Where can we play? Which markets or segments are worth entering. How do we win? The specific advantage that makes users choose you. What do we give up? Strategy is choice; if you are not saying no to something, you do not have one. How will we know? The signals that tell you it is working or that you should change course.
Should we enter this market? A simple grid
Market attractiveness means size, growth and how well served customers already are. Ability to win means whether you have an edge: distribution, data, brand, cost or a product advantage. Candidates often argue only the first half. Interviewers are usually waiting to hear the second.
What creates an edge that lasts
Worked example: a food delivery app considers groceries
Prompt: "A mid-size food delivery app is thinking of launching grocery delivery. Should it?" (Illustrative, no claims about any real company.)
Where are we? A loyal restaurant-ordering base, a rider network, and strong evening demand. Idle rider capacity in the mornings.
Where can we play? Grocery is a large and frequent category, but well served by specialists who compete on speed and freshness. The attractive niche is small top-up orders (milk, eggs, vegetables) where our existing riders and app habit already help.
How do we win? Not by matching specialists on assortment. Our edge is existing customers, riders who are idle in the morning, and one app for both. That suggests limited assortment, morning delivery windows, and cross-selling to current users.
What do we give up? Attention and cash from the core business, and a full-range grocery ambition. I would deliberately not compete on the weekly big basket.
How will we know? A pilot in two neighbourhoods for 8 weeks. Metrics: share of grocery orders from existing customers, repeat rate within 14 days, and delivery cost per order. Kill criteria stated upfront: if repeat rate stays low or unit cost stays above the value of the order, stop.
The recommendation is a conditional yes: a narrow, cheap pilot with pre-agreed stop rules, not a full launch. Interviewers often prefer that to a confident all-in answer, because it shows you can act under uncertainty.
Fifteen strategy questions to practise
- Should a ride-hailing company launch a food delivery service?
- How would you respond if a large tech company copied your core feature?
- How would you price a new subscription for a learning app?
- Should we build our own payments system or use a partner?
- How would you decide whether to expand to a new country?
- A startup competitor is growing faster than us. What do you do?
- How would you decide between growing users and growing revenue this year?
- Should a marketplace focus on supply or demand first?
- How would you monetise a free product with a large user base?
- When would you say no to a big customer's feature request?
- How would you enter a market that already has a strong leader?
- What would make you shut down a product line?
- Should a B2B product add a self-serve plan?
- How would you use AI to defend your position, and what are the risks?
- What would you do first as the PM of a product that is declining?
Pricing questions: a simple way to answer
Pricing sounds like maths and is mostly a value question. Start from what the user gets and what alternatives cost them, then choose a model, then test. The three common models fit different situations:
| Model | Works best when | Watch out for |
|---|---|---|
| Subscription | Value is delivered continuously | Churn if value is not felt monthly |
| Usage-based | Usage varies a lot between customers | Unpredictable bills scare buyers |
| Freemium | Free users bring more users or data | Too many stay free forever |
Then say how you would validate it: test two or three price points with small groups, watch conversion and refund rate, and check that the paying group looks like the users you want. Never claim one perfect number from thin air.
Build, buy or partner
Second worked example: a big player copies your core feature
Prompt: "A much larger company just launched a feature almost identical to ours. What do you do?"
First: do not react in a week. Find out what your users actually value about you. If the answer is the feature alone, you have a problem. If the answer is speed, focus, a community, or a specific niche, then the copy matters less than it feels.
Second: look at what the large company cannot easily match: they are slow to change, serve a broad audience, and rarely care deeply about a niche. Double down there. Ship what your most loyal users have been asking for, and tell them plainly you are staying focused on them.
Third: watch, do not guess. Track churn among your best users and new signups from the competitor overlap for the next month. Set a trigger in advance: if loyal-user churn rises past a level you name, revisit the plan. That is a real strategy answer: understand your edge, act on it, and define what would prove you wrong.
How answers change with seniority
For a junior role, interviewers care that your reasoning is structured and that you can weigh two or three factors sensibly. For a senior role they expect you to bring in more variables: organisational capacity, timing, second-order effects on the existing business, and a clear view on what you would stop doing to fund the new bet. If the role is senior, always mention what would be deprioritised; it is the clearest signal you think like a strategist.
Common mistakes
Answering with a framework recital and no opinion. Assuming the market is attractive because it is big. Ignoring the current business and how it helps or hurts. Failing to say what you would not do. And giving an all-or-nothing answer when a staged test is the smarter move. Also avoid inventing precise market numbers: use round, stated assumptions and show the logic.
How to practise
Pick one company you know well every day and ask the five questions about a real decision it could face. Write four lines for each. After a week you will have a stock of reasoning patterns and examples you can adapt to any prompt. Then try them out loud with someone who will change a fact halfway and see whether your answer flexes sensibly. See also the 50 question bank and the guide to case studies.
Frequently asked questions
What are product strategy interview questions?
Questions that test whether you can think at the level of a whole product or company: entering markets, responding to competitors, pricing, build-versus-buy and choosing what not to do.
How do I answer a product strategy question?
Use five questions in order: where are we, where can we play, how do we win, what do we give up, and how will we know. Then give a clear recommendation with a staged, testable plan.
Do junior PM interviews include strategy questions?
They can, usually in lighter form. Senior roles weight them heavily, but even a first PM interview may ask whether to enter a market or how to respond to a competitor.
What is a moat in product strategy?
A durable advantage that keeps users choosing you as competitors appear, such as network effects, data, switching costs, brand, scale or distribution.
Want this sharpened for your specific situation?
I take on a small number of career calls and resume reviews each month.
See how we could work together