Interviewing product managers is uniquely difficult. You’re not just interviewing for skills, or experience, or even raw intelligence—though all of those matter. You’re also interviewing for judgement. And judgement is notoriously hard to assess in the artificial confines of a one-hour conversation.
To this day, the core of my product management interview comes from something I learned in 2015 from Jason Lynn—co-founder of mParticle and one of the best product thinkers in ad tech. When Jason first told me how he evaluates PMs, I recognized his genius immediately. I scribbled down every word, and for the last ten years, I’ve used a version of his method to hire and develop truly outstanding product teams.
Most PM interviews tend to cover the predictable categories: domain expertise, root-cause analysis, use-case construction, segmentation, strategy, frameworks. Good candidates generally come prepared with polished answers to those questions and examples from their experience.
But Jason’s interview goes farther and asks a core question that forces a candidate out of scripted answers and into the uncomfortable terrain where real product judgement lives.
It goes like this:
You’re two weeks away from launching a major product release that your engineering team has been working on for six months. A salesperson corners you in the hallway and says they’re working on a deal worth $10 million—if we deliver Feature X in the next two weeks. Feature X directly conflicts with the release you’ve been preparing.
What do you do?
Most people, even experienced PMs, approach this like a math problem:
- How many points of work is Feature X?
- How many points are left in the major release?
- What happens if we push the date back?
- Should we prioritize the release or the $10 million?
They frame it as a zero-sum tradeoff, as if the only two choices are A or B.
But product judgment rarely operates in binary.
PMs who’ve actually lived through this scenario many times will pause, smile, and immediately start asking different questions:
- How well do I know this salesperson?
- Who’s the client?
- What exactly is the remaining scope of the release?
- What’s the precise scope of the new feature?
- Can I speak with the client directly?
In other words: dealing in ambiguity is part of the job responsibility; PMs are constantly trying to improve their information orientation while at the same time understanding the optimal stop point to make a decision. “Judgment” being the shortcut term for this.
In real life, the job isn’t to choose between two bad options. The job is to unlock a better option that no one realized existed.
The best PMs instinctively create new paths—by connecting the client, the salesperson, and engineering; by distinguishing between what’s truly required and what’s merely assumed; by reframing constraints; by discovering that Feature X, properly scoped, may not conflict at all; or by finding a path to deliver enough value to close the deal without blowing up six months of work.
This is the difference between PMs that are more administrative in their function, and PMs that truly have world class judgement.
Some PMs are excellent at keeping lists and organizing feature requests. They are reliable, structured, and efficient. Give them 5 units of effort and they’ll return 5 units of value. Nothing wrong with that. Many organizations run on this type of PM.
But the best PMs?
They see the world through the eyes of customers, engineers, salespeople, and executives simultaneously. They understand what actually creates value. They know when to bend a roadmap and when to protect it. They cultivate direct relationships with every stakeholder that matters. They produce 5 units of value with 3 units of effort because they’re optimizing from first principles, not just from a spreadsheet.
That’s the lesson of Jason Lynn and it’s still the best way I know for evaluating product judgement—because it reveals how a PM thinks when the rules are unclear, the stakes are high, and the right answer isn’t in any textbook.