The resume problem is not that candidates lie about their skills. It is that resumes ask hiring teams to trust skill claims without giving them anything to verify. A line that says "Proficient in Python, SQL, and statistical modelling" is a claim with no evidence attached. The hiring team is left to either assume it is true, design an assessment to test it, or skip the question and rely on the interview to reveal whether the claim holds up. None of those are good options at scale.
The fix is structural. Verification means linking each skill claim to an artefact a hiring team can actually check. The mechanisms exist — they just have to be operationalised inside the funnel. This article covers what verification means, the three approaches in current use, when each works, and how to put them into practice without rewriting your hiring process from scratch.
What verification actually means
A claim is verified when someone other than the candidate has reviewed evidence of the skill and produced a record that travels with the candidate.
The clauses matter. Someone other than the candidate — self-assessment is not verification. Reviewed evidence — reading a CV bullet point is not verification of the skill, only of the claim. A record that travels — a verbal endorsement that lives in someone's head and never reaches the hiring team is not actionable.
The skill claim is verified once a hiring team can answer, with a click rather than a meeting, the question every recruiter eventually has to ask: show me proof that this person can do the thing they say they can do. The mechanisms differ in what the click reveals — a test score, a reviewed deliverable, a cryptographically signed credential — but they share the underlying property of being checkable without a phone call.
The three approaches
Skills assessments
The oldest mechanism. Hiring team designs a structured exercise — coding test, case study, work-sample task, structured behavioural exercise — and the candidate completes it under controlled conditions. The hiring team scores the work against pre-set criteria. The score becomes the verification record.
Done well, assessments are strong evidence. The candidate produced the work in front of the hiring team's instrument; the score reflects how the work compared to a known bar; both inputs are auditable. Most major early-career employers use some form of assessment in their funnel — coding tests in software engineering, case interviews in consulting, structured Excel exercises in banking, take-home tasks in design and product roles.
The cost is operational. Assessments require a hiring team to design the exercise, calibrate it on a known population, score consistently across reviewers, and recalibrate when the role evolves. They also produce a one-shot signal — pass or fail at this specific instrument — that does not compose with anything else the candidate has done. A candidate who failed your specific assessment may have demonstrated the same skill ten times in their portfolio; the assessment does not see that.
References
The oldest informal mechanism. Someone who saw the candidate work — a former manager, a professor, a colleague — vouches for them. The reference can be structured (formatted check call, scripted questions, transcribed answers) or informal (a phone conversation between two senior people in adjacent fields).
References are powerful when they are real. A senior person with stakes in their own credibility, who can describe specific work the candidate produced and specific situations the candidate handled, is harder to fool than any other verification mechanism. The texture of a real reference call is unmistakable: the referee remembers things the candidate could not have made up because they came from inside the work.
The cost is reach. References scale poorly. They take time, they consume the referee's attention, they cannot be batched. Most hiring funnels reserve references for the final stage of senior hires; for early-career roles where the volume is high and the candidate's network is shallower, the references that exist are often weak (a single professor, an internship manager who barely remembers the candidate) and the cost of running them is disproportionate to the signal.
Verifiable credentials
The newest mechanism, and the one that solves what assessments and references cannot. A verifiable credential is a digitally signed claim about a candidate, issued by one party — a university, a learning platform, a certifying body — and independently checkable by any third party using open cryptography. The format is defined in the W3C Verifiable Credentials Data Model standard and Open Badges 3.0.
The mechanism inverts the assessment-and-reference cost structure. The credential travels with the candidate, can be checked in seconds without contacting the issuer, and stacks across many issuers. A single candidate can hold dozens of credentials from different programmes, employers, and platforms — each with its own evidence, each independently verifiable, each readable by any hiring system that understands the standard.
For early-career hiring, the practical advantage is that verifiable credentials let you read the work the candidate has shipped. A credential issued by a platform like Ewance is tied to a specific challenge a student completed: the brief, the deliverable, the rubric assessment, the date the credential was issued, all preserved in the credential itself. A recruiter clicks through and sees not just "this person has the skill" but "here is the work they did that demonstrates it, and here is how it was assessed".
When each approach works
Assessments work when you have a small set of well-defined skills the role requires, you have the volume to amortise the cost of designing and running the exercise, and the role is sufficiently standardised that the assessment generalises. They work less well when the role is broad, the skills required vary by team, or the candidate population is small enough that calibration is unstable.
References work when you are hiring for senior or specialised roles where each candidate goes through a hand-crafted process, the reference's senior status meaningfully informs the hiring decision, and the cost of a wrong hire justifies the time investment. They work less well at the top of the early-career funnel — for entry-level hiring at scale, references are a final-stage check, not a screening tool.
Verifiable credentials work when candidates carry credentials issued by platforms or institutions whose standards you trust, the credentials cover the skills the role actually requires, and your hiring system can read the credentials at scale. The practical question is not whether verifiable credentials are stronger than the alternatives — they are simply different artefacts in the funnel — but whether your candidate population has them in sufficient density to make verification at scale viable.
The honest answer for most early-career hiring teams is to use all three. Verifiable credentials at the top of the funnel to filter on demonstrated work. Assessments at the mid-funnel to confirm specific skills against a controlled bar. References at the final stage to validate the candidate as a person who shows up and works.
Verifiable credentials in practice — what to ask for
If you want to operationalise credential-based verification, start by adding a question to your application form — "Share any verifiable credentials you hold (W3C Verifiable Credentials, Open Badges 3.0, or platform credentials with a public verification URL)" — and make it optional. The response rate from candidates who have credentials will tell you whether this verification approach is viable for your candidate population.
For each credential a candidate shares, ask three questions before treating it as evidence. What is the issuer's standard? A credential from an institution with a published rubric and a known assessment process is stronger evidence than a self-attested badge from a course-completion platform. What does the credential cover? A credential tied to a specific deliverable with a published rubric tells you more than a credential that just attests to course completion. Does the credential resolve? Click the verification URL; the cryptography either confirms the credential is genuine or it does not. The check is binary.
Ewance credentials, for example, are issued in W3C Verifiable Credentials Data Model 2.0 format with Open Badges 3.0 metadata, anchored on Ethereum L2 by LearnCoin so the issue date and content are tamper-evident. The credential URL exposes the brief the student worked from, the deliverable they shipped, the rubric the work was assessed against, and the assessment itself. A recruiter reading the credential can form a judgement about both the skill claim and the supporting work without contacting Ewance, the candidate, or anyone else. Try the verification flow at /tools/credential-verifier/ to see what the recruiter side actually looks like.
How to operationalise verification in your hiring funnel
Start with one role. Pick the entry-level role you fill the most of, where the time-cost of mis-hires is highest and the signal you currently have is weakest. Map the skills that role requires onto verification mechanisms — assessments for the technical skills you can test cheaply, credentials for the work-product evidence, references for the late-stage character check.
Add a credentials field to the application form for that role. Make it optional. Watch for ninety days how many candidates submit credentials, what kind, and whether the credentials correlate with downstream interview performance. The data tells you whether verification is meaningfully tightening your funnel, or whether the verified-credential population is still too small.
For roles where credentials are sparse but the signal is needed, run a sponsored challenge — through Ewance or a similar platform — that produces credentials tied to your actual hiring criteria. The candidates who ship strong work on the challenge become verified for the skills you tested for, and the credentials they earn travel with them into your funnel and beyond.
The goal is not to replace your existing hiring process. It is to give the early stages of that process something to verify on, so by the time a candidate reaches an interview slot you have already filtered on demonstrable work — not just self-described skills.
What to do this quarter
Pick the role. Add the credentials question. Try the verifier. Watch what changes in the funnel.
If you want to see the candidate-side of the equation — students working through real challenges and earning the kind of credentials your hiring team would actually want to verify — start at the industry overview, or book a demo to walk through the verifier with a real Ewance credential.
