Three vetting steps
Every candidate we present has passed three steps. The technical skills assessment tests the languages and frameworks a candidate claims, at the seniority they claim. For an AWS engineer it covers AWS architecture and services (compute, storage, networking, IAM), IaC with Terraform, and CI/CD. It ends with a practical task on a real AWS setup, judged on what the design leaves exposed and what it costs to run. The soft-skills evaluation covers English, taking feedback and working in a team, and the third step is an analysis of their job history.
Some roles also get a live coding interview, where the candidate writes code and talks through their choices. A background check runs only when a client asks for one.
Why the task is judged on cost
Two designs can pass the same functional test and cost very different amounts to run. Picture a nightly job that takes ten minutes. One candidate gives it a server that stays on all day. Another starts it on a schedule and lets it stop. Both work, and one of them bills you for nearly 24 idle hours a day.
Your own interview
With staff augmentation, you interview each candidate before anyone starts, and you can turn one down on the CV or on the interview. Our technical interview and live coding, where the role has it, can be part of your own selection, with full visibility.
To test a candidate yourself, ask how they would keep an S3 bucket private, what they check in a Terraform plan before it is applied, and where they look first when the monthly bill jumps. The last answer tells you the most.