The Coders Guild offered clear and practical insights into generative AI, which we’ve started applying in our business. The course was well-structured and relevant to our needs, making the learning process straightforward and effective.
The Coders Guild led the research and development that produced the UK’s first Level 4 AI and Automation apprenticeship standard — built with Skills England and the Alan Turing Institute after a year of research into what SMEs actually need from AI training. We’re not reselling someone else’s framework. We designed it, and we’re running the first cohorts now.
Our trainers work in the field. Every programme is delivered by industry practitioners — people using these tools in real businesses, not academics teaching from a curriculum. That means what gets taught reflects how AI and automation work in practice, not how they looked two years ago.
Built for smaller businesses. Most AI training is designed with enterprise budgets and infrastructure in mind. Ours isn’t. Everything we do is built around the constraints and opportunities of SMEs — businesses where one capable person can genuinely change how the whole organisation works.
Pick the one that matches where you are. If it’s not obvious, tell us what you’re working with and we’ll point you right.
Spend, policy, risk, who on the team needs what. AI for Leaders is six weeks that take you from using the tools to leading the doing.
Grow your own AI capability with fully funded, hands-on training. Your people learn on real work in your business, on the UK’s Level 4 AI and Automation apprenticeship, the standard we created with Skills England.
Closed cohorts on your dates, up to twelve people, built around how your business actually works. One conversation tells you what fits.
Want to go deep yourself? Our courses run from Foundations through Intermediate to Advanced. See them all below.
“Businesses need outputs, not certifications. That’s why our training returns value fast: people do the work on your business, instead of watching videos and hoping some of it sticks.”
Crispin Read – who led the R&D on the UK’s new Level 4 AI and Automation standard with Skills England
Every business is different. If you’re unsure which option works best, or you need something more tailored to your specific challenges, fill in the form and we’ll send you some options and arrange a call.
"*" indicates required fields
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Software testing ensures applications work reliably, meet requirements, and provide good user experiences. That’s always been true. What’s changed is what testers are expected to work with – AI-based systems, ML models, and automated pipelines that need a different kind of thinking to test well. Whether you’re doing manual testing, writing automated tests, or testing AI systems themselves, the fundamentals of good testing matter more than ever.
Every business is different. If you’re unsure which option works best, or you need something more tailored to your specific challenges, fill in the form and we’ll send you some options and arrange a call.
"*" indicates required fields
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
You can start in testing without coding skills, but you’ll need to develop some technical capability for career progression:
Entry-level manual testing: No coding required initially. You can learn testing fundamentals, execute tests, and document bugs without programming.
However, coding becomes important because:
What you actually need:
Think of coding as something you’ll develop over time, not something you need day one. Many successful test automation engineers started with zero coding knowledge and learned through practical application.
Languages used in testing: Python, JavaScript, Java, C# are most common. Python is good starting point for beginners.
The terms are often used interchangeably, but technically they’re different:
Software Testing: The activity of executing software to find bugs. Testing checks whether software works correctly by running it and comparing actual behaviour to expected behaviour.
Quality Assurance (QA): Broader concept covering all activities that ensure quality. QA includes testing but also covers processes, standards, reviews, prevention activities, and quality culture.
In practice:
Quality Engineering: Newer term emphasising engineering approaches to quality – automation, continuous testing, metrics, quality infrastructure. Quality engineers are more technical than traditional testers.
Don’t worry too much about terminology. Read job descriptions to understand what role actually involves rather than focusing on whether it’s called QA, testing, or quality engineering.
Manual testing isn’t dying but it is evolving:
What’s declining:
What remains valuable:
The future is combination:
Career advice:
Pure manual testing without technical skills provides limited career progression. Combining exploratory testing skills with automation capability creates strong career foundation.
The “best” tool depends on context, but here’s practical guidance:
For web automation, start with Selenium WebDriver:
Consider Cypress or Playwright if:
For API testing:
For mobile:
Practical approach:
Most important is learning automation thinking – how to write maintainable tests, design frameworks, handle waits and synchronisation, debug failures. These concepts transfer across tools.
Yes. Testing is one of the most accessible tech careers without degree requirements:
Why degrees matter less in testing:
What matters more than degrees:
Getting started without degree:
Reality check:
Many testers successfully built careers without degrees by demonstrating capability through certifications, portfolio work, and practical experience. Focus on building demonstrable skills rather than worrying about lack of degree.
The tester-developer relationship is crucial for effective quality:
Traditional (problematic) model:
Modern collaborative model:
Good working relationships involve:
In Agile teams:
Best tester-developer relationships feel like partnership working toward shared goal of quality software, not adversarial relationship of QA police versus developers.
Testing can be long-term career or stepping stone to other roles:
Progression within testing:
Adjacent career moves:
Specialisation paths:
Common progressions:
What helps progression:
Testing provides solid foundation in software development and quality. How far you progress depends largely on technical skills you develop and direction you choose to take. Many successful developers, DevOps engineers, and product managers started in testing.
Software testing is the practice of systematically checking whether software works as intended, identifying bugs before users encounter them, and ensuring quality throughout development. Testing exists to reduce risk – the risk that software doesn’t do what it should, breaks under certain conditions, or creates poor user experiences.
Manual testing involves human testers exploring applications, executing test cases, and identifying issues through hands-on interaction. Manual testers think like users, try unexpected paths, and catch issues automated tests might miss. They document bugs, verify fixes, and ensure new features work across different devices, browsers, and scenarios.
Test automation involves writing code that checks software automatically. Automated tests run repeatedly without human intervention, catching regressions quickly and enabling continuous deployment. Test automation engineers write test scripts, maintain test frameworks, and build infrastructure that lets teams ship confidently and quickly.
Quality assurance (QA) takes broader view than just finding bugs. QA engineers think about quality throughout development lifecycle – reviewing requirements, identifying risks, defining test strategies, and helping teams build quality in rather than testing it in afterwards. Modern QA is less about gatekeeping and more about enabling teams to deliver quality software quickly.
Testing work varies significantly by organisation and methodology. Traditional testing often happens after development, with dedicated test phases and formal test plans. Agile testing happens continuously alongside development, with testers embedded in development teams. DevOps and continuous delivery require extensive test automation to enable rapid, safe deployments.
The field is evolving from purely manual testing toward more technical roles. While manual testing skills remain valuable, most testing careers now require some technical capability – understanding APIs, writing basic scripts, working with test automation tools, or understanding development processes. Pure manual testing roles are declining while technical testing roles grow.
AI adds a new layer to this. Testing AI-based systems requires understanding how ML models behave, where they fail unpredictably, and how to design tests for systems that don’t always produce the same output twice. At the same time, AI tools are changing how testers work – generating test cases, identifying edge cases, and automating repetitive test execution. Testers who understand both sides of that are increasingly valuable.
Testing combines several skills. Analytical thinking helps identify what could go wrong and design tests that expose problems. Attention to detail catches subtle bugs others might miss. Communication skills are essential for documenting bugs clearly and working with developers. Understanding users helps test in ways that matter. Technical skills enable automation and working effectively with development teams.
Testing work exists across every sector. Any organisation building software needs testing capability. Financial services need rigorous testing for regulatory compliance and risk management. Healthcare requires testing for safety-critical applications. E-commerce needs testing for reliability under load. Government digital services need accessibility testing. Games need testing across platforms and devices.
Here it is with full formatting:
Software testing requires combining analytical thinking, technical skills, and quality mindset:
Testing Fundamentals
Test design: Creating tests that efficiently expose bugs. Understanding equivalence partitioning, boundary value analysis, decision tables, state transition testing. Designing test cases that provide good coverage without being redundant.
Defect identification: Recognising when software isn’t working correctly. Understanding difference between bugs, design issues, and expected behaviour. Knowing what’s worth reporting and what isn’t.
Bug reporting: Documenting bugs clearly so developers can reproduce and fix them. Writing good bug reports with clear steps to reproduce, expected versus actual behaviour, screenshots or videos, environment details.
Test coverage: Understanding what you’ve tested and what you haven’t. Identifying gaps in testing. Balancing comprehensive testing with time constraints.
Risk-based testing: Prioritising testing effort on highest-risk areas. Understanding what matters most and focusing testing there.
Manual Testing Skills
Exploratory testing: Systematically exploring applications without detailed scripts. Thinking creatively about what could go wrong. Following interesting paths and investigating suspicious behaviour.
Test execution: Following test cases accurately, documenting results, identifying and investigating failures, retesting after fixes.
Regression testing: Verifying that existing functionality still works after changes. Understanding what areas might be affected by changes.
User acceptance testing (UAT): Testing from user perspective. Verifying software meets business requirements and user needs.
Cross-browser and cross-device testing: Testing applications work across different browsers, devices, screen sizes, and operating systems.
Test Automation
Programming for test automation: Writing test scripts in languages like Python, JavaScript, Java, or C#. Understanding programming fundamentals well enough to write maintainable test code.
Selenium WebDriver: Most common tool for browser automation. Writing scripts that interact with web applications, locate elements, perform actions, verify results.
Cypress or Playwright: Modern alternatives to Selenium. Understanding when to use which tool and their trade-offs.
API testing: Testing APIs directly rather than through user interface. Using tools like Postman, REST Assured, or writing API tests in code. Understanding REST APIs, HTTP methods, status codes, JSON.
Test frameworks: Using frameworks like JUnit, pytest, TestNG, or Jest. Understanding test structure, assertions, setup and teardown, test organisation.
Page Object Model: Design pattern for maintainable UI test automation. Separating test logic from page details, making tests easier to maintain when UI changes.
Testing AI & ML Systems
Testing AI-based systems requires a different approach to traditional software testing. Unlike deterministic systems that produce the same output for the same input, AI models are probabilistic – results vary, and “correct” isn’t always black and white.
Understanding how ML models are trained, evaluated and deployed: Knowing enough about the model lifecycle to design meaningful tests around it.
Designing tests for non-deterministic outputs: Testing for acceptable ranges and behaviours rather than exact expected results.
Prompt engineering and testing LLM-based applications: Understanding how prompts affect outputs and how to test applications built on large language models.
Identifying bias and fairness issues in model outputs: Recognising when a model is behaving in ways that are technically functional but practically problematic.
Data quality testing and validation: Ensuring the data going into AI systems is clean, representative and fit for purpose.
Testing agentic AI systems: Testing systems that take autonomous actions requires understanding failure modes that don’t exist in traditional software.
Testing Types & Techniques
Functional testing: Verifying features work as specified. Testing positive and negative scenarios, edge cases, error handling.
Integration testing: Testing how components work together. Verifying data flows correctly between systems, APIs integrate properly, services communicate correctly.
Performance testing: Testing how applications perform under load. Understanding response times, throughput, resource usage. Using tools like JMeter, Gatling, or k6.
Security testing: Identifying security vulnerabilities. Understanding common vulnerabilities (SQL injection, XSS, authentication issues). Basic penetration testing concepts.
Accessibility testing: Ensuring applications work for users with disabilities. Testing with screen readers, keyboard navigation, colour contrast. Understanding WCAG standards.
Mobile testing: Testing mobile applications on iOS and Android. Understanding mobile-specific concerns – different screen sizes, orientations, gestures, network conditions.
Test Infrastructure & CI/CD
Continuous integration: Understanding how automated tests run in CI/CD pipelines. Working with Jenkins, GitHub Actions, GitLab CI, or CircleCI.
Test environments: Understanding different test environments (dev, test, staging, production). Managing test data, understanding environment differences.
Docker basics: Understanding containers for consistent test environments. Running applications and tests in containers.
Version control: Using Git for test code. Branching, committing, pull requests, code review.
Agile & Collaboration
Working in Agile teams: Testing within sprints, participating in planning and standups, collaborating with developers, understanding definition of done.
Shift-left testing: Testing earlier in development cycle. Reviewing requirements, identifying testability issues, preventing bugs rather than just finding them.
Behaviour-driven development (BDD): Writing tests in business language using tools like Cucumber. Understanding Gherkin syntax, writing feature files, connecting to test automation.
Test-driven development (TDD) awareness: Understanding how developers write tests before code. Collaborating on unit test strategy.
Tools You’ll Use
Test management: Jira, TestRail, Zephyr, or similar tools for managing test cases, test runs, and tracking bugs.
Browser automation: Selenium WebDriver, Cypress, Playwright, or Puppeteer for automated UI testing.
API testing: Postman, Insomnia, REST Assured, or requests library for Python.
Performance testing: JMeter, Gatling, Locust, or k6 for load testing.
Mobile testing: Appium for mobile automation, BrowserStack or Sauce Labs for device cloud testing.
Accessibility testing: WAVE, aXe, screen readers (NVDA, JAWS, VoiceOver).
Browser DevTools: Chrome DevTools, Firefox Developer Tools for investigating issues, understanding network requests, debugging.
Virtual machines and emulators: VirtualBox for testing different operating systems, Android Studio emulators, Xcode Simulator.
AI-assisted testing tools: GitHub Copilot for test code generation, AI-powered test case generators, LLM-based exploratory testing assistants, tools like Testim or Mabl that use AI for test maintenance and intelligent test execution.
Technical Knowledge
How web applications work: Understanding client-server architecture, HTTP requests and responses, how browsers render pages, cookies and sessions.
Databases basics: Writing simple SQL queries to verify data, understand data flows, set up test data.
APIs and web services: Understanding REST APIs, JSON and XML, authentication mechanisms, API testing approaches.
HTML, CSS, JavaScript basics: Reading HTML to locate elements, understanding CSS selectors, basic JavaScript for browser automation.
Command line: Comfortable using terminal or command prompt for running tests, managing files, using development tools.
Quality Engineering Mindset
Prevention over detection: Thinking about how to prevent bugs rather than just finding them. Improving processes, tools, and practices to reduce defects.
Testing strategy: Deciding what to test, how to test it, what level of testing (unit, integration, E2E), balancing manual and automated testing.
Metrics and measurement: Understanding test coverage, defect density, test effectiveness. Using metrics to improve quality, not just report it.
Risk awareness: Understanding business impact of different bugs. Prioritising testing effort appropriately.
Soft Skills
Analytical thinking: Breaking down complex systems, identifying what could go wrong, designing tests that expose problems.
Attention to detail: Noticing subtle issues, inconsistencies, edge cases others might miss.
Communication: Writing clear bug reports, explaining technical issues to non-technical stakeholders, advocating for quality.
Collaboration: Working effectively with developers, product managers, designers. Building relationships, not being adversarial.
Curiosity: Wanting to understand how things work, what could break them, how users will interact with them.
Persistence: Investigating difficult bugs, not giving up when issues are hard to reproduce, following problems through to resolution.
Testing careers offer progression from manual testing through technical testing and quality engineering to leadership roles:
Junior Tester / QA Tester: Executing test cases, documenting bugs, learning testing fundamentals, working under supervision. Typically manual testing focused. Salary: £20,000 – £28,000.
Entry roles involve learning how to test systematically, write clear bug reports, use test management tools, and understand quality mindset. You’ll execute tests designed by others initially, gradually taking on more test design.
Test Analyst: Similar to junior tester but with more analytical focus. Designing test cases, analysing requirements, identifying test scenarios. Salary: £22,000 – £30,000.
Software Tester / QA Engineer: Independently designing and executing tests, owning quality for features or components, writing some automated tests, mentoring junior testers. Salary: £28,000 – £45,000.
At this level you’re trusted to test features independently, make decisions about test approach, and balance manual and automated testing appropriately.
Test Automation Engineer: Specialising in test automation. Writing automated test scripts, maintaining test frameworks, building test infrastructure. Requires stronger programming skills than general testing roles. Salary: £32,000 – £50,000.
Automation engineers spend most time writing and maintaining test code. You’re more software engineer than traditional tester, but focused on quality and testing concerns.
Performance Test Engineer: Specialising in performance and load testing. Designing performance tests, analysing results, identifying bottlenecks, working with developers on optimisation. Salary: £32,000 – £50,000.
Security Test Engineer: Specialising in security testing. Identifying vulnerabilities, penetration testing, security scanning, working with security teams. Salary: £35,000 – £52,000.
Senior Test Engineer / Senior QA Engineer: Leading testing for complex features or systems, defining test strategy, mentoring other testers, improving testing processes. Salary: £42,000 – £65,000.
Test Architect / Automation Architect: Designing test frameworks and infrastructure, setting automation standards, making technology decisions for testing. Salary: £50,000 – £75,000.
SDET (Software Development Engineer in Test): Hybrid developer/tester role. Building testing tools and infrastructure, working on testability of systems, strong programming skills. Common in tech companies. Salary: £45,000 – £70,000.
Quality Engineer / Quality Assurance Engineer: Focus on quality throughout development process, not just testing. Working on preventing defects, improving development practices, building quality culture. Salary: £40,000 – £65,000.
Test Manager / QA Manager: Managing testing team, defining test strategy, allocating resources, reporting on quality, coordinating testing across projects. Salary: £50,000 – £75,000.
Head of QA / QA Director: Leading QA function, setting quality strategy, building testing capability, influencing organisational approach to quality. Salary: £65,000 – £95,000.
VP of Quality / VP of Engineering (Quality): Executive responsibility for quality across organisation. Strategic quality leadership, building quality culture. Salary: £80,000 – £120,000+.
Testing skills transfer to several adjacent areas:
DevOps/Site Reliability Engineering: Testing background helps with monitoring, reliability, and quality of infrastructure and deployments.
Development: Many testers transition to development roles, bringing quality mindset and understanding of testing to development work.
Product Management: Testing experience provides deep understanding of how products work, user scenarios, and quality concerns.
Business Analysis: Testing teaches requirements analysis, edge case thinking, and systematic problem breakdown.
Consulting: Experienced testers become test consultants, helping organisations improve testing practices.
Testing field is shifting toward more technical roles. Pure manual testing positions are declining while technical testing and quality engineering grow. Career progression increasingly requires developing technical skills – programming, automation, understanding CI/CD, working with APIs.
This doesn’t mean manual testing skills aren’t valuable – exploratory testing, usability thinking, and understanding user scenarios remain crucial. But combining these with technical capabilities creates more career opportunities and higher compensation.
Testing suits people who combine analytical thinking with attention to detail and enjoy finding and solving problems.
Analytical mindset: Testing requires thinking systematically about what could go wrong, how users might interact with software, and what scenarios need checking. If you enjoy breaking down complex problems, testing is engaging.
Attention to detail: Catching subtle bugs, noticing inconsistencies, and spotting edge cases requires careful observation. You can’t be detail-oriented sometimes – it needs to be consistent.
Curiosity about how things work: Good testers want to understand how systems work, why they might break, and what happens under different conditions. Natural curiosity drives better testing.
User empathy: Understanding how real users interact with software, what frustrates them, and what matters most to them helps focus testing on what actually matters.
Comfortable with technology: You don’t need to be a programmer initially, but you need comfort learning technical tools, understanding how software works, and developing technical skills over time.
Communication skills: Testing involves constant communication – writing bug reports, explaining issues, advocating for quality, working with developers. Clear communication is essential.
Complete career changers: Many successful testers came from completely different fields. Customer service, retail, teaching, administration – diverse backgrounds often bring valuable perspectives on how users think.
Computer science or IT backgrounds: Technical education provides foundation, though many testers succeed without degrees.
Support or helpdesk experience: People who’ve helped users troubleshoot problems often have good instincts for what goes wrong and how users experience issues.
Domain expertise: Healthcare, finance, retail, or other domain knowledge combined with learning testing skills creates valuable specialisation.
People who genuinely enjoy finding problems and helping fix them. Those who can balance being thorough with being pragmatic – knowing when to keep digging versus when to move on. Individuals who communicate issues constructively rather than just criticising. People who see testing as enabling quality, not gatekeeping.
Successful testers aren’t adversarial with developers – they’re collaborators working toward shared goal of quality software. They advocate for users and quality without being dogmatic or inflexible.
Age and background don’t matter. Testing values careful thinking, systematic approach, and communication skills – often developed through diverse life and work experience. Many successful testers started mid-career or later.
Never finding everything: No matter how thoroughly you test, some bugs slip through. You can’t test everything. Learning what to focus on and accepting some uncertainty is necessary.
Being bearer of bad news: Testers often report problems and delays. Telling people their work has issues, especially repeatedly, can be emotionally draining.
Repetitive aspects: Some testing work, especially regression testing, can be repetitive. Though automation helps with this.
Time pressure: Often testing is squeezed at end of development cycles. Pressure to sign off on quality when you haven’t tested enough is stressful.
Undervaluation: Some organisations don’t value testing properly, seeing it as cost rather than investment. Working where quality isn’t prioritised is frustrating.
Technical skill requirements increasing: Testing roles increasingly require programming and technical skills. If you don’t want to develop technical capabilities, career options narrow.
Finding important bugs: Catching critical bugs before users experience them provides genuine satisfaction. You’ve protected users and the business from problems.
Improving quality: Seeing software quality improve through better testing, automation, or process changes. Your work makes products better.
Variety: Testing different features, using different techniques, working across different areas of applications. Most days involve varied work.
Problem-solving: Investigating difficult bugs, figuring out reproduction steps, understanding root causes. Testing provides intellectual challenge.
Impact: Quality affects user experience, business success, and team morale. Good testing has tangible impact.
Continuous learning: New tools, techniques, technologies, and domains to learn. Testing provides endless learning opportunities.
AI adds another layer to this shift. Testers who understand how to test AI-based systems – and how to use AI tools in their own workflow – are becoming some of the most sought-after people in quality engineering. It’s not a separate specialism yet, but it’s moving that way fast. If you’re coming into testing now, building that understanding early puts you ahead of most people already in the field.
Software testing is one of the most accessible tech careers. You can start learning immediately without expensive tools or extensive programming knowledge:
Start testing websites and apps you use:
This builds observational skills and testing mindset. You’re already testing – just do it more deliberately and systematically.
Learn testing fundamentals:
Get familiar with test tools:
Testing portfolios demonstrate capability to potential employers:
Document testing you’ve done:
Contribute to open source:
Create test case examples:
While you can start with manual testing, developing technical skills opens more opportunities:
Learn programming basics:
Learn test automation fundamentals:
Understand APIs:
Learn version control:
Testing certifications aren’t required but can help early in career:
ISTQB Foundation Level:
Other certifications:
Certifications help but don’t replace practical skills and experience. Employers value demonstrable capability over certificates alone.
Experience is most important factor in hiring:
Volunteer testing work:
Crowdsourced testing platforms:
Internships or junior positions:
Apprenticeships: Software testing apprenticeships provide structured learning while working in real testing roles. You’re paid, gain hands-on experience, and earn a qualification. Duration: 15-18 months. Government-funded for qualifying employers.
Apprenticeships suit people who need income while learning or who learn better through practical application than academic study.
Bootcamps: Testing bootcamps teach practical skills intensively. Some government-funded options. Duration: 8-12 weeks.
Online courses: Many free or low-cost testing courses from Test Automation University, Udemy, Coursera.
University degrees: Computer science or software engineering degrees provide foundation but aren’t essential for testing careers.
Entry-level testing positions exist but are competitive:
Target smaller organisations: SMEs and startups often hire junior testers and provide broad learning opportunities. You’ll test across different areas rather than specialising immediately.
Look for manual testing roles: Start with manual testing positions to get foot in door, then develop automation skills.
Emphasise analytical skills: Highlight problem-solving, attention to detail, and systematic thinking from any previous work.
Show you’ve self-studied: Portfolio projects, certifications, and online courses demonstrate commitment and initiative.
Be willing to start junior: First role might be lower salary or level than you’d like. Use it to gain experience and progress quickly.
Network: Join testing communities – Ministry of Testing has local meetups, online forums, and conferences. Many roles filled through connections.
Consider adjacent roles: Support analyst, data quality analyst, or QA analyst roles might be easier entry points than pure testing roles.
The Coders Guild offers software testing apprenticeships covering manual testing, test automation, quality assurance, and testing in Agile environments. Training is practical, includes real testing work, and is taught by working test professionals.
Government funding is available for apprenticeships and qualifying programmes. Browse our software testing courses below or get in touch to discuss which route might work for you.
Junior Tester / QA Tester: £20,000 – £28,000 for entry-level manual testing roles.
Software Tester / QA Engineer: £28,000 – £45,000 for mid-level testers with some experience and potentially some automation skills.
Test Automation Engineer: £32,000 – £50,000 for automation specialists. Higher than equivalent manual testing roles due to technical requirements.
Senior Test Engineer / Senior QA Engineer: £42,000 – £65,000 for experienced testers leading testing efforts and mentoring others.
Test Architect / SDET: £50,000 – £75,000 for technical testing specialists designing frameworks and infrastructure.
Performance/Security Test Specialist: £35,000 – £60,000 depending on experience. Specialists often earn more than generalists.
Test Manager / QA Manager: £50,000 – £75,000 for managing testing teams and setting strategy.
Head of QA / QA Director: £65,000 – £95,000 for leading quality function in organisations.
Salaries vary significantly by location and sector. London pays 20-30% more than other regions. Financial services, technology companies, and consulting typically pay more than retail, public sector, or smaller organisations.
Technical testing roles (automation, SDET, performance) generally pay more than pure manual testing roles. The gap widens with experience.
Testing job market is mixed – some areas growing, others declining:
Growing demand:
Declining demand:
Reality check: Entry-level manual testing roles are competitive. Many people see testing as entry into tech, creating oversupply at junior manual testing level. However, technical testing roles have more demand than supply.
Testing work is generally remote-friendly:
Remote works well for:
Some in-person benefit:
Many testing roles are now remote or hybrid. Testing was one of first functions to successfully adopt remote work widely.
Testing contracting is common:
Test contractors: £250-£500 per day depending on experience and specialisation. Manual testers at lower end, automation specialists and SDETs at higher end.
Test automation contractors: £350-£600 per day for automation engineers with proven capability.
Test consultants: £400-£700+ per day for experienced consultants helping organisations improve testing practices and strategy.
Contracting typically requires several years of permanent experience first. Clients want people who can deliver independently and quickly.
Testing careers offer reasonable progression for people who develop technical skills:
Technical skills drive compensation: Testers who develop programming, automation, and quality engineering skills earn significantly more than those who remain in manual testing.
Specialisation pays: Performance testing, security testing, or domain expertise (financial testing, healthcare testing) commands premium salaries.
Leadership progression: Moving into test management or quality leadership increases compensation but caps lower than development or product leadership.
Adjacent moves often better compensated: Transitioning from testing to development, DevOps, or product management often provides better long-term compensation than pure testing careers.
Senior technical testers can reach £70,000-£90,000. QA Directors can reach £100,000+ at large organisations. However, equivalent development or DevOps roles often reach these levels faster.
Testing job security depends on skills:
More secure: Technical testing skills – automation, performance, security, quality engineering integrated with development.
Less secure: Pure manual testing without technical skills increasingly vulnerable to automation and offshore competition.
Overall, testing remains necessary – software needs quality assurance. But the nature of testing work is changing. Adapting to more technical, quality engineering approach provides better long-term security than clinging to traditional manual testing.
If you’ve got an event, collaboration or success story we should know about – get in touch.
FREE AI WEBINARS
Two short, practical AI sessions a month. Free. Drop your email and we’ll send you the link, plus the recordings of the ones you’ve missed.
"*" indicates required fields
