Manual Tester Salary in UK (2026)

TL;DR

A credible 2026 regional benchmark places permanent manual QA at GBP 28,000 to 35,000 for junior, GBP 35,000 to 50,000 for mid-level, and GBP 50,000 to 70,000 for senior roles. London and lead roles can be higher, but match responsibilities, region, and complete benefits before choosing a target.

Key Takeaways

• A 2026 South West salary guide places manual QA at GBP 28,000 to 35,000 junior, GBP 35,000 to 50,000 mid-level, and GBP 50,000 to 70,000 senior.
• London benchmarks are often higher, but housing, commute, office frequency, and employer pay zones affect the real value.
• Compare base salary first, then employer pension, bonus, leave, health benefits, on-call duties, overtime, and remote terms.
• Contract day rates cannot be converted to salary without accounting for unpaid time, employer costs, employment status, and assignment risk.
• API investigation, SQL, accessibility, mobile coverage, domain expertise, and strong exploratory testing improve a manual tester's market scope.
• Use the budgeted band and role evidence to negotiate, rather than treating a national table as a guaranteed personal rate.

Manual Tester salary UK research in 2026 has a useful evidence base: one current regional guide lists GBP 28,000 to 35,000 for junior manual QA, GBP 35,000 to 50,000 for mid-level, and GBP 50,000 to 70,000 for senior roles. A separate recruiter guide places manual testers around GBP 35,000 junior, GBP 45,000 mid-level, and GBP 55,000 or more senior outside London, with higher London reference points.

Those figures are directional, not guaranteed. Job titles mix scripted execution, exploratory testing, UAT, API investigation, regulated evidence, and leadership. This guide shows how to match the data to the vacancy and compare permanent salary, benefits, location, and contract work without false precision.

TL;DR

Use annual gross base salary as the first comparison. Add pension, bonus, leave, health cover, working pattern, and other benefits in separate rows.

1. Manual Tester salary UK benchmarks for 2026

The ADLIB 2026 Digital Technology salary guide provides unusually clear experience bands for Tester/QA (Manual). It lists GBP 28,000 to 35,000 for 0 to 2 years, GBP 35,000 to 50,000 for 2 to 4 years, GBP 50,000 to 70,000 for 4 to 6 years, GBP 70,000 to 90,000 for lead roles at 6 to 10 years, and GBP 90,000 to 110,000 for head-level work. The guide is labelled for the South West, so do not present it as a national official scale.

The Adria Solutions 2026 salary guide reports manual tester or QA tester reference points outside London at GBP 35,000 junior, GBP 45,000 mid-level, and GBP 55,000 or more senior. Its London table shows GBP 40,000, GBP 50,000, and GBP 60,000 or more. Adria says the figures come from its own data and industry insight.

The overlap is more valuable than an artificial average. Both sources place established hands-on manual QA broadly from the mid GBP 30,000s through the GBP 50,000s, with senior and London observations extending upward. Your target still requires comparable scope, sector, region, and level.

Record the guide date and method. A 2026 publication can reflect placements or observations gathered earlier.

2. Manual Tester salary UK by experience and responsibility

The ADLIB table uses experience brackets, but years should be treated as a sorting aid. Employers pay for the work you can own. A junior tester may execute reviewed cases, learn the product model, raise reproducible defects, and retest fixes. A mid-level tester may design coverage, run exploratory sessions, query data, inspect API traffic, and advise on release risk. A senior specialist may handle complex integrations, coach others, improve requirements, and coordinate quality across teams.

A candidate with six years of repetitive test-script execution does not automatically meet a senior engineering band. A four-year tester who independently investigates payments across browser, service, database, and reconciliation may have stronger evidence. Likewise, a lead salary does not apply merely because you coordinated one release.

Read the job description for decision authority. Who defines strategy, owns environments, speaks to stakeholders, manages people, and signs off risk? Use that scope, not the most generous title found online.

3. Gross salary, take-home pay, and the benefits package

UK job adverts generally state annual gross base salary before Income Tax, employee National Insurance, pension contributions, student-loan deductions, and other individual adjustments. Take-home pay changes with current tax rules, tax code, pension choice, benefits, and personal facts. Use current official guidance or a reputable calculator for an estimate, and seek qualified advice when the decision is material.

Separate compensation into categories:

1. Guaranteed base salary.
2. Conditional cash, such as annual bonus, on-call pay, or overtime.
3. Employer pension contribution.
4. Benefits, including health cover, life insurance, leave, training, and travel support.
5. Equity or long-term incentives.

