Something significant shifted in UK hiring last year. According to recent data, 50% of UK employers have now removed degree requirements from job postings — up 28% from the year before. Only 14% of UK job adverts currently require a university degree.
This isn't a trend. It's a restructuring. And if your interview prep is still built around talking through your CV and credentials, you're preparing for a process that's rapidly disappearing.
Skills-based interviews work differently. Here's what they look like, why they're spreading, and how to actually prepare for them.
What Is a Skills-Based Interview?
A skills-based interview (also called a competency-based interview) is designed to assess whether you can do the job — not whether your background looks right on paper.
Instead of "Walk me through your CV", you get questions like:
- "Give me an example of a time you had to learn something quickly under pressure."
- "Describe a situation where you had to deliver a project with incomplete information."
- "How have you handled a disagreement with a colleague about technical direction?"
Every question is asking for evidence. The interviewer isn't interested in what you know in the abstract — they want to see how you've applied it in the real world.
This format has been common in structured graduate schemes and public sector roles for decades. What's changed is that it's now the dominant format across tech, finance, product, and beyond.
Why Companies Have Made the Switch
Two things pushed this accelerating shift.
First, degree requirements were creating liability. In the UK, requiring a degree for a role where it isn't genuinely necessary can constitute indirect discrimination under the Equality Act — it disproportionately excludes candidates from lower-income backgrounds, certain ethnic groups, and older workers. With 77% of the working population lacking a university degree, the talent pool shrinkage was also a practical problem.
Second, credentials don't predict performance. Skills tests, structured competency interviews, and practical exercises turn out to be far better predictors of how someone will actually do in the role. That's not a new finding, but companies are finally acting on it at scale. 77% of UK employers now use skills assessments as part of their hiring process.
The result: hiring managers who used to ask "where did you go to university?" are now asking "show me what you can do."
What to Expect in a Skills-Based Process
The format varies by company, but most skills-based hiring processes involve some combination of:
1. Competency questions (behavioural) Structured around the STAR method — Situation, Task, Action, Result. You'll be asked to recall specific examples from your experience. These aren't hypotheticals. "What would you do if…" is a different question from "Tell me about a time when…"
2. Practical exercises or simulations A take-home task, a live coding test, a case study, or a role-play. These are increasingly common at mid-stage, before or instead of a technical screening call.
3. Structured scoring Your answers are often rated against a rubric. Interviewers at companies with formal skills-based processes are scoring your responses in real time — clarity, evidence quality, relevance, depth. It's more rigorous than an unstructured chat, which is actually good news for candidates who prepare well.
How to Prepare
Build an evidence bank first
Before you practise answering questions, build the raw material. Write down 8–12 strong examples from your experience — projects, challenges, failures, team situations, high-stakes deliveries. For each one, note the context, what you specifically did, and the measurable outcome.
These become the building blocks you draw on throughout the interview. Most competency questions can be answered with the right example if you've mapped your story bank in advance.
Prioritise depth over breadth in your answers
The single most common mistake in skills-based interviews is giving a thin answer — technically correct, but lacking evidence. "I improved the process" is not an answer. "I reduced our deployment time from 4 hours to 40 minutes by introducing a parallel pipeline" is.
Good answers have:
- A specific situation with real stakes
- Your individual contribution (not "we")
- A concrete, quantified result where possible
- A brief reflection on what you learned
Practise speaking, not just thinking
Reading through examples in your head is not the same as articulating them under pressure. The gap between knowing your stories and delivering them fluently — at a pace that's easy to follow, without filler words, without trailing off — is where most people lose points.
This is the part that takes actual spoken repetition. Record yourself answering questions. Listen back. Notice where you say "um", where you speed up when nervous, where your answer loses structure. Then adjust and repeat.
Tools like Instant Interview let you practise this with a live AI interviewer that adapts its follow-up questions based on your answers — and scores your responses on STAR structure, delivery pace, and filler word rate. It's the closest thing to real practice without booking a friend for an hour.
Prepare for follow-up probes
Skills-based interviewers are trained to go deeper. If your answer is thin, they'll push: "What was your specific role in that?" or "What would you do differently now?" These aren't hostile — they're looking for the signal beneath the surface.
The best way to prepare is to interrogate your own answers. After you give an example, ask yourself: could an interviewer legitimately challenge any part of this? If yes, have a sharper version ready.
Research the skills framework, not just the role
Many organisations — especially large ones — publish competency frameworks or list the skills they assess on their careers page. If they do, this is the single most valuable thing you can read before an interview.
Map your evidence bank directly to their stated competencies. If they're hiring for "stakeholder management", "delivery under pressure", and "technical leadership", you should walk in with a pre-loaded example for each.
If the company doesn't publish a framework, look at the job description and extract the implied competencies. "You'll work cross-functionally with design, data, and engineering" implies: collaboration, communication, managing without authority.
The One Mistake That Kills Skills-Based Interviews
Treating competency questions as conversation rather than evidence delivery.
Skills-based interviews are structured for a reason. When you drift into a vague narrative — "So I've always been someone who takes ownership, and in my last role, we had this situation where basically the team was struggling…" — you're giving the interviewer nothing they can score.
Be direct. Give the context in two sentences. Describe what you did. Say what happened. That's the structure. It feels mechanical at first, but with practice it becomes natural — and the scores reflect it.
What This Means for Your Prep Timeline
If you have an interview coming up, prioritise in this order:
- Build your evidence bank (1–2 hours, one-time)
- Map examples to the role's competencies (30 minutes per application)
- Practise out loud until your delivery is fluent, not just accurate (ongoing)
The shift to skills-based hiring is good news for candidates who prepare well. It levels the playing field — the person who can demonstrate real competence clearly and concisely will consistently outperform someone with a stronger CV who can't articulate their work under pressure.
Prepare for the format, not just the questions.
Jacob, Instant Interview
