The Best Way to Solve a PM Case Study Is to Not Solve It
The best way to solve a case study in an interview is to not solve it. At least not immediately. Especially if it's solution-oriented.
This happened in one of my interviews last year.
TL;DR: When given a case with a pre-baked solution (like "build Netflix Music"), don't jump into executing that solution. Question the underlying problem first. Narrow it down. Validate whether the proposed solution even makes sense. Then propose alternatives based on real analysis. This is what PMs actually do at work, and interviewers love seeing it.
The Netflix Music case
Interviewer: "Let's take up a case. Assume I'm the CEO of Netflix and you're the Product Head. I want you to work on a new product, Netflix Music, to compete with Spotify and Apple Music. What would you do?"
Now, most candidates would start running with this. They'd discuss features for Netflix Music. Market positioning against Spotify. Potential differentiators. Maybe a pricing strategy.
That's the trap.
Me: "Can you provide some context? What problem is this expected to solve?"
Interviewer: (thinking) "Let's say Netflix is experiencing losses. We want to address this with the new product."
Me: "Can you clarify what you mean by losses? What kind of data do we have?"
Interviewer: "Let's say we expected revenues to grow by 10-20% YoY but it has declined. Feel free to make assumptions and ignore my solution if required."
Me: "Understood. Let me take some time to think through."
What I presented
After a few minutes of thinking, I presented:
1. Problem narrowing
I focused on narrowing down the problem instead of just looking at a single number called "revenue."
- Did new subscriptions go down? Or did existing users stop renewing?
- If renewal is down, is it specific to some countries, age groups, or content languages?
- If it's country-specific, are there geopolitical issues, or is a new player eating into Netflix's share?
Each of these leads to a completely different solution. "Revenue declined" could mean 10 different things. A PM who builds "Netflix Music" without understanding which of those 10 things is happening is guessing, not solving.
2. Solutions based on root cause
Based on my assumptions about the most likely root cause, I proposed solutions and outlined what success would look like from both a product and business perspective.
I also explicitly stated: "I wouldn't venture into a new business area without clear evidence that our current business model couldn't be improved."
That's the key insight. Building Netflix Music is a massive bet. Before making that bet, you'd exhaust the options within your existing model. Maybe the problem is content quality in specific regions. Maybe it's pricing. Maybe it's churn during off-peak content seasons.
Why this approach wins
The interviewer didn't want me to design Netflix Music. They wanted to see if I'd challenge the premise.
What 4 out of 5 candidates do: Accept the solution as given and start executing it. Design the features. Discuss market positioning. Build a roadmap for Netflix Music.
What the best candidates do: Question why. Dig into the problem. Validate whether the proposed solution even addresses the right issue.
| Approach | Signal to interviewer |
|---|---|
| Accepts solution, starts executing | "This person follows orders without questioning" |
| Questions the problem, proposes alternatives | "This person thinks like a PM and challenges assumptions" |
This applies to all solution-oriented cases
This isn't just about Netflix Music. Any time a case presents you with a solution upfront, your first instinct should be to question the problem behind it.
Common examples:
"Build an ATM for the blind." Don't jump into designing a tactile ATM interface. Ask: what problem are blind users facing with banking? Is it ATM-specific or is there a broader access issue? What alternatives exist?
"Design an alarm clock for the deaf." Don't start listing vibration features. Ask: what's the actual problem? Waking up reliably? What solutions exist already? What's failing about them?
"Build a competitor to X." Don't start feature-listing. Ask: why compete with X? What customer need isn't being met? Is building a competitor the only option?
In each case, rather than jumping to the prepared answer (which is what 4 out of 5 interviewees do), ask the interviewer:
- What problem is being solved?
- What's the context?
- Why now?
- What evidence supports this direction?
Then formulate solutions based on the actual problems.
The muscle to develop
Solving real problems backed with data is a critical skill for a Product Manager at their job as well. Every day, stakeholders come with solutions:
- "We need to build feature X" (but why?)
- "Let's redesign the dashboard" (what's wrong with it?)
- "We should add AI to this" (what problem would it solve?)
The PM's job is to question the solution and find the problem. Then determine if that solution is even the right one.
Developing this as muscle memory, so you do it automatically in interviews and at work, is one of the most valuable things you can practice.
How to practice this
-
Take any case study you've practiced and add "why?" before solving. Before designing the feature, spend 5 minutes questioning the premise.
-
Practice with a partner. Have them give you solution-oriented cases. Practice asking 3-4 clarifying questions before proposing anything.
-
In real conversations, notice when people give you solutions instead of problems. Practice reframing: "What's the problem this solves?" becomes your default first question.
-
Time yourself. You should spend at least 30-40% of your case time on problem definition. If you're jumping to solutions in the first minute, you're not questioning enough.
The bottom line
Don't get carried away solving something without understanding the problem. The best PM answer to a solution-oriented case is: "Let me understand the problem first."
That single sentence, delivered with confidence, tells the interviewer everything they need to know about how you'll operate as a PM.
How ProductResume helps
This problem-first thinking is what hiring managers evaluate in case rounds. But you need to get to the case round first. Score your PM resume to make sure your resume earns the interview, then use Interview Prep to practice questioning premises and structuring case answers.