Vetting is the product.
Anyone can forward you a CV. What you are actually buying is the filter in front of it — four stages, eight hours of assessment, and a written record you get to read before you say yes.
What happens at each vetting stage?
Four stages. About three in a hundred applicants reach the talent pool.
| Stage | What happens | Pass rate |
|---|---|---|
Stage 1 Application & screening Baseline check before anyone spends real time. Most applications end here. |
| Pass rate 40% 40 of 100 still in |
Stage 2 Skills assessment Role-specific work under observation — code, outreach sequences, campaign teardowns. |
| Pass rate 25% 10 of 100 still in |
Stage 3 Communication & culture Whether they can work inside someone else's team, in English, across a time zone. |
| Pass rate 60% 6 of 100 still in |
Stage 4 Training & onboarding Nobody meets a client without completing this. A few still don't make it. |
| Pass rate 50% 3 of 100 still in |
What does Sprint Labs score during vetting?
Technical proficiency
Depth in modern frameworks and languages, with production experience we can verify — not a certificate wall.
Problem-solving
Breaking down an unfamiliar problem and defending the trade-offs, live, with someone senior watching.
English communication
Professional written and spoken English. Assessed on a call, not self-reported on a form.
Time zone alignment
Real overlap with your working day, confirmed as a condition of the role before we shortlist.
Security awareness
Secure practice, data handling and OWASP fundamentals. Mandatory pass for everyone, every discipline.
Professional standards
Reliability, proactive updates, ownership when something breaks. Checked with references, not assumed.
Passing vetting is where the work starts.
Nobody reaches a client without completing our onboarding programme. It is the difference between someone who can code and someone who can join your standup on day two and be useful.
Training continues after placement — a budget, a mentor and quarterly reviews, because the alternative is watching good people go stale on your account.
Cyber security
Secure coding, data protection, OWASP guidance and vulnerability awareness.
Client communication
Update cadence, meeting etiquette, escalation and stakeholder handling.
Tools & workflow
Modern toolchains, CI/CD, ticketing and delivery standards before day one.
Ongoing development
Mentorship, an annual learning budget and quarterly reviews after placement.
| Criterion | Score bar | Score |
|---|---|---|
| Technical proficiency | 94 | |
| Problem-solving | 88 | |
| English communication | 91 | |
| Security awareness | PASS | |
| Professional standards | 96 | |
| Time zone overlap | AEST |
What's in a Sprint Labs candidate file?
Every shortlisted candidate arrives with their scores, their recorded interviews and the notes of the person who assessed them. No polished summary standing between you and the evidence.
Hard to get in.
Worth it once you are.
The bar is high on purpose — it is what lets us pay above market and put you in front of companies who treat you as their own engineer, not a resource line.
How does Sprint Labs vetting work?
What are the stages of the Sprint Labs vetting process?
Four stages: application and screening (resume, initial skills screen, background and reference verification); a role-specific practical skills assessment under observation; a communication and culture interview in English, including recorded video; and security, client-communication and workflow training before any client introduction. Around eight hours of assessment in total, with a written record you can read before you interview.
How many candidates make it into the Sprint Labs talent pool?
Roughly 3% of applicants. We reject far more than we accept because every hire becomes a Sprint Labs employee, not a marketplace listing.
Do candidates record a voice introduction?
Yes. Every candidate submits a short Vocaroo voice recording so you can hear their spoken English before shortlisting.
Read a real shortlist.
Post one request and see what a vetted candidate file actually looks like. No call required to start.
Last reviewed by the Sprint Labs team