Vetting senior engineers: what a 3% bar means
Keyword-matching résumés is not vetting. Here’s the five-gate process behind a genuine top-3% engineering bench.
“Vetted” is the most overused word in staffing. Too often it means a recruiter skimmed a résumé for keywords. A real bar looks different: sequential gates, each of which can end the process, graded by engineers rather than filters. Here’s the shape of one that admits roughly 3% of applicants.
Gate 1, Application screen
Experience, code and role fit reviewed by engineers, not keyword filters. Around 41% of applicants clear this. The goal is to catch signal a parser misses: depth of ownership, quality of past work, and to reject the rest fast.
Gate 2, Technical assessment
A timed, real-world problem graded on correctness, structure and trade-offs. Not a trivia quiz, a task that resembles the work. This is where most fall away; roughly 22% remain.
Gate 3, Live pair session
A senior engineer pairs live to see how a candidate thinks, debugs and communicates under mild pressure. You learn more in 45 minutes of pairing than in any take-home. About 11% survive.
Gate 4, System & communication
Architecture depth plus written and spoken English at a professional bar. Senior engineers need to explain trade-offs and push back clearly, especially across time zones. Around 5% remain.
Gate 5, Client-fit interview
Final calibration against a specific domain, seniority and team culture. Roughly 3% of the original pool make it through.
Why slow and expensive is the point
A funnel like this is deliberately costly to run. That cost is a feature: it keeps the bar high, and it’s a big reason vetted engineers stay. It also lets us stand behind a named-developer guarantee, the engineer you interview is the one who joins, backed by a two-week risk-free trial.
One more thing that belongs in 2026: AI fluency is a graded part of the process, not an afterthought. See the full funnel on our how we vet page, or browse the bench by skill.
More from the dispatch.
How to Onboard Engineers in Two Weeks Without Cutting Corners
Shipping in the first two weeks is a process problem, not a talent problem. Here is how to onboard engineers in two weeks so they contribute real work fast.
How to Prepare for a Senior Engineering Interview
A practical guide to help experienced engineers walk into a senior interview ready to demonstrate judgement, not just recall. What to revise, what to skip, and how to talk about your work.
What to Look for in a Remote Engineering Role
Not all remote jobs are built the same. Here is what an experienced engineer should scrutinise before accepting a remote engineering role, from time zone reality to career progression.