Product sense interview questions, and how to answer them
Product sense questions are the part of a PM interview most people dread. “How would you improve Spotify?” sounds open-ended, so candidates either freeze or start listing features. Neither works. The good news: interviewers aren’t looking for a brilliant idea. They’re looking for a way of thinking, and once you know what they’re scoring, these questions get much easier.
What a product sense question is really testing
A product sense question checks whether you can take a vague problem and turn it into a clear, sensible decision. In practice, interviewers listen for four things:
- Do you start with the goal? Strong candidates ask what success looks like before suggesting anything.
- Do you find the real problem? They pick a specific user and a specific pain, rather than “improving the experience”.
- Do you make choices? They prioritise, say what they’d not do, and explain why.
- Can you turn it into action? They end with something you could test next week, and how you’d know it worked.
That’s the LIFT framework: Lead with outcomes, Identify real problems, Frame strategically, Take action. It’s the structure I teach the PMs I mentor, and it works for almost every product sense question.
How to answer with LIFT: a worked example
Question: “How would you improve the onboarding of a budgeting app?”
“Before I jump in, what are we trying to improve? I’d assume the goal is more new users still budgeting after 30 days, since that drives retention and revenue. I’d measure it as the share of new users who set up a budget and come back in week four.”
“Who’s dropping off, and why? I’d focus on people who download the app but never connect a bank account. The likely pain is trust and effort: connecting a bank feels risky, and setting up categories feels like homework.”
“There are three ways to attack this: reduce the effort, build trust, or show value before asking for anything. I’d prioritise showing value first, because it eases both the effort and the trust problem, and it fits a retention goal better than a one-off nudge.”
“I’d test a version where users get a sample budget from three quick questions before connecting a bank. Success is a higher share of users reaching week four. If it doesn’t move, I’d check whether people still stall at the bank connection step.”
Notice the answer never needs a clever feature idea. It needs a clear goal, a specific user, a reasoned choice and a test.
12 product sense questions to practise
Improve an existing product
- How would you improve Google Maps?
- Pick your favourite app. What would you change, and why?
- How would you increase engagement on LinkedIn?
- How would you improve the checkout of an online store?
Design something new
- Design a product to help people find a flatmate.
- Design a fridge for families with young kids.
- Build a feature to help remote teams feel more connected.
- Design an app for people learning to cook.
Strategy and trade-offs
- Should a streaming service add a free, ad-supported tier? How would you decide?
- Your biggest customer wants a feature no one else has asked for. What do you do?
- Engagement is up but revenue is flat. What’s going on?
- You have room to build one of three ideas. How do you choose?
Practise them out loud with LIFT as your structure, and time yourself. Aim for a clear answer in 10 to 15 minutes, about the length of a typical interview question.
Common mistakes
- Jumping to features. Listing ideas before agreeing on a goal is the most common reason good candidates score poorly.
- Designing for “everyone”. Pick one user group and go deep. You can mention others later.
- Not making a call. Interviewers want to hear “I’d prioritise X over Y because…”. Hedging reads as indecision.
- No way to measure it. Finish with what you’d test and the number you’d watch.
How ready are you to be a PM?
Take the free PM Readiness Score: ten quick questions, a score out of 100 and the area to work on first. Or get the LIFT guide, the framework behind everything on this page.
Frequently asked questions
What’s the difference between product sense and product design questions?
They overlap heavily. Product design questions ask you to design something; product sense is the wider skill of judging what’s worth building. The same structure works for both.
How long should a product sense answer be?
Usually 10 to 15 minutes in an interview. Spend the first couple of minutes on the goal and the user, and leave time for a test and a metric at the end.
Do I need PM experience to answer these well?
No. Interviewers are testing how you think. Examples from design, analysis, product ownership or engineering count, as long as you show the reasoning.
Is there one right answer?
No. Two candidates can propose different solutions and both score highly. What matters is a clear goal, a specific problem, a reasoned choice and a way to test it.