Every candidate we introduce to you has been through two stages: a screening that every applicant takes, and a review we do ourselves. 3.9% of applicants make it through screening and our review.
Here is what each stage involves.
Stage 1: Screening
Every applicant answers questions about their skills, their experience and how they like to work, and is ranked against your role. Only the applicants who come through screening move on to our review.
Stage 2: Our review
We meet every candidate before you do. In that review we:
- Check their English. You will work with them in standups, code reviews and written threads, so we hear them speak before you do.
- Confirm their experience is what they say it is.
- Call their references. We speak to people who have worked with them.
- Review their code or portfolio. For a developer that means their code (repositories or work samples); for a designer, their portfolio.
A candidate only reaches you once all four hold up.
Then you interview
You run your normal interview, and the choice is always yours. Because the screening and our review have already covered English, references and the candidate's actual work, your interview can spend its time on fit with your team. Our post on how to interview a senior developer covers what is worth asking.
What the 3.9% means
An acceptance rate on its own tells you little. What matters is what it selects for, which is why the steps are written down here. Whichever provider you are weighing, ask the same two questions: what do you check, and how many applicants don't get through? A vague answer to either usually means there is no real bar. Our buyer's checklist for nearshore partners has more questions like these.
For how vetting fits into the rest of an engagement, from opening a position to the first day of work, see How it works.