Product, marketing and design
A first round for product managers should answer three things: do they decide from evidence, can they say no, and can they move engineers and designers without authority. You’ll hear all three in how they describe a trade-off they actually made.
Product decisions have layers, and AI-led follow-ups ask the second and third “why” a script would skip.
What to screen for
The questions
Ask them in order. Listen for specifics: what happened, what they did, how it ended.
Strong answer
Names the request and who made it, the evidence they weighed, what they said instead of yes, and how they kept the relationship intact.
Weak answer
Has never said no, or describes building everything that was asked for as a win.
Strong answer
Describes customer conversations, support tickets or usage data, and a clear problem statement written before any solution.
Weak answer
Starts from a solution a stakeholder requested and works backward to justify it.
Strong answer
Names the metric, admits the miss plainly, explains what they learned and whether they iterated, rolled back or moved on.
Weak answer
Calls every launch a success, or can’t say what a launch was meant to change.
Strong answer
Asks why first, then looks at cutting scope, a smaller first version or re-sequencing, and tells stakeholders about the trade-off early.
Weak answer
Pushes the team to hit the original date, or lets it slip quietly.
Strong answer
Leads with the problem and what success looks like, lists what’s out of scope and open questions, and brings engineers in before it’s finished.
Weak answer
Describes a long list of requirements handed over once complete.
Strong answer
Frames it as a question about users, settles it with a test or customer sessions, and gives the designer credit where it’s due.
Weak answer
“I’m the PM, so I made the call”, or claims they’ve never disagreed with a designer.
Strong answer
Ties choices to a small number of goals, explains where judgment overrode a scoring method, and describes a real sales request they said no to.
Weak answer
Recites a framework acronym with no example of using it.
Strong answer
Names a specific user and problem, proposes one small change, and says which behavior they’d measure afterward.
Weak answer
Adds several features with no user, reason or way to tell if they helped.
Before the interview
Quick facts to read alongside the interview. They aren’t scored.
Listen for
Avoid
Use this in LessRounds
Paste the questions into a scripted interview, add the scorecard skills, and share one link. Every product manager candidate gets the same questions, and you get a score for each skill with the quote behind it.
Keep it light. A spoken first round works best with past decisions and one short scenario. Save a written case for a later round, and keep it small enough to finish in a couple of hours.
Technical enough to have an honest conversation with engineers about trade-offs. Ask them to explain a technical constraint they worked around. If they can explain it plainly, that’s usually enough.
Start with 10 free interviews a month. No card, no sales call.