01

Find the claim doing the most work

Which claim makes this candidate relevant? A shipped feature, a commissioning project, a team built from scratch? Start there. A generic career walk-through can wait until you understand that claim.

02

Ask for a decision, not a definition

“Explain RAG” can produce a rehearsed answer. “Which retrieval decision did you change after users started using the product?” asks for a lived example. Listen for the constraint, the choice and the result.

03

Separate the team’s outcome from personal contribution

Use “What was already in place?” and “Which part did you own?” without assuming the CV exaggerates. Collaborative work can be excellent evidence once the person’s contribution is clear.

04

Close the practical gaps

Confirm availability, compensation expectations and location requirements directly. The absence of these details in a CV is an open question. Record the candidate’s answer separately from the original document.

TAKE THIS BACK TO YOUR DESK

A question you can reuse

“Tell me about one decision on that project that you personally owned. What were the alternatives, and what happened after you chose?”