I’ve been watching SMEs struggle with the same problem for years now. You need better testing. You know you need better testing. But when you look at the market for QA engineers, the options feel impossible.

You can’t afford a senior at £57,500. You can’t wait six months to recruit one. And even if you could, there’s no guarantee they’d understand your specific stack or stick around long enough to make it worthwhile.

So you do what most teams do. You ask your developers to test their own work. You ask your product manager to click through things when they have time. Maybe you hire a junior and hope they figure it out.

None of this works. And I think the reason is simple.

We’ve been treating QA like a role you hire for, when it’s actually a capability you build.

The Problem With Buying Senior Talent

The median QA engineer salary in the UK is £57,500. That’s before you factor in recruitment costs, benefits, and the time it takes to onboard someone into your specific environment.

And here’s the bit that doesn’t get talked about enough. Senior QA engineers often come with assumptions baked in from their last company. They’ve worked in a different tech stack. They’ve used different tools. They’ve operated in a different workflow.

That’s not their fault. But it means you’re paying top dollar for someone who needs to unlearn as much as they need to learn.

Then there’s retention. 84% average team turnover is common across tech. You invest in someone, they get good at your systems, and then they’re headhunted.

You’re back to square one.

What If You Built Your Own QA Capability Instead?

I think there’s a better way. And it starts with recognising that QA isn’t just about finding bugs.

The best testers I’ve worked with aren’t the ones who’ve memorised Selenium syntax. They’re the ones who understand the product, the users, and the business logic well enough to ask the right questions.

They’re the ones who spot the edge case that breaks the checkout flow. Who notice that the error message makes no sense to someone in a hurry. Who flag the accessibility issue before it becomes a complaint.

You can’t buy that kind of contextual knowledge. You build it.

Option One: Hire an Apprentice

An apprentice isn’t a compromise. They’re someone you train specifically for your environment, your stack, your workflows.

The Level 4 Software Tester apprenticeship costs £18,000. If you’re an SME, the government funds 95% of that. If you can access levy transfer, it’s cost-neutral.

But the real value isn’t the subsidy. It’s what you get.

You get someone who learns your product from the ground up. Who understands why you built things the way you did. Who knows which areas are fragile and which are stable. Who can communicate with your developers in a way that actually helps them fix issues faster.

And retention? Apprentice turnover averages 39%. Some companies see as low as 15%. When you invest in someone’s career, they tend to stick around.

Option Two: Upskill Someone Already on Your Team

This is the option most people overlook. And I think it’s often the smartest move.

You’ve got a project manager who’s always spotting issues in staging. Or a content person who’s constantly finding broken links. Or a developer who’s good at thinking through user journeys.

These people already understand your business. They know the product. They’ve got institutional knowledge that a new hire would take months to develop.

What they don’t have is formal QA training. But that’s fixable.

You can upskill them through an apprenticeship. They keep doing their current role part-time whilst they learn testing properly. And at the end of it, you’ve got someone who can do both.

That’s not just cost-effective. That’s strategic.

What Good QA Actually Looks Like

I think we need to stop thinking about QA as “the person who clicks buttons to see if they break.”

Good QA is about three things.

Exploratory Testing

Automated tests handle the happy path. They check that the form submits. That the payment goes through. That the user gets logged in.

But automation doesn’t catch the weird stuff. The edge cases. The things that happen when a user refreshes mid-transaction, or uses a screen reader, or has a dodgy internet connection.

That’s where humans add value. And it’s not about experience. It’s about curiosity.

An apprentice who’s genuinely curious about how things break is worth more than a senior who’s just running through a checklist.

Maintenance and Hygiene

Every time your developers update code, automated tests can break. Not because the code is wrong. Because the tests are brittle.

This is the bit that gets neglected. Senior developers don’t want to spend their time fixing flaky tests. So the test suite slowly becomes unreliable. Eventually, people stop trusting it.

A dedicated tester owns this. They keep the tests working. They make sure the automation stays useful. They free up your senior developers to build features instead of babysitting test scripts.

The Bridge Between Tech and Users

Developers build for how the system should work. Users interact with how it actually works.

The gap between those two things is where most bugs live.

A good tester bridges that gap. They think like a user. They ask whether something makes sense, not just whether it functions. They flag the things that are technically correct but practically confusing.

And because apprentices are often learning the system alongside the users, they’re perfectly positioned to do this.

The ROI Is Faster Than You Think

The common pushback is time. “We can’t afford to train someone. We need someone who can hit the ground running.”

I get it. But here’s what actually happens.

Right now, your senior developers are spending 20-30% of their week on manual QA or bug triage. That’s expensive time. A senior developer at £60,000 costs you roughly £12,000-£18,000 per year just in QA work they shouldn’t be doing.

An apprentice recovers that time within the first quarter.

Then there’s the cost of bugs in production. Fixing something in staging costs you an hour. Fixing it in production costs you a day, plus reputational damage, plus support tickets.

A dedicated tester catches those issues earlier. The ROI isn’t theoretical. It shows up in your sprint velocity and your support queue.

How We’re Helping Teams Build This Capability

At The Coders Guild, we’ve been running the Level 4 Software Tester apprenticeship for years now. And the teams that get the most out of it are the ones who treat it as capability building, not just hiring.

We don’t just teach people how to find bugs. We teach them how to think like engineers. How to work in an Agile team. How to communicate issues in a way that helps developers fix them faster. How to use modern tooling without getting lost in the complexity.

And because it’s an apprenticeship, they’re learning whilst they’re working. They’re applying what they learn to your actual product. They’re building institutional knowledge from day one.

The government covers 95% of the cost for SMEs. Levy transfer can make it cost-neutral. And the retention rates speak for themselves.

Stop Searching, Start Building

The QA skills gap isn’t going to close itself. 27% of all vacancies in 2024 were skill-shortage vacancies. That number’s not shrinking.

You can keep competing for the same small pool of senior talent. Or you can build the capability you actually need.

Hire an apprentice and train them properly. Or upskill someone already on your team who’s showing the right instincts

Either way, you’ll end up with someone who understands your product, your users, and your business logic better than any external hire ever could.

And you’ll have built a QA function that actually works.