For decades, the CV was the gatekeeper. It told you where someone went to university, which companies they'd worked for, and how neatly they could summarise their career in two pages. For a long time, that was enough. In 2026, it increasingly isn't.

Skills-based hiring was one of the most talked-about shifts in Q1 — and for good reason. The way engineering talent is being evaluated is changing at a pace that most hiring processes haven't caught up with. The companies that close the gap fastest will win the talent war in Q2 and beyond.

Why the CV has started to fail

The CV was built for a slower-moving world. It captures history, not capability. It tells you what someone did, not what they can do right now — and in a landscape where the tools, languages, and practices that define great engineering are evolving quarter by quarter, that distinction matters enormously.

The rise of AI-native development has accelerated this. An engineer who spent three years at a respected firm but hasn't adapted to modern tooling may look stronger on paper than a self-taught developer who's been building production-grade systems with the latest stack for the past eighteen months. The CV can't reliably tell you which is which.

There's also a supply issue driving the shift. With demand for senior AI and engineering talent far outstripping availability, hiring managers who filter purely on pedigree — prestigious universities, brand-name employers — are dramatically narrowing their pool and often missing the strongest candidates in it.

What skills-based hiring actually looks like

The shift isn't simply about asking candidates to complete a technical test. The most effective hiring managers are rethinking the entire evaluation framework.

It starts with being precise about what the role actually requires. Not "five years of Python experience" but specific capabilities: can this person design a scalable data pipeline? Can they debug a failing deployment under pressure? Can they work effectively alongside AI tooling to increase their own output? When you define requirements at the skill level rather than the credential level, you open the door to candidates who would otherwise never get a first conversation.

From there, structured evaluation replaces gut instinct. Portfolio reviews, pair programming sessions, take-home projects scoped to real problems the team is solving — these give signal that a CV simply cannot. They also reduce bias, because they shift the conversation from where someone came from to what they can actually deliver.

What this means for Q2

The hiring managers who will move fastest in Q2 are those who've already separated job requirements from job assumptions. They're not asking "does this person look right?" They're asking "can this person do this?" — and they've built a process that answers that question reliably.

If your hiring process still routes predominantly on CV screening, you are likely rejecting candidates who would perform in the top quartile of your team, and progressing candidates who look the part but struggle to deliver it.

The talent market in Q2 will be competitive. The companies that evaluate on demonstrated skill — not documented history — will hire faster, hire better, and build stronger teams as a result.

At Tides Digital, skills-based evaluation is built into how we source and present candidates. We go beyond the CV so you don't have to start from scratch.