An employer contribution described as 8 percent may depend on your own contribution or qualifying earnings. Ask what pay definition applies, whether salary sacrifice is available, when enrolment begins, and whether contributions exceed the statutory minimum. Read the scheme documents rather than converting a headline percentage directly to cash.

Bonus also needs conditions. Check target and maximum, individual and company measures, payment history, joining-year proration, and whether you must remain employed on the payment date. Compare base with base first. A maximum bonus is not guaranteed salary.

4. London, South East, regional hubs, and remote pay

The Adria guide shows London manual QA reference points approximately GBP 5,000 above its outside-London points at junior, mid, and senior levels. That is one recruiter's view, not a universal London weighting. Large employers may use formal location zones, small companies may use one national band, and remote-first teams may pay by role rather than residence. Ask how the specific company works.

London offers access to finance, commerce, media, consulting, government suppliers, and large technology employers. Cambridge has software and research-intensive companies. Bristol and the South West include digital, aerospace, public-sector, and engineering work. Manchester, Leeds, Edinburgh, Glasgow, Belfast, Birmingham, Newcastle, Reading, and other hubs have distinct sectors and costs. A UK average hides these labour markets.

Model housing, council tax, commute, required office days, childcare, and travel. A higher London salary can still leave less disposable income. Conversely, a particular employer, domain, or network may create career value beyond first-year cash. Score finances and career access separately.

For remote roles, confirm the contractual work location, permitted residence, office attendance, customer travel, equipment, expenses, and whether pay changes after a move. A vacancy marked remote may still require monthly travel or residence within a commuting zone.

5. Permanent employment versus contract testing

A day rate is not an annual salary divided into smaller pieces. Contractors may face unpaid holidays, gaps between assignments, insurance, equipment, accountancy, training, sick time, and early termination. The client may also set working practices and location. Employment status and tax treatment depend on facts and current rules, not only contract wording.

Do not multiply a day rate by 260 and compare that result with a permanent base. Build conservative billable-day scenarios, such as a lower case with gaps and a higher case with stable work. Then deduct the costs and risk that an employer would normally carry. Seek qualified tax and legal advice for inside or outside IR35 questions and business structure. Generic online rules are not a substitute for facts.

Ask about assignment length, notice, extension history, payment terms, timesheet approval, agency margin, expenses, location, equipment, security screening, and professional indemnity requirements. Clarify whether the advertised rate is the worker rate or another figure in the supply chain.

Contracting can provide flexibility, specialist exposure, and higher short-term cash. It also transfers utilisation and benefit risk. Compare it with permanent work only after placing paid leave, pension, bonus, health benefits, training, and job-search gaps on the same model.

6. Sector, domain, and clearance premiums

Manual testing in retail, banking, insurance, health, games, government, transport, telecoms, and enterprise software involves different failure consequences. Banking and payments value authorization, ledger consistency, reconciliation, fraud controls, auditability, and operational resilience. Health settings may add sensitive data, interoperability, clinical workflow, and formal evidence. Public-sector and defence work can add location, citizenship, security clearance, and documentation requirements.

A domain creates market value when it shortens the time to safe ownership. 'Five years in finance' is weaker than explaining how you validated interest calculation boundaries, role permissions, statement generation, and reconciliation without exposing customer data. The same principle applies to insurance claims, rail ticketing, NHS-connected workflows, or commerce refunds.

Security clearance is an eligibility condition and process, not a skill to invent. State current status accurately and verify sponsor requirements. Some cleared roles are on-site because of system constraints. Include commute and flexibility in the package comparison.

Games testing is a separate labour market with distinct project cycles, platforms, and employment patterns. The National Careers Service currently describes computer games tester salaries from GBP 24,000 starter to GBP 36,000 experienced. Do not use a general software QA band for a games role without matching the work.

7. Skills that strengthen a manual QA salary case

Manual quality work is strongest when it reveals information that scripted checks miss. Employers value a tester who can understand user goals, model state, notice contradictions, isolate conditions, and communicate business risk. Technical depth increases the number of places where that tester can gather evidence.

Develop a coherent combination:

• Exploratory testing with charters, session notes, coverage models, and focused debriefs.
• Test design using boundaries, equivalence, decisions, states, pairs, and domain-specific risks.
• HTTP, JSON, authentication, browser developer tools, and API exploration.
• SQL for approved read-only verification of state, relationships, duplicates, and cleanup.
• Accessibility testing across keyboard, semantics, zoom, contrast, errors, and supported assistive technology.
• Mobile risk including permissions, interruptions, connectivity, upgrade, notifications, and device conditions.
• Observability literacy, including logs, correlation identifiers, feature flags, and environment configuration.

