SDET Salary in UK (2026)

TL;DR

A practical 2026 SDET salary UK benchmark is GBP 40,000 to GBP 75,000 for permanent Automation Tester or SDET roles in the Robert Walters UK salary survey. London, senior product roles, and specialist engineering can differ, while contract day rates must be compared after employment status, unpaid time, benefits, and risk.

Key Takeaways

• Robert Walters' 2026 UK guide places permanent Automation Tester or SDET roles at GBP 40,000 to GBP 75,000 in medium enterprises and GBP 45,000 to GBP 75,000 in large enterprises.
• The same guide shows a GBP 400 to GBP 600 PAYE contract day-rate range, which is not directly comparable with employee salary.
• London can pay more, but finance, commerce, public sector, consulting, and regional product markets use different bands and benefits.
• Pension contributions, bonus, equity, leave, private medical cover, on-call work, and office travel all affect total reward.
• Senior SDET roles require code, service testing, testability, CI reliability, observability, and influence beyond a UI suite.
• Candidates should verify current tax and employment-status rules for contract work rather than applying a generic day-rate multiplier.
• A clear achievement-led CV and a small runnable project provide stronger negotiation evidence than framework keyword density.

SDET salary UK searches produce several plausible answers because sources combine different titles, regions, levels, and employment types. Robert Walters' 2026 UK salary survey lists permanent Automation Tester or SDET ranges of GBP 40,000 to GBP 75,000 in medium enterprises and GBP 45,000 to GBP 75,000 in large enterprises. Its PAYE contract reference is GBP 400 to GBP 600 per day. Glassdoor's broader SDET Engineer category reports a lower mixed-market average, which shows why the definition matters.

Use these figures as starting evidence, then match the actual role. A London fintech test-platform position, a regional consultancy automation role, and a public-sector contract can share SDET language while offering different cash, risk, benefits, and engineering ownership.

TL;DR

All values are gross. A target should state whether it is base salary, total permanent reward, PAYE day rate, or another contract arrangement.

1. SDET salary UK benchmarks for 2026

The Robert Walters 2026 UK Salary Survey groups Automation Tester and SDET together. It reports GBP 40,000 to GBP 75,000 permanent annual salary for medium enterprises and GBP 45,000 to GBP 75,000 for large enterprises. The guide also gives average figures of GBP 65,975 and GBP 59,000 respectively. Those averages differ despite the similar ranges, which is a reminder to inspect the population rather than rank employer size mechanically.

Glassdoor's July 2026 SDET Engineer page reported about GBP 40,492 average total pay, with a typical range near GBP 30,986 to GBP 53,499. Its category includes thousands of submissions and may capture junior development-in-test programmes, consultancies, related titles, and locations outside the highest-paying product market. A separate exact-title sample can show a higher number but a much smaller submission count.

Keep the source and definition together. Robert Walters provides recruiter survey bands for Automation Tester or SDET. Glassdoor aggregates submitted pay for a title category. Neither knows your exact level. Add 25 current jobs, noting London or regional location, permanent or contract status, employer type, technology, security clearance, and published range.

The answer is a matched interval, not whichever website displays the largest figure.

2. Permanent salary and day rate answer different questions

Permanent employees receive an annual base and may receive bonus, pension contributions, equity, paid leave, sick pay, private medical cover, life assurance, income protection, learning support, and other benefits. Contractors may be quoted a PAYE, umbrella, agency, or company rate. The amount invoiced or paid per day is not personal take-home income and does not include the same risk.

The Robert Walters guide reports GBP 400 to GBP 600 as a PAYE contract day-rate range for Automation Tester or SDET. Multiplying a day rate by 260 assumes work on every weekday and ignores public holidays, leave, sickness, gaps, notice, training, administration, and contract termination risk. A realistic planning model uses several billable-day scenarios and keeps taxes and costs separate.

Ask the recruiter exactly how the rate is engaged and advertised. Determine who the employer is, what deductions or fees apply, whether holiday pay is included or accrued, and which expenses or equipment are covered. Employment-status and tax rules can materially change the comparison. Use current HMRC guidance and qualified advice for your circumstances.

Choose contract work for a reason, such as flexibility, specialist projects, or a deliberate risk premium. A day-rate headline alone is not a strategy.

3. London, regional hubs, and remote bands

London has deep finance, fintech, commerce, media, consulting, and global product markets. Some roles pay a London premium, particularly where domain knowledge, scale, or office attendance narrows the pool. Cambridge has software, research, semiconductor, and life-science employers. Bristol combines finance, aerospace, defence, and technology. Manchester, Leeds, Edinburgh, Glasgow, Birmingham, Belfast, Cardiff, Newcastle, and other cities have substantial product, public-sector, consulting, and regulated markets.

