Vetting integrity

Gartner predicts that by 2028, one in four candidate profiles worldwide will be fake (Gartner, July 2025). It is a forecast, not today’s rate. But generative AI already makes a borrowed identity, a borrowed portfolio or a borrowed voice in an interview cheap, and remote hiring removes the last natural check: being in the room.

Ruzora places engineers you have never met in person into teams you run. So identity and ownership of the work are part of vetting, not an afterthought, and this page states what that means for you. It states outcomes: what is checked, what happens when a check fails, and what you get before day one. It does not state mechanics, for the reason in section 5.

Before an engineer can appear on any shortlist, they pass two separate evaluations, scored separately, and then a live technical interview with a technical expert at Ruzora.

• A graded coding challenge in their own stack, with no AI assistants allowed. It runs in a sandbox against hidden tests, so the score reflects working code rather than a plausible-looking file.
• An AI technical interview, on camera. Every answer is recorded on webcam. No camera, no interview. The interview is scored for engineering judgment, with an English level attached.
• A live technical interview with a technical expert at Ruzora, on a video call, before they can meet any client: system design or a technical deep-dive in their stack, trade-offs, and how they communicate. The same person sees the recording, the code and the live call, which is also how we know the person on the call is the person who did the work.

A passing score is required on both. Each score is compared with the hundreds of engineers who took the same evaluation, so “senior” on a Ruzora scorecard is a position among peers, not an adjective. Where the bars sit is not published (section 5). The share of applicants who clear both is computed from our own data and shown on How we vet whenever the sample is large enough to publish.

Scores alone do not put an engineer on the bench. Every completed evaluation goes through an integrity review before the engineer can reach a shortlist. The review looks at the result, the recording and the code together, and at whether the work and the person in front of the camera are the same person who will show up on your team.

The review is done by a technical expert at Ruzora, who also interviews the engineer live before any client meeting. AI scores the work; a person decides whether the result stands. The same person-in-the-loop rule applies to every automated signal we use: a signal is a reason to look, never a verdict.

• Nothing is auto-rejected. A flagged result is held for review. It does not reach a client shortlist until the review is done, and it does not disqualify the engineer by itself.
• The engineer may be asked to redo part of the evaluation, for example to retake a step on camera. Honest engineers pass this routinely; it costs them a little time, not the opportunity.
• Confirmed fraud is removed for good. An engineer confirmed to have cheated on an evaluation, or to have misrepresented who they are, is removed from the bench permanently. They are not re-invited, re-assessed or re-listed under a different role.
• If it is found after a placement, the 60-day replacement guarantee in our standard terms applies on documented technical grounds, and the engineer is removed from the bench in the same way. See Trust and standard terms.

We do not publish how the integrity checks work: which signals are collected during an evaluation, how they are weighed, or where the scoring bars sit. People who intend to cheat read this page too, and every mechanism we describe is a mechanism they can route around. A buyer who needs more than this page can ask us under NDA.

We also do not publish marketing percentages about our bench. The only pass rate on this site is computed from our own assessment data and recomputed as engineers are assessed; when the sample is too small, the number is withheld rather than estimated.

Integrity runs both ways, because engineers trust us with their profiles. Sol, our hiring agent, and the client portal accept work email addresses only, verified with a one-time code or a Google Workspace or LinkedIn sign-in. Personal email domains are refused on every path.

Before an agreement is signed, buyers see blind profiles: first name and surname initial, verified skills, scores, seniority and availability. Never an employer, never a full name. Full profiles come after the service agreement (section 7), and only to teammates on the company’s own email domain; partners, agencies and guest links stay blind.

After you sign the service agreement (MSA) and have a short kickoff call with Roberto, you get the engineers' full profiles, and Ruzora runs the interviews with you. You mark each engineer hire or pass, with a reason. Nobody joins your team without your yes.

The agreement itself carries no price. The exact rate for each engineer is in that engineer’s statement of work (SOW), because each engineer’s rate depends on their own salary expectations. Our standard terms are on Trust and standard terms.

The coding challenge is graded automatically and the interview is scored by AI. A person at Ruzora reviews every result before an engineer can reach a shortlist, and you make the hire-or-pass call. Sol never decides who gets hired.

Candidates are told the same before they start, including that their interview is recorded and how to ask for a human review: AI interview notice.

The same two evaluations and the same integrity review are available for a candidate from your own pipeline. Send us a CV and get our vetting report back, free, or have us run the coding challenge and the interview on your candidate before you make the offer. See the vetting service and the free candidate check. We only contact your candidate if you ask us to, and we never recruit them.

Background checks, right-to-work and criminal-record checks are not part of Ruzora’s vetting; where your engagement needs them, they are arranged per statement of work. Data handling for recordings and assessment results is covered by the Privacy Policy. Anything else: team@ruzora.com.