The exploratory testing techniques guide helps make human-led investigation visible. Use the API testing fundamentals guide to build technical reach below the UI. Basic automation literacy is valuable, but do not claim automation engineering after copying one tutorial.

A strong specialist may remain primarily manual while improving requirements, risk decisions, and diagnostic speed.

8. Use a runnable offer comparison script

The following JavaScript runs with a current Node.js runtime and uses no external packages. Save it as compare-offers.mjs, replace the illustrative inputs, and run node compare-offers.mjs. It compares guaranteed base, target cash, employer pension contribution, and contracted hours without pretending to calculate tax.

const offers = [
  { name: 'Regional product team', base: 47000, bonusPct: 5, pensionPct: 8, hours: 37.5 },
  { name: 'London consultancy', base: 52000, bonusPct: 8, pensionPct: 4, hours: 40 },
];

for (const offer of offers) {
  const targetBonus = offer.base * offer.bonusPct / 100;
  const employerPension = offer.base * offer.pensionPct / 100;
  const contractHours = offer.hours * 52;

  console.log({
    name: offer.name,
    guaranteedBase: offer.base,
    targetCash: offer.base + targetBonus,
    statedEmployerPension: employerPension,
    basePerContractHour: Number((offer.base / contractHours).toFixed(2)),
  });
}

The pension calculation assumes the contribution applies to full base, which may not match an actual scheme. Change it only after reading the plan. Target cash remains conditional. The hourly figure ignores leave, commute, overtime, learning, stability, and career options. This is a question generator, not a decision engine.

A QA portfolio should include evidence of product reasoning too. Publish a sanitized test strategy, exploratory charter, API investigation, or accessibility review of a practice app. Never upload employer code, internal URLs, credentials, production data, or confidential screenshots.

9. CV, portfolio, and interview evidence

Keep the CV specific. 'Responsible for manual testing' does not show level. A stronger truthful pattern is: 'Modelled subscription renewal and cancellation states across web, payment callback, and account data, identifying a duplicate-charge risk before launch and adding the scenario to release coverage.' The bullet shows scope, method, and outcome.

Use only figures you measured. If you claim a 40 percent regression reduction, be ready to explain the baseline, date range, calculation, and tradeoff. If you cannot share numbers, describe the decision and product result without inventing precision. Preserve official titles and clarify responsibilities in bullets.

A compact portfolio can show a risk map, test charters, high-value cases, two clear defect reports, API requests, SQL queries against local data, and an accessibility note. Add setup instructions and the limits of the exercise. Ten thoughtful artefacts are stronger than 500 generated cases.

Prepare stories for ambiguity, a serious defect, a missed defect, release pressure, disagreement, and process improvement. The manual testing interview questions guide can structure rehearsal. State what you personally observed, decided, and changed.

10. Negotiate a Manual Tester salary UK offer

Use the salary guides as context, then rely on matched openings and the employer's budget. A practical statement is: 'For a mid-level role owning exploratory coverage, API investigation, and release input, I am targeting GBP X to GBP Y base. Could you share the approved band and how pension and bonus are structured?' Replace the placeholders with a realistic range supported by the role.

Ask whether the vacancy spans multiple levels. A broad advertised range may cover junior through senior candidates. Find out what evidence distinguishes placement and what the next level requires. If the company cannot share a band, ask for the budgeted midpoint or confirm whether your target is within scope before investing in a long task.

If base cannot move, discuss employer pension, additional leave, sign-on payment, remote terms, training, private health cover, title accuracy, or a written early review. An early review is meaningful only with a date, criteria, decision owner, and possible adjustment. Check sign-on clawbacks and benefit waiting periods.

Do not justify salary mainly with rent or personal need. Those factors determine acceptance, while level, market, and role value support negotiation. Never invent another offer. Use the QA salary negotiation guide for a complete preparation script.

11. Questions to ask before accepting

A good offer conversation is two-way due diligence. Ask what the tester owns in the first 90 days, who writes automated checks, how developers test, who decides release risk, and how the team handles escaped defects. Ask how much time goes to scripted regression, exploratory testing, UAT support, environment coordination, and production investigation.

Clarify base salary, pay frequency, probation, notice, bonus, pension, leave, sick pay, health cover, life insurance, overtime, on-call, travel, office days, equipment, expenses, and training. Request plan documents for important benefits. If the role supports weekend releases, ask about frequency, compensation, and recovery time.

Understand the manager and operating environment. What does excellent performance look like? Why is the role open? How long have team members stayed? What was the last quality incident and what changed? Answers reveal whether quality is shared or deposited entirely on the tester.

