Product, marketing and design
A first interview with a product manager should answer three questions. Do they make decisions from evidence? Can they say no? Can they get engineers and designers on board without being their boss? You’ll hear all three when they describe a trade-off they actually made.
Product decisions have several layers. The AI asks follow-up questions, like the second and third “why” that a fixed script would skip.
What to look for
The questions
Ask them in order. Listen for real details: what happened, what the candidate did, and how it ended.
Strong answer
Names the request and who made it, the evidence they weighed, what they offered instead of a yes, and how they kept a good working relationship.
Weak answer
Has never said no, or describes building everything that was asked for as a win.
Strong answer
Describes talking to customers, reading support requests or looking at usage data, and writing down the problem clearly before picking any solution.
Weak answer
Starts from a solution someone in the business asked for and works backward to justify it.
Strong answer
Names the number, admits the miss plainly, and explains what they learned and whether they improved it, undid it 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 doing less, a smaller first version or changing the order of work, and tells the people affected about the trade-off early.
Weak answer
Pushes the team to hit the original date, or lets it slip quietly.
Strong answer
Starts with the problem and what success looks like, lists what’s left out and what’s still undecided, and brings engineers in before it’s finished.
Weak answer
Describes a long list of requirements, handed over only once it’s complete.
Strong answer
Treats it as a question about users, settles it with a test or by watching customers try it, and gives the designer credit where it’s due.
Weak answer
“I’m the product manager, 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 when their judgment overruled a scoring system, and describes a real sales request they said no to.
Weak answer
Names a planning method by its initials, 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
Short form questions the candidate answers before the interview. You read the answers next to the interview. They aren’t scored.
Listen for
Avoid
Use this in LessRounds
Paste the questions into a scripted interview, where the AI reads each question word for word. Add the skills from the scorecard, then share one link. Every product manager candidate gets the same questions. You get a score for each skill, with the candidate’s own words that explain it.
Keep it light. A spoken first interview works best with past decisions and one short scenario. Save a written case study for a later interview, 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 limit they worked around. If they can explain it plainly, that’s usually enough.
Start with 100 free credits, enough for about 20 interviews. No credit card or sales call needed.