Skip to content
← Insights
Nov 14, 20264 min read

Another hiring gate still has to prove something

Skill assessment, identity verification and account access answer different questions. Give each hiring check a purpose and a route for correcting mistakes.

A pastel application folder beside a blank identity card, a physical access key and an inspection magnifier.

Adding another question to a job application proves that an applicant completed another question. Whether it tests a useful skill or reduces fraud depends on the question, the process, and what happens after the answer arrives.

Recruiting needs several kinds of evidence. A work sample can show how someone approaches a task. Identity checks address who is entering the employment relationship. Access controls limit what an account can do after hiring. Treating any one of these as proof of the others creates a gap.

The aim should be a process in which each step resolves a named uncertainty. Unnecessary steps consume applicants' time while leaving the consequential uncertainty untouched.

Name the question each check answers

A short technical exercise may show that the submitted solution meets a requirement. It may leave uncertainty about the tools used, the assistance received, and who will actually do the work after an offer. Those are different questions to resolve explicitly.

The U.S. Office of Personnel Management's structured-interview guidance describes predetermined questions and common rating standards. Structure makes the assessment procedure inspectable. It does not turn an interview into identity verification.

If a role permits AI assistance, explain that before the task. Evaluate the candidate against the expected work conditions. A concealed ban that is enforced through guesses about writing style creates a different test from the one the applicant understood.

Portfolio evidence has limits too. A repository can help support a discussion about decisions and contributions. Its existence cannot prove that every claimed contribution belongs to the person presenting it. Follow-up questions should address the relevant work without demanding disclosure of a previous employer's confidential material.

Remote hiring has an access problem after the interview

The FBI's October 2026 advisory on fraudulent remote IT workers describes organised activity and recommends layered verification throughout employment. It is a warning about a documented threat, not an estimate of the proportion of ordinary applicants who are fraudulent.

That distinction prevents an indiscriminate response. A weak signal should prompt proportionate review in context. Nationality, accent, or a poor video connection is not proof of deception. Legitimate applicants can encounter technical and access difficulties.

The employer also needs controls after selection. An identity check cannot compensate for an account with excessive permissions. A technically capable employee can still receive access the role does not require. Review what is granted, who approved it, and how it will be removed.

Changes during onboarding deserve a defined process. If payment or contact details change, verify the change through the organisation's approved channel. The relevant staff need a way to escalate uncertainty without improvising a new collection of sensitive documents.

More personal data creates another responsibility

ICO recruitment guidance addresses the handling of applicants' information. The page is under review following the Data (Use and Access) Act. The purpose and necessity of a check should be established before collecting the information. A document retained by a recruiter becomes data the organisation must protect and manage.

Decide which stage actually requires the check. A process that needs identity confirmation before access is granted does not automatically need every early applicant to submit a passport. The organisation should establish its lawful requirements and retention rules for its location and role.

Give applicants an understandable explanation of the step and a contact for resolving a problem. A legitimate candidate should have a route to correct a mismatched record. An unexplained automated failure can otherwise become a rejection the hiring team never investigates.

This is a process-design question with legal consequences. A generic online checklist cannot decide the lawful basis or exact documents for every employer. The hiring organisation needs those decisions settled in its own procedure.

Measure what the added step changes

Before introducing a new gate, record the uncertainty it is meant to reduce. Then examine completion rates and review outcomes. If suitable applicants leave because the task is burdensome, that cost belongs beside any reduction in unwanted submissions.

Keep assessment disagreements separate from verification failures. A candidate who lacks a required skill and a record that needs correction should not disappear into the same vague rejection category. Different findings require different actions.

The process is ready when staff can explain what each check establishes, what remains uncertain, and who handles an exception. A longer funnel can still be a weak funnel. Each step should earn its place through evidence relevant to the decision it controls.

HiringSecurityWork