For regulated work, ask about evidence, audit, data access, security checks, and environment restrictions. For a consultancy, ask about client allocation and bench practice. For a startup, ask about runway only when appropriate and examine how equity, workload, and priorities are managed. Put material employment terms in writing.

12. A 90-day UK job-market plan

Days 1 to 30 are for role calibration. Choose a location, work model, industry, and level. Collect 20 to 30 matching vacancies and record salary, scope, source, date, office policy, and repeated skills. Keep manual, automation, lead, and UAT-only roles separate. Compare the ADLIB and Adria guides with this live sample.

Days 31 to 60 are for evidence. Select one repeated gap, such as API testing, accessibility, or SQL. Build a small practice project that shows how the skill improves risk coverage. Write a short README, preserve requests or queries, and explain what remains untested. Update CV bullets so every major keyword is supported by an example.

Days 61 to 90 are for interviews and calibration. Rehearse scenario answers, run a balanced application pipeline, and track each stage. Record recruiter bands and the reason for rejection where supplied. If several roles require automation engineering, decide whether to develop that path or narrow the target. Do not casually rename yourself.

The plan does not guarantee a band or deadline. It improves the quality of the comparison set, evidence, and interview performance. Salary outcomes still depend on hiring demand, location, work authorization, timing, and the employer's approved budget.

Interview Questions and Answers

Q: What Manual Tester salary UK range are you seeking?

Give a gross base range linked to the role's level and scope, then ask about the approved band, pension, and bonus. Do not quote the national maximum when applying for a regional junior role.

Q: How would you test an online bank transfer?

Model authentication, payee creation, limits, confirmation, pending and failed states, duplicate submission, ledger posting, notifications, reversal, and audit history. Place rule and state checks below the UI where possible, while preserving focused user journeys and accessibility.

Q: What do you do when a user story has no acceptance criteria?

Clarify the user outcome, rules, examples, constraints, dependencies, and failure impact. Make assumptions visible and ask targeted questions. Begin reversible exploration around high-risk behavior without silently converting the current implementation into the requirement.

Q: How do you test under a fixed deadline?

Use change and product risk to rank coverage. Protect critical journeys and integration boundaries, run a small trusted regression set, and report untested areas and uncertainty. The release owner then makes an informed decision with visible residual risk.

Q: A developer says your bug is expected behaviour. What next?

Reproduce together and separate observed behavior from the expected rule. Bring the requirement, user impact, request data, logs, and a minimal path. If intent remains unclear, ask the product owner to decide and record the outcome.

Q: When would you automate a manual regression check?

Automate when the check is repeated, valuable, deterministic enough, and has a clear oracle at a reliable interface. Include data, maintenance, runtime, and diagnosis cost. Keep novel exploration and subjective evaluation human-led where that produces better information.

Q: How do you know testing is complete?

Testing is sufficient when agreed exit criteria are met, important risks have credible evidence, blocking defects are resolved or accepted, and residual risk is explicit. A case count alone cannot prove completeness. Time can end testing, but it should not hide uncertainty.

Common Mistakes

• Applying a London figure to every UK vacancy.
• Treating the top of a lead or head band as a senior tester entitlement.
• Comparing target bonus with guaranteed base.
• Ignoring pension basis, weekly hours, office days, overtime, and on-call work.
• Converting a contract day rate to salary using 260 paid days.
• Giving tax or IR35 assumptions without current professional advice.
• Listing API, SQL, accessibility, or automation without supporting evidence.
• Using years alone to claim a level.
• Inventing offers, outcomes, security clearance, or work authorization.
• Relying on verbal remote or early-review promises.

Conclusion

Manual Tester salary UK data in 2026 provides strong planning bands. The ADLIB guide places manual QA from GBP 28,000 to 35,000 junior, GBP 35,000 to 50,000 mid-level, and GBP 50,000 to 70,000 senior in its regional market. Adria's outside-London and London reference points broadly support that progression while showing a location difference.

Use those sources to orient your research, then match live vacancies, compare complete permanent packages, and treat contract work as a separate risk model. A credible salary target comes from role scope, evidence, region, and the employer's band, not from one attractive headline.

Interview Questions and Answers

Frequently Asked Questions

Related Guides

• Automation Tester Salary in UK (2026)
• Manual Tester Salary in Canada (2026)
• Manual Tester Salary in Germany (2026)
• Manual Tester Salary in India (2026)
• Manual Tester Salary in USA (2026)
• Performance Tester Salary in UK (2026)