Do not subtract a fixed amount from London data to estimate every region. Employer mix matters. An Edinburgh financial platform role can pay above a London agency role. A defence position may trade cash for stability, pension, clearance sponsorship, or specialized experience. A remote-first US-linked product firm may use its own national band.

Build two comparison columns: gross reward and personal work cost. The second includes housing, commute, rail travel, parking, office days, childcare, and time. Confirm whether "remote" means anywhere in the UK, a commuting radius, or occasional client sites. Ask whether the team, not just company policy, actually follows the advertised pattern.

When a salary range is disclosed, ask which office and level it covers. A national advertisement can contain several location bands hidden behind one broad interval.

4. Level the responsibilities before the candidate

Junior SDETs implement reviewed automation, learn the system, and investigate contained failures. Mid-level engineers independently choose test layers, create data, build reliable API and UI coverage, and integrate CI. Senior SDETs own framework evolution, system-level risk, observability, and release evidence. Lead and staff roles influence several squads through architecture, coaching, standards, and tooling. Test managers may occupy a separate people and delivery path.

Use this role test:

Years are not enough. A ten-year candidate who has never owned code or system diagnosis may not meet a senior product SDET bar. A five-year candidate with cross-service tooling and strong influence may. The QA engineer versus SDET guide helps make the distinction explicit.

5. Total reward beyond base salary

UK permanent offers can include a target bonus, pension contribution, restricted stock or options, private medical insurance, dental cover, life assurance, income protection, enhanced parental leave, extra holiday, employee share plans, training, and home-office support. The tax treatment and personal value vary. Keep each item separate from guaranteed base.

Pension deserves attention. Record the employee contribution required to receive the full employer contribution, the scheme type, vesting or eligibility details, and salary-sacrifice options where applicable. A stronger pension can materially change long-term value, but it does not pay this month's rent. Balance both needs.

Bonus language matters. Ask about target percentage, company and individual factors, first-year proration, payment date, notice requirements, and historical practice without treating history as a promise. For equity, record grant type, number of units or options, vesting, exercise price where relevant, liquidity, and currency.

Time and responsibility are compensation. Compare contracted hours, holiday, on-call rota, weekend releases, travel, and office frequency. A GBP 5,000 base increase can disappear in rail costs and unpaid time if office expectations differ. Read the final employment agreement and policies before accepting.

6. Technical skills that improve UK market access

Modern browser automation remains useful, with Playwright, Cypress, and Selenium all appearing in UK vacancies. Higher-paying roles usually need more than a framework. Deepen Java, TypeScript, Python, or C# so you can solve coding tasks, design maintainable libraries, review pull requests, and debug async or concurrent behavior.

Service testing matters across finance, retail, travel, government, and SaaS. Learn HTTP, authentication, schema and contract testing, databases, queues, idempotency, and eventual consistency. Delivery ownership adds Git, Linux, containers, CI configuration, secrets, parallelism, and failure artifacts. Cloud and observability become valuable when you can trace a failing transaction across services.

Domain knowledge can differentiate candidates. Financial services reward understanding of ledger integrity, reconciliation, audit, fraud, and resilience. Public services may emphasize accessibility, privacy, policy rules, and reliable citizen journeys. Commerce values pricing, tax, inventory, payment, and fulfilment. Defence and certain government work can require eligibility for security clearance.

Use the API testing interview questions guide and the Playwright TypeScript tutorial to build a coherent browser and service story. Certifications help only when target vacancies require them or the learning changes your practice.

7. Write a runnable rail-refund rules test

This Node.js example tests a small refund rule as a pure function. It uses the built-in node:test and node:assert APIs, so there are no third-party packages or invented methods. Save it as refund-policy.test.mjs and run node --test refund-policy.test.mjs with a current Node.js release.

import test from 'node:test';
import assert from 'node:assert/strict';

function refundFor({ farePence, delayMinutes, journeyCompleted }) {
  if (!Number.isInteger(farePence) || farePence < 0) {
    throw new TypeError('farePence must be a non-negative integer');
  }
  if (!Number.isInteger(delayMinutes) || delayMinutes < 0) {
    throw new TypeError('delayMinutes must be a non-negative integer');
  }
  if (!journeyCompleted) return farePence;
  if (delayMinutes >= 60) return farePence;
  if (delayMinutes >= 30) return Math.floor(farePence / 2);
  return 0;
}

test('refunds half the fare at the 30-minute boundary', () => {
  assert.equal(
    refundFor({ farePence: 5101, delayMinutes: 30, journeyCompleted: true }),
    2550
  );
});

