The one-page résumé is a remarkable piece of compression. In a few hundred words, it is supposed to convey a person's education, employment history, competences and character, in a format that a stranger will scan in six seconds. It is a tool built for a world of standardised careers, and it is showing its age.
The replacement being tested in several industries is the skills record: a verified, portable account of what a person can actually do. It sounds like a technical upgrade. In practice, it raises questions about trust, fairness and who gets to define competence.
Why the résumé fails
The résumé's weaknesses are well known. It rewards people who are good at writing about themselves. It compresses complex work into job titles. It relies on credentials that may be outdated or irrelevant. And it is easy to inflate: surveys consistently find that a significant share of applicants misrepresent something.
Employers respond by adding filters, tests and interviews, which pushes the cost of screening onto candidates. A graduate may spend hours on assessments for a job they will never hear about again.
A skills record tries to solve this by recording evidence rather than claims. A completed project, a verified certificate, a signed-off practical assessment, a portfolio of work: each is a data point that can be checked.
What verification means
The key word is verified. A self-declared list of skills is just a résumé in a different font. What makes a record useful is that someone other than the candidate has confirmed it: an employer, a training provider, a professional body, or an assessment platform with an auditable process.
This is where the model gets complicated. Verification costs money, and the organisations that can afford it are usually large. Smaller employers and community training providers may be locked out, which could entrench the advantage of people who already have access to formal credentials.
There is also the question of ownership. If a skills record lives on an employer's platform, what happens when the person leaves? If it lives on a vendor's platform, what happens when the vendor closes? Workers need portability, and portability requires standards.
The fairness problem
Any new hiring tool inherits the biases of its designers. A record that rewards certain kinds of evidence — certificates, digital portfolios, formal assessments — may disadvantage people whose competence was developed informally, or whose work is not easily documented.
There is a risk of what researchers call "evidence bias": the tendency to trust what is measurable over what is real. A care worker's ability to calm a frightened patient is not captured by a badge. A experienced technician's judgement is not captured by a multiple-choice test.
The best schemes address this by combining verified records with structured references and practical trials. The worst simply digitise the old hierarchy.
What candidates want
For all the talk of transformation, the candidate experience is often worse than the résumé era. Applying for a job now frequently means creating an account, uploading a CV, retyping the same information, completing an assessment, and then waiting for an automated rejection.
A skills record could reduce that friction if it were genuinely portable: fill it in once, share it with consent, revoke access when you want. That is a product design problem as much as a technical one, and it requires employers to accept records they did not create.
Some are starting to. Consortiums of employers and training providers have begun to agree on common formats, and a few platforms now support open standards for credentials. Progress is slow, but the direction is clear.
The human remainder
Even a perfect skills record would not replace the interview, because most jobs require something that cannot be certified in advance: whether you can work with this particular team, in this particular place, at this particular moment.
What a good record can do is get the conversation to the right starting point. Instead of spending the first interview establishing whether someone can do the basic tasks, the interviewer can ask how they handled a difficult project, or what they would do differently. That is a better use of an hour.
The résumé will not disappear. But it may become a summary of a richer record rather than the record itself. That is a modest change, and a meaningful one: it shifts the question from "what does this person claim?" to "what can this person show?"
