Verified skills assessment
The candidate proves what they can do once. Every employer they apply to reads the same verified result, and nobody has to take a resume on faith.
A verified skills assessment is a supervised test of role-relevant ability whose result is recorded and reused rather than re-run for every application. On CalHire a candidate completes one baseline assessment, receives a skills profile scored per skill, and that profile stays valid for 90 days. Employers see the verified score instead of a self-reported claim, and the candidate does not sit the same test again for every job.
Last reviewed
The short version
- A resume is a claim. An assessment result is evidence. The whole design follows from that one difference.
- The baseline assessment is taken once and reused: valid for 90 days, retakeable after a 30-day cooldown.
- Scores are recorded per skill, not as a single number, so an employer can weigh the skills their role actually needs.
- A low score never auto-rejects anyone. It changes where a candidate sits in a ranked list that a human still reads.
Why the resume stopped working
A resume is a document a candidate writes about themselves, formatted to please a screening process nobody has explained to them. It reports where someone has been, not what they can do. Those are different questions. Those two things correlate loosely at best, and the correlation is weakest exactly where hiring most needs to be accurate: career changers, self-taught engineers, people who took time out, people whose last employer was never going to be a household name.
The screening layer built on top of it has made this worse rather than better. Keyword matching rewards candidates who know which words to use. Generative writing tools have made a polished, targeted, entirely unverifiable resume free to produce at scale, so whatever signal a well-written application once carried has largely evaporated. Recruiters are now reading more applications containing less information.
The alternative is not a better parser. No parser fixes a document nobody has to tell the truth in. It is to stop asking candidates to describe their ability and start asking them to demonstrate it, once, under conditions everyone can see.
How the assessment works
One sitting, generated for the skills the candidate declares, supervised by the integrity layer.
- 1
The candidate declares their skills
Not a job title and not a work history. A set of skills they claim to have, which determines what they are asked. Someone who declares nothing is assessed on nothing, so the declaration is an honest starting point rather than a formality.
- 2
The assessment is generated for those skills
Questions are produced per candidate against the declared skill set rather than drawn from a fixed public bank. That matters for a practical reason: a static question bank leaks, and a leaked bank measures who found the leak.
- 3
They sit it once, under supervision
The integrity layer records environmental, behavioural and content-authenticity signals during the session. There is no webcam requirement and no proctor watching a video feed. What is being checked is whether the work is the candidate’s own, not whether they looked away from the screen.
- 4
The result becomes a skills profile
Each declared skill gets its own verified score. The profile belongs to the candidate rather than to one employer’s pipeline, so applying to a second job does not mean sitting a second test.
- 5
It expires, on purpose
A verified score is valid for 90 days. After that it needs refreshing, because a two-year-old result is a claim about the past dressed up as evidence about the present. Candidates can retake after a 30-day cooldown, which stops score-farming through sheer repetition.
What an employer actually receives
A score per skill
Not one composite number. If your role needs strong SQL and passable writing, you can weight it that way rather than accepting an average that hides both.
A date, and an expiry
Every verified score carries when it was earned and when it lapses. A result you cannot date is a result you cannot rely on.
The integrity record
The signals raised during the session, with PII-free evidence attached, so a flagged result can be reviewed by a person rather than quietly discarded.
The same test, for everyone
Every candidate for a role is measured against the same skills on the same scale. That is what makes a comparison between two candidates mean anything.
No identity attached
The profile reaches you without a name, photo, age, school or employer. You are reading ability in the literal sense that nothing else is available to read.
A record that survives the decision
Scores, weights and the human decision are written to a hash-chained audit trail. If you are ever asked to account for a hiring decision, the evidence exists.
What makes an assessment worth trusting
The technical term is validity: does the test measure the thing you care about, and does performance on it predict performance on the job. It is a real, measurable property, and most hiring assessments are never checked against it.
Three things move validity in the right direction, and the design follows all three. Content has to be job-relevant, which is why questions are generated against declared skills rather than pulled from a generic aptitude bank. Conditions have to be consistent, because a test that is easy for one candidate and hard for another measures the conditions rather than the candidate. And results have to be scored against a fixed rubric rather than an impression.
None of that makes a test perfect. Nothing makes a test perfect. It makes the error understandable, which is a lower bar than perfection and a considerably higher one than most resume screening clears.
What this does not do
An assessment does not tell you whether someone is a good colleague, handles pressure well, or will still want the job in a year. It measures a bounded set of skills at a point in time. Interviews, work samples and references exist because those other things matter, and all three are supported here rather than treated as replaced.
A verified score is not a guarantee against every form of cheating. The integrity layer raises signals with confidence levels; it does not deliver verdicts. Any decision that turns on an integrity flag is reviewed by a person, because a false accusation of cheating is a serious thing to get wrong.
Skills assessment does not by itself make hiring fair. It removes one large source of bias and introduces something new that has to be checked: whether the assessment produces different selection rates across groups. That is what the adverse-impact analysis in the compliance console is for, and it is not optional.
This fits badly where the skill genuinely cannot be assessed remotely in a sitting. Licensed clinical practice, hands-on trades, and roles whose core requirement is a supervised credential need that credential verified first. Assessment is the second step there, not the first.
Questions people actually ask
How long does the assessment take?
Why does a verified score expire after 90 days?
Can a candidate retake the assessment to improve their score?
What stops a candidate having someone else take the test for them?
Does the employer see the candidate’s name during assessment review?
Is the assessment identical for every candidate applying to a role?
Related
Where this connects to the rest of the platform.
Assessment integrity without surveillance
Four families of signal, each with a confidence level and PII-free evidence. No webcam, no verdicts, and environmental flags are excluded from scoring where accommodations apply.
Composite scoring and blind ranking
A composite score you set the weights for, defaulting to 40 percent test, 35 percent interview and 25 percent role fit. It orders a list. It never makes a decision.
Anonymous candidate screening
Employers evaluate candidates with no name, photo, age, school or employer attached, because that information is never sent rather than merely hidden.
Read the reasoning
The evidence and the argument behind what is on this page.
What skills-based hiring actually is (and what it is not)
Skills-based hiring decides on demonstrated ability, not proxies like degrees or job titles. What it means in practice, where it fails, and how to run it well.
ReadDoes your assessment predict anything? Validity for non-specialists
An assessment that feels rigorous can predict nothing. What validity and reliability mean, how to check yours, and the four ways hiring tests quietly break.
ReadDropping the degree requirement: what has to replace it
Removing a degree requirement without replacing the signal makes hiring more subjective, not less. What the degree was doing, and what to measure instead.
ReadDoes an ATS really reject your résumé? What actually happens
The "75% of résumés are rejected by robots" claim has no verifiable source. What an ATS actually does, where filtering really happens, and what to do about it.
ReadSee a verified pipeline for one of your roles
Post a role free and review anonymous, skill-ranked candidates. No card, no sales call to get started.