test('refunds an abandoned journey in full', () => {
  assert.equal(
    refundFor({ farePence: 5101, delayMinutes: 5, journeyCompleted: false }),
    5101
  );
});

test('rejects a fractional fare', () => {
  assert.throws(
    () => refundFor({ farePence: 10.5, delayMinutes: 30, journeyCompleted: true }),
    TypeError
  );
});

The policy is illustrative, not a statement of any operator's current rules. In an interview, identify missing dimensions: ticket type, operator, cause, return journey, multiple legs, claims window, caps, customer eligibility, and policy version. That distinction between executable logic and external policy demonstrates sound test design.

8. Create a UK-ready CV and portfolio

A UK CV commonly leads with a concise profile, relevant technical skills, and reverse-chronological experience. Keep official titles but explain scope where titles are vague. Avoid personal data that is not needed for the application. State work authorization accurately when it helps answer a predictable recruiter question.

Write achievement bullets with engineering mechanisms. "Built tests" says little. "Moved pricing invariants from 68 browser journeys into service contracts, reducing median pull-request feedback from 27 to 12 minutes" shows layer choice and outcome. Use only facts you can defend. If you lack measurements, describe scale and risk without inventing precision.

A portfolio should be small enough to review. Include setup, architecture, deterministic data, CI, artifacts, and a decision note. Add accessibility or API coverage when relevant to UK roles. Never publish employer repositories, production data, client names under confidentiality, or proprietary take-home solutions.

Use the SDET resume example to make ownership visible. Tailor the first half-page to the vacancy's real problem, whether that is platform reliability, financial services, mobile, or public accessibility. Keyword matching gets attention, but credible evidence wins the technical screen.

9. Prepare for UK SDET interviews

A typical process can contain recruiter screening, hiring-manager discussion, coding, test design, automation exercise, system design, and behavioral interviews. Consultancies may add a client conversation. Contracts can move quickly and focus on immediate delivery. Government or regulated roles may have longer checks. Ask for format, language, and live-coding expectations early.

Practice coding without test-framework helpers. Arrays, maps, parsing, object design, async behavior, error handling, SQL, and debugging are common foundations. For automation, explain locators, waiting, fixtures, page or component abstractions, API clients, data isolation, parallelism, and CI artifacts. Senior candidates should reason about contracts, events, observability, resilience, and organizational ownership.

Prepare stories about a critical defect, flaky suite, framework decision, release disagreement, incident, coaching, and mistake. Include the commercial or user risk, not only technical steps. UK interviewers may ask competency-style questions, but a rigid memorized script sounds thin. Use clear context, your specific action, result, and learning.

Ask how the team defines seniority, who owns quality at each layer, and what problem the role must solve in six months. Those answers also reveal whether the advertised salary matches the scope.

10. Contracting, employment status, and clearance

Contract work requires more due diligence than multiplying a rate. Determine the engagement route, status assessment, payment terms, termination notice, expected location, equipment, insurance, and who carries unpaid time. Rules associated with off-payroll working and IR35 are fact-specific and can change. Use current HMRC material and professional advice rather than social-media formulas.

Create a conservative cash-flow model with different billable-day and gap scenarios. Include pension saving, leave, sickness, professional costs, training, insurance, and delayed payment. Keep business revenue, taxable income, and personal take-home distinct. Contracting can still be attractive, but the decision should price risk intentionally.

Some defence, police, government, and critical-infrastructure roles require security clearance or eligibility checks. A candidate cannot always obtain a clearance independently, and residency or history requirements may apply. Read the vacancy, answer screening questions honestly, and ask what the employer sponsors. Do not claim a clearance that has expired or belongs to another context.

Permanent candidates also need written clarity on probation, background checks, start conditions, restrictive terms, and bonus eligibility. Verbal summaries do not replace the agreement.

11. Negotiate an SDET salary UK offer

Ask for the role's base band and level before anchoring. UK salary ranges increasingly appear in advertisements, but a broad range may cover several locations or seniorities. Ask what evidence places a candidate at the top. Then connect your request to the scope: "This role owns TypeScript tooling, service contracts, and CI reliability across four teams. Comparable senior positions support a base near GBP X. Is there flexibility to align the offer?"

Keep base, target bonus, equity, pension, and sign-on payment separate. Give a narrow researched range when required, not your minimum. Your private walk-away point should include manager, stability, commute, on-call load, growth, and family needs.

If base is fixed, explore pension, sign-on payment, bonus guarantee, equity, leave, flexible work, training, or an earlier review with written criteria. For a contract, negotiate rate together with notice, duration, location, and payment terms. A higher rate with immediate termination and heavy travel is a different product.

