Reference calls are the most skipped step in engineering hiring, and the most wasted when they do happen. "Would you hire them again?" gets a yes almost every time. It tells you nothing.
In our vetting process the reference call is the last of four stages, after a technical screen, a system design review and a conversation in English. That order matters: by the time we call a past lead, we already know which specific work the engineer told us about. The call exists to confirm that work.
Prepare from the earlier stages
Before the call, write down three claims the engineer made, as concretely as they made them. For example:
- "I designed the retry and idempotency layer for our payments API."
- "I ran the rollback when the new model version degraded."
- "I led the migration off the old queue."
These become your questions. You're not asking the reference to evaluate the engineer. You're asking them to confirm facts.
Questions that get real answers
- "They mentioned they built X. What was the team's situation when that started?"
- "Who else worked on it, and which part was theirs?"
- "What happened when it went wrong the first time?"
- "If they'd stayed another six months, what would you have given them next?"
The second question does the most work. Ownership is where CVs and reality drift apart most often.
Signals worth writing down
- The reference describes the same work, unprompted, in roughly the same terms. Good.
- The reference remembers the engineer but not the work. Neutral; ask someone closer.
- The reference attributes the key part to someone else. That's the finding.
Keep the evidence, not the vibe
We write what the reference confirmed, and who said it, into the summary that goes with each shortlisted engineer. Seniority is set by what was shown and confirmed, not by the title on the CV.
Two calls per engineer, with people who managed or worked directly with them on the work in question, is usually enough.
The full four-stage process, with what each stage checks and who runs it, is at bromena.com/how-we-vet.
— Bromena team
Top comments (0)