What is skills-based hiring?

Skills-based hiring means evaluating candidates on demonstrated ability to do the job, rather than proxies for ability like a degree, a job title, or years of experience. It usually means dropping degree requirements and adding some form of skills assessment or work sample to the process.

Does skills-based hiring actually widen the talent pool?

Yes, and by a lot. LinkedIn's 2025 Skills-Based Hiring report found it expands the qualified candidate pool by a median of 6.1x globally compared to traditional hiring, and 8.2x for AI-specific roles.

Is a skills test enough on its own?

A test tells you someone can solve a bounded problem under exam conditions. It does not tell you how they handle ambiguity, ownership, or a real deadline, which is most of what an early startup hire actually needs. Most founders get more out of a real work sample or a look at something the candidate has already shipped.

Skills-Based Hiring: A Complete Guide for Startup Founders

"Skills-based hiring" has become one of those phrases that gets used to mean three different things depending on who is saying it. If you are a founder trying to decide what to actually do differently, it is worth pulling those apart.

Three ways to actually evaluate skills

Assessments. A standardised test of a specific skill, taken online, scored automatically. Good for filtering at volume, weak at telling you anything about judgment, communication, or how someone behaves under real ambiguity. This is the version most HR tech vendors sell, because it is the easiest to package as software.

Work-sample interviews. A short, paid or unpaid exercise that mirrors a real task: fix this bug, mock up this screen, write this cold email. Better than a test because it looks like the actual job. Still artificial, because everyone knows it is a performance, and it only ever tests one narrow slice of the role.

Proof of prior work. Evidence the candidate produced before you ever spoke to them: a shipped project, a deal they closed, a piece of writing, an open-source contribution. This is the richest signal of the three, because it was not created for your benefit. Nobody optimises a two-year-old GitHub commit history for a job interview six months in the future.

Each is a step up from the last in how well it predicts real performance, and each is a step down in how easy it is to run. That trade-off is exactly why most companies default to the easiest option (the resume, which is really assessment number zero) rather than the best one.

Why this matters more at Series A and B than anywhere else

LinkedIn's 2025 Skills-Based Hiring report found that dropping degree and title requirements in favour of skills expands the qualified talent pool by a median of 6.1x globally. For AI-specific roles, the expansion is 8.2x, and non-degree candidates see 6% greater pool expansion than degree holders on average. Candidates without a traditional pipeline into a role, career-changers, self-taught engineers, people from outside the usual university-to-grad-scheme track, are disproportionately filtered out by title and degree requirements that have little to do with whether they can actually do the job.

For an early-stage startup in Australia or New Zealand, where the pool of "obviously qualified" candidates by traditional metrics is already small, cutting yourself off from 6x the candidates over a proxy that does not predict performance is expensive. Cut Through Venture's Q2 2026 data shows the region's early-stage market is narrowing, not widening: deal count is at its slowest pace since before 2020 even as total capital stays relatively high, meaning fewer companies are competing for a talent pool that has not grown to match. Every founder hiring right now is competing with other well-funded companies for the same small set of "obvious" candidates. Widening what counts as evidence is one of the few levers a founder can pull without spending more money.

The practical version for a founder with no recruiting team

You do not need an assessments platform or a formal work-trial program to hire on skills. You need a habit:

Before you look at anyone's resume, decide what evidence would actually convince you this person can do the job. Be specific: not "strong communicator" but "has written something publicly that a non-technical person could understand."
Ask for that evidence directly in your job post or outreach, instead of asking for years of experience or a specific past title.
Spend your limited screening time looking at the evidence, not the resume. A five-minute look at a real project tells you more than a twenty-minute resume screen.
Keep the interview for judgment and fit, not for re-verifying things a work sample already showed you.

This is close to how recruiters at good agencies already operate, they build a mental model of what "good" looks like for a role and go looking for it, rather than waiting for it to apply. The difference at a startup is you usually do not have a recruiter doing that legwork for you.

Where this gets hard, and what to do about it

The honest failure mode of skills-based hiring is that it takes real time per candidate, and founders do not have real time. That is the case for using a network built around signal rather than trying to build the evaluation machinery yourself: on Matchbox, candidates arrive with the evidence already attached to their profile, so screening is a matter of reading it rather than chasing it down. Browse the network to see what that looks like in practice, or read the startup hiring playbook for the rest of a founder-led process built the same way.