Never invent a competing offer. Ask for the final terms in writing and take reasonable time to review them. Use qualified advice when tax, status, equity, or contractual restrictions are material.

12. A 30-day UK salary campaign

Days 1 to 7 are for calibration. Choose permanent, contract, or both, then define target level and regions. Collect 25 vacancies and record employer type, salary or rate, location, office policy, language, test layers, cloud, clearance, and interview stages. Add the Robert Walters and Glassdoor references with their definitions.

Days 8 to 14 are for positioning. Rewrite CV bullets around code, risk, and outcomes. Prepare one story each for service testing, automation reliability, CI, architecture, collaboration, and failure. Complete a small runnable project with an honest limitations section.

Days 15 to 21 are for rehearsal. Solve practical coding tasks, review unstable test code, design coverage for a UK domain, and run a mock system-design interview. Practice the salary answer in annual gross base terms. Contractors should also complete conservative rate scenarios.

Days 22 to 30 are for evidence. Apply to matched roles, speak with recruiters, and record actual bands and level feedback. Diagnose repeated failure by stage. Do not rewrite your entire profile after one rejection. Use several consistent signals to adjust the target.

At day 30, your salary range should cite current matched roles, not only a national page. Add an expiry date and refresh it during an active search.

Interview Questions and Answers

Q: What salary are you looking for?

State a researched annual base range for permanent work or the exact engagement assumptions for a day rate. Connect the figure to the role's level and scope, then ask for the approved band. Keep bonus, pension, and equity separate.

Q: How do you decide what not to automate?

Avoid automating work with low repeat value, unstable intent, weak oracles, or high maintenance unless the risk justifies it. Preserve exploratory, usability, and judgment-heavy testing. Revisit the decision as the product stabilises and execution frequency changes.

Q: How would you test a rail refund policy?

Model policy versions, eligibility, ticket and journey types, delay boundaries, multiple legs, abandonment, partial use, caps, claims windows, and evidence. Keep policy data separate from calculation code. Verify rounding, audit trail, and customer communication.

Q: What is the difference between retrying and fixing a flaky test?

A retry repeats the condition and can gather evidence or mask a fault. A fix removes the causal source, such as shared data, poor synchronisation, unstable selectors, leaking state, or environment failures. Retries should remain reported, owned, and temporary.

Q: How do you test an event-driven service?

Verify message schema and semantics, producer and consumer contracts, authorization, ordering assumptions, duplicates, retries, dead letters, and idempotency. Correlate events to observable state with bounded waits. Include operational diagnostics and recovery behavior.

Q: What would you report to a delivery lead?

Report evidence tied to release decisions: critical-risk coverage, actionable failures, unresolved product risk, feedback time, and repeated incident themes. Separate environment and test faults from product defects. Avoid turning test count into a target.

Q: How do you review a take-home automation exercise?

I expect readable setup, deterministic execution, meaningful assertions, useful failure output, sensible abstractions, and an explanation of tradeoffs. I do not reward unnecessary framework complexity. The candidate should be able to explain every dependency and line they submit.

Common Mistakes

• Treating the largest published range as a guaranteed senior salary.
• Comparing a GBP 500 day rate directly with a GBP 65,000 permanent base.
• Multiplying a day rate by 260 without unpaid time, status, and risk.
• Ignoring pension, leave, bonus rules, office travel, on-call work, and notice.
• Assuming every London role pays more than every regional product role.
• Calling UI script maintenance senior SDET architecture.
• Preparing framework trivia while skipping coding, API, and system design.
• Claiming a security clearance or work status inaccurately.
• Uploading confidential employer or client material to a portfolio.
• Negotiating before confirming whether the range covers several levels or locations.

Conclusion

SDET salary UK evidence is clearest when employment type and title stay visible. Robert Walters' 2026 permanent range of GBP 40,000 to GBP 75,000 for Automation Tester or SDET is a strong recruiter benchmark. Glassdoor's lower mixed-category average and the GBP 400 to GBP 600 PAYE day-rate reference answer different questions.

Match the vacancy by level, region, domain, and engineering ownership. Compare base, pension, bonus, equity, time, and risk separately. Then support your target with a focused CV, runnable project, and interview stories that prove reliable delivery. That is how a broad UK range becomes a defensible personal number.

Interview Questions and Answers

Frequently Asked Questions

Related Guides

• Automation Tester Salary in UK (2026)
• QA Automation Engineer Salary in UK (2026)
• Manual Tester Salary in UK (2026)
• Performance Tester Salary in UK (2026)
• QA Lead Salary in UK (2026)
• QA Manager Salary in UK (2026)