Updated September 2026
Interview a startup product manager in four stages: a founder screen on motivation and decision rights, a product sense conversation about your own product, a work sample presented to the founder and engineering lead, and a final round with the team and references. Across all four, look for evidence of customer discovery and outcomes, not polished frameworks.
Strong answer: recent, specific conversations with a clear decision that followed, and a habit of asking about past behaviour.
Red flags: research that only happens through other teams, or talks about "the voice of the customer" without examples.
Strong answer: names the trade-off and who lost out, uses data and customer evidence together, and admits a failed launch plainly.
Red flags: relies on a scoring framework with no judgement, or every launch was a success.
"I'd score all three with RICE and build the highest score."
"I'd ask what each one is for. If the large customer is at risk of leaving, that may win this month, but I'd tell the founder and engineering lead why, and what we're delaying."
Strong answer: short specs focused on the problem, respect for engineering estimates, and a clear example of technical depth.
Red flags: specs that dictate the solution in detail, or blames engineers for missed dates.
Strong answer: a realistic view of decision rights, disagreement handled with evidence, and a 30-day plan built around listening.
Red flags: expects full control of the roadmap from day one, or needs a team around them before they can deliver.
Share an anonymised slice of your real backlog (10 to 15 items), a few customer quotes, and one or two usage numbers. Ask them to pick what goes into the next cycle, explain what they would leave out, and say what they would need to learn first. Cap preparation at two hours, then give them 20 minutes to present and 40 minutes of challenge.
Look for a clear link between evidence and choices, a short list rather than everything, and questions about data they don't have. The challenge section matters most: watch whether they defend a good decision and change a weak one.
| Outcome | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Customer discovery | No recent conversations | Some, rarely acted on | Regular, clearly shapes decisions | Built a discovery habit a whole team adopted |
| Prioritisation | Everything is a priority | Framework without judgement | Clear choices, explains trade-offs | Chose what to leave out and why, backed by evidence |
| Shipping with engineering | Long specs, blames engineers | Works with engineers, limited trust | Short specs, respected by engineers | Engineers ask to work with them again |
| Outcomes | Only talks about features shipped | Mentions metrics loosely | Moved named metrics | Also knows which launches failed and why |
| Founder handover | Wants full control, or none | Unclear on boundaries | Clear on decision rights | Proposes how the handover should work |
A dedicated Funded.club recruiter screens product candidates for discovery and outcomes before they reach you. You see first screened candidates within 7 days, on a fixed fee agreed upfront (see pricing).
Use your own anonymised backlog, customer quotes and a few numbers, and ask them to plan the next cycle. Generic cases, such as designing an app for a well-known brand, tell you little about how they would work in your company.
Yes. An engineer's view on whether they would want to build from this person's specs is one of the best signals you will get.
Write the role and scorecard first, using our product manager job description template. Our guide to hiring your first product manager covers the full search.
Worth a brief chat about your next hire? Book a free call.