01
Big outcomes with no clear contribution
“Grew revenue” or “launched a platform” needs context. Ask what the candidate owned, how success was measured and what changed because of their decision. Separate team results from individual responsibility without expecting confidential business data.
02
Activity without a customer problem
Roadmaps, ceremonies and feature counts describe activity. Ask which user problem mattered, what evidence supported it and how the candidate checked the result. A strong answer can also describe a feature they stopped or a hypothesis that failed.
03
Claims that do not connect to examples
If every skill is labelled “expert,” choose one and ask for a concrete decision. Discuss a prioritization conflict, a research insight and a disagreement with engineering. Use the same questions and scoring criteria across candidates.
04
Do not mistake a different career path for a risk
Employment gaps, career changes, unfamiliar employers and résumé design do not establish ability or integrity. Verify relevant claims fairly, offer a chance to clarify and keep sensitive personal information out of the assessment.