Beyond the Resume: What Skills-Based Hiring Actually Looks Like

Every few months, someone declares the resume dead. It isn’t. We still ask for one, and so do you. What has changed is the job it does. The resume used to be the gate: it decided who got an interview. In today’s market, it has become the context, and something else decides.

That something is skills-based hiring, and most companies say they are doing it. Far fewer actually are.

What a resume can and can’t tell you

A resume is a record of where someone has been. It is good at that. It tells you the industries they know, the size of the team they have run, how long they stay and whether their career has a direction.

What it cannot tell you is whether they can do the job you are hiring for. A title is not a skill. “Managed a $4M budget” says nothing about how well that task was done. And with AI polishing more applications than ever, even the wording is less of a signal than it was. The document that gets someone in the door is easier to perfect than it has ever been. The work underneath it is not.

Saying it and doing it are different things

Most companies now describe themselves as skills-based employers. Look at the data and the picture changes. When Harvard Business School and the Burning Glass Institute tracked companies that dropped degree requirements, only 3.6% of roles were actually affected, and for most of those, who got hired did not change. Nearly half the companies were skills-based “in name only”: the job posting changed, the hiring did not.

That is the gap. Deleting “bachelor’s degree required” from a posting is a policy. Skills-based hiring is a process, and it happens in the interview room, not the job posting.

What it actually looks like

1. Write the role as outcomes, not credentials. Instead of “five years’ experience and a degree in accounting,” write what the person must be able to do in the first year: close the month in five days, build the board pack, and manage two direct reports. Defining the outcomes informs your interview process.

2. Ask for a work sample. Assign a short, realistic task from the actual job. A sales candidate works a mock discovery call. A controller reviews a set of numbers with a problem hidden in them. An hour of real work tells you more than an hour of questions about work.

3. Run a structured interview. Ask the same questions for every candidate, scored against the same criteria, before anyone compares notes. Unstructured interviews reward confidence and rapport. Structured ones reward the ability to do the job.

4. Keep the resume. Change its job. It is still the fastest way to understand someone’s context and ask better questions. But, it should not be the reason someone is in or out.

Why it is worth the effort

The companies that do this properly get two things. Better hires: in SHRM’s skills-first hiring research, organizations that consistently use skills-first strategies were more likely to exceed their financial objectives than those that don’t (35% versus 27%), and about a third of organizations now hire this way as a matter of course. And a bigger pool: the moment you stop screening on credentials, candidates who took a different route into the work become visible — and in a market this tight, they are being hired by someone.

How FGP does it

We have hired this way for years: competency-based interviews scored against the role, assessments where they add real signal, and shortlists built on what candidates can do, with the resume as the map, not the verdict. It is also part of why candidates trust the roles we bring them — a process that measures the work attracts the people who can do it. To see how that translates for your team, start with how we work with companies, or have our consulting team build the outcome-based job descriptions, structured interview guides and manager training to run it in-house.

Keep asking for the resume. Just don’t let it make your decision. If you would like help with the part that comes after the upload, we’d love to connect.