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 Evaluate an AI Consulting Partner: A CTO's Checklist
Choosing an AI consulting partner is a hiring decision, not a procurement exercise. Here is how to separate genuine engineering capability from slideware.
How to Structure an Engineering Staffing Contract That Stays Flexible
A rigid contract locks you into last quarter's plan. Here is how to structure an engineering staffing contract that flexes with roadmaps, headcount, and budget without leaving you exposed.
Adding AI Features Without Derailing Your Existing Roadmap
Adding AI features to a live product is less about the model and more about protecting the roadmap you already committed to. Here is how to do both.