How vetting works
Two recorded interviews. Then a person checks again.
This is the bar a professional clears before we put the vetted badge on their profile. You can watch the same technical interview we scored before you meet anyone.
Tell us who you needThe funnel, in real numbers
Of the 527 people who completed our recorded intro interview, 93 passed both recorded interviews: 18%. Figures verified on 12 October 2026.
Profiles reviewed
3,263
Sat the recorded intro interview
527
Passed both recorded interviews
93
Hold the vetted badge
27
Seven steps, each with a bar to clear
Today’s bar for the vetted badge. Automated scores inform it; a person decides.
- 01
Profile and project review
We read what they have built, with which stack and at what level of responsibility, before inviting them to interview.
To passRelevant stack and project history
- 02
Recorded intro interview
Spoken answers on camera about past work and how they work, including how they use AI tools day to day. Each answer is assessed from the recording.
To passCommunication 3/5 or higher, working English or Italian at B2 or above
- 03
Recorded technical interview
Questions written for their stack, answered on camera and scored answer by answer. We also check that the level they claim matches the level they show.
To passTechnical score 3/5 or higher, seniority confirmed
- 04
Timed skills test
A short, timed set of questions on their stack, taken with the technical interview.
To pass70% or higher
- 05
Recruiter review
A recruiter rates the candidate against the roles we fill.
To passRating 4/5 or higher
- 06
Final live call
Fifteen minutes, camera on, once every measurement has passed. A person confirms the candidate is the one in the recordings.
To passIdentity and consistency confirmed
- 07
A person awards the badge
Scores inform the decision but never award the badge on their own. A recruiter records the decision and the reason.
To passRecorded decision by a person
You see the evidence we used
Profiles we send come with the recorded technical interview from step 3. Jump to the questions that matter for your role and judge the answers yourself.
Once someone joins your team, you get daily end-of-day reports and a monthly review with your account manager.
What you get for every candidate
A recorded technical interview, so you see how they think before you book a call.
Question 1 of 5
00:40 / 22:14
Design a rate limiter for a public API
Their answer
“I’d start with a token bucket per API key, kept in Redis so every instance shares the same count.”

Senior backend engineer
8 years · Tirana · CET · Available from 1 December
Questions in this interview
- 00:40Design a rate limiter for a public API
- 05:15Find the cause of a slow production query
- 09:30Review a pull request with a hidden bug
+ 2 more questions
Start with the role