Hiring and Sponsoring IT quality and testing professionals (SOC Code 2136)

SOC 2136 covers IT quality assurance and testing professionals who design test strategies, build automated test frameworks and own software quality outcomes — a professional-level role that goes beyond running manual test scripts against a checklist.

‍

Manual tester versus test professional

‍

This is one of the sharper eligibility lines in the IT occupation group. A tester who executes pre-written test cases with no input into test design, automation or quality strategy is unlikely to meet the RQF6 skill level 2136 sits at. What supports the classification is evidence the person designs test plans, builds or maintains automated test suites, defines acceptance criteria with development teams, and reports on quality risk — not just logs bugs into a tracker. Write the CoS job description around these responsibilities specifically, since a generic 'tester' description invites the wrong assumption.

‍

Evidence that carries weight for this code

‍

Beyond the job description, the strongest evidence for 2136 tends to be concrete artefacts rather than general statements about experience: automated test suites the person has built in tools like Selenium, Cypress or Playwright, performance or load-testing work in tools such as JMeter, a test strategy or test plan document with their name on it, defect and coverage metrics they've reported to stakeholders, and involvement in defining acceptance criteria alongside developers or product owners during sprint planning. A CV that lists testing tools without any evidence of design or ownership work is weaker support than a portfolio, however informal, showing what the person actually built and decided. In regulated sectors such as finance, healthcare or insurance, quality professionals may also own test data management — ensuring test environments run on anonymised or synthetic data rather than live customer records — and that kind of responsibility is a further, sector-specific sign of professional-level ownership rather than routine test execution.

‍

Salary and going rate for this code

‍

Sponsorship requires pay to meet the higher of the general Skilled Worker salary floor and the SOC 2136 going rate — check both figures against the going rates guide and the salary floor guidance, since testing roles are sometimes priced closer to technician-level pay in the wider market even when the sponsored role needs to meet a professional-level threshold.

‍

Where quality leadership crosses into a different code

‍

As testers become QA leads or test managers with responsibility for a whole team's quality function, budget for testing tools, or input into hiring, the role can start to look less like SOC 2136 and more like an IT management occupation. There's no fixed rule for exactly where that line falls, but if the person spends most of their time managing people and quality process rather than personally designing tests and automation, it's worth checking whether a management-level code is the better fit before defaulting to 2136 out of habit.

‍

Misclassifying a testing role has consequences beyond an awkward audit conversation. If the going rate for the correct code turns out to be higher than what's being paid, the sponsor may need to backdate a pay correction or risk the CoS being treated as non-compliant — and a pattern of underpaying sponsored testers against the wrong benchmark is the kind of finding that can affect a sponsor's compliance rating rather than being written off as a one-off clerical error.

‍

Outsourced and offshore testing: the genuine vacancy question

‍

Software testing is one of the most commonly outsourced or offshored functions in the industry, and that history can work against a sponsorship case if it isn't addressed directly. If a business has historically run testing through an offshore team or a third-party test house, be ready to explain why this particular role needs to sit in the UK and be filled by this specific sponsored hire — proximity to the development team, regulatory or data-residency requirements, or a shift in delivery model are all genuine reasons, but they need to be stated rather than assumed. This is exactly the kind of question a mock audit exercise will surface before a real one does.

‍

Records worth keeping from day one

‍

Appendix D record-keeping duties require sponsors to retain the evidence used to justify the role and the recruitment decision. For a quality/testing hire, that means keeping the test-strategy job description, any technical assessment used during hiring, and evidence of the person's actual test-design work once in post — store it centrally through secure document management rather than relying on individual managers' inboxes.

‍

Keeping track of reporting deadlines

‍

Sponsor duties include reporting relevant changes within set timeframes through the Sponsorship Management System. Missing a reporting deadline is an easy, avoidable compliance failure — smart alerts and reminders can flag CoS reporting windows and renewal dates before they're missed. Full obligations are set out in the official record-keeping guidance.

‍

FAQs

‍

Can a QA engineer with a computer science degree but no automation experience qualify under 2136?

‍

A degree helps but isn't the deciding factor — what matters is whether the day-to-day duties involve test design and quality ownership, not just the candidate's academic background.

‍

Does 2136 cover security testing and penetration testing roles?

‍

It can, where the role is genuinely about designing and executing quality/security test strategy — but check whether a more specific occupation code fits better before defaulting to 2136.

‍

Is an automation-only tester with no manual testing background still eligible?

‍

Yes, in principle — automation-first testing is a legitimate and increasingly common specialism, and building or owning an automated test framework is itself strong evidence of professional-level work, regardless of how much manual testing the person has also done.