Skills-based hiring: why startups should stop reading CVs
Degrees and job titles tell you almost nothing about whether someone can do the work. Here is how to hire based on what people can actually do.
The CV is lying to you
A candidate has a computer science degree from a good university and 4 years at a well-known company. Great CV. You bring them in. They can't solve a basic coding problem.
Another candidate dropped out of university, taught themselves to code, and spent 3 years freelancing for small companies you've never heard of. Terrible CV. They're one of the best engineers you'll ever interview.
This happens constantly. And yet most companies still screen CVs the same way: degree, company names, years of experience, job titles. None of these reliably predict whether someone can do the work.
What skills-based hiring actually means
It's not complicated. Instead of filtering candidates by credentials, you filter them by demonstrated ability. Can they do the job? Prove it.
This doesn't mean "no interviews." It means the interview tests real skills, not proxies for skills. Instead of asking where they went to school, you give them a problem similar to what they'd face in the role and see how they handle it.
77% of companies say they struggle to find talent. Most of them are looking in the wrong places because they're filtering out capable people based on irrelevant criteria.
Why this matters more for startups
You can't afford to fish from a small pond
Big companies can require a degree from a top university because they get 500 applications per role. You don't. Every requirement you add that doesn't directly relate to job performance shrinks your candidate pool. At a startup, you need every qualified person you can get.
Startup work doesn't map to traditional credentials
A marketing degree teaches you marketing theory. Your startup needs someone who can write copy, set up analytics, run paid campaigns, and build a content calendar — often in the same week. The person who learned these skills by actually doing them for 2 years is more useful than someone who studied them in a classroom for 4.
The best startup employees are often non-traditional
Career changers. Self-taught developers. People who built businesses on the side. People who took unconventional paths often have exactly the scrappiness and adaptability that startups need. Traditional CV screening filters these people out.
How to actually do it
Step 1: Define the skills that matter
Before you write the job ad, list the 5-7 specific skills this person needs. Not "good communication" — that's a personality trait, not a skill. Things like: "can write SQL queries to extract and analyze customer data," "can create a paid campaign from scratch and optimize based on performance data," "can debug a production issue under time pressure."
Be specific enough that you could test each skill in an interview.
Step 2: Remove credential requirements from the job ad
Drop "Bachelor's degree required." Drop "5+ years of experience." Instead, describe what the person will do and what skills they need to do it. You'll get a wider range of applicants, including people who can do the job but wouldn't have applied because they don't have the "right" background.
Step 3: Use work samples and practical tests
Ask for a portfolio. Give a take-home assignment (short — 2 hours max, and pay for it). Do a live problem-solving session. For engineering, pair programming on a real problem. For marketing, a mock campaign brief. For sales, a role-play call.
The goal isn't to get free work. It's to see how someone thinks and works, which a CV can never show you.
Step 4: Structure your interviews around skills
Create a scorecard for each skill. Every interviewer evaluates the same skills using the same criteria. This removes the gut-feel bias where interviewers hire people who remind them of themselves.
Ask behavioral questions tied to specific skills: "Tell me about a time you had to learn a new tool quickly to deliver a project. What was the tool, what was the project, and what was the result?"
The objections (and why they're wrong)
"But a degree shows they can learn"
So does completing an online course, building a side project, switching careers, or any number of other things. A degree is one signal of learning ability. It's not the only one, and it's often not the best one.
"Experience matters"
Yes. But years of experience and quality of experience are different things. Someone with 3 years of intense, hands-on experience at a fast-moving startup often outperforms someone with 7 years at a company where they did the same thing on repeat.
"It takes too long to evaluate skills properly"
It takes longer to evaluate skills than to scan a CV. It takes much less time than hiring the wrong person, managing them for 6 months, letting them go, and starting over. The upfront investment in better evaluation saves you from the much larger cost of bad hires.
What this looks like in practice
We place candidates across European startups. The companies that adopt skills-based hiring consistently find better matches. They hire faster because they're not waiting for the "perfect CV" that doesn't exist. They retain longer because people hired for what they can do are more likely to succeed than people hired for what they've done.
Start small. Pick one role. Remove the degree requirement. Add a practical assessment. Compare the quality of candidates you get versus your usual process. The results speak for themselves.