Quality Assurance Test Infrastructure Engineer

A Quality Assurance Test Infrastructure Engineer builds and maintains the systems that let a software team's automated tests run reliably - the test machines, pipelines, emulators, test data and reporting dashboards. Rather than writing tests for individual features, you make sure the whole testing machinery works, is fast, and gives trustworthy results. You work mainly for the engineering teams inside your own company (developers, QA engineers, release managers) rather than for external clients.

Starting salary: £27k–£38k
Live graduate jobs: Search all jobs
Main way in: Graduate software engineering or technology schemes at larger…
They usually ask for: A degree in computer science, software engineering or a closely…

Approximate graduate salary

Typically somewhere around £27,000–£38,000 to start, though this varies widely. London and large tech or finance employers sit at or above the upper end; smaller firms, consultancies and roles outside the South East often start lower. Defence and cleared roles can pay a premium once clearance is held.

What you'd actually do

Maintaining and extending CI/CD pipelines - 'continuous integration/continuous delivery', the automated system that builds code and runs tests every time a developer submits a change - so that test suites trigger correctly and report results back to the right place.
Investigating 'flaky' tests: tests that pass sometimes and fail other times for reasons unrelated to the code, often caused by timing issues, shared test data or an unstable environment. A lot of the job is working out whether a failure is a real bug or an infrastructure problem.
Setting up and configuring test environments - servers, containers, virtual machines, device labs or mobile emulators - so they mirror production closely enough for test results to mean something.
Writing scripts and tooling (commonly Python, Bash, Groovy, or the team's main language) to generate test data, spin environments up and down, or automate repetitive setup work.

Show 3 more

Fielding questions from developers and QA testers who are blocked - 'the build is red and I don't know why', 'the test environment is down' - and triaging whether it's their code or your infrastructure.
Monitoring how long test runs take and reducing them, for example by parallelising tests across machines or splitting a slow suite, because a test pipeline that takes hours slows everyone down.
Reviewing test reporting and dashboards, and sometimes presenting trends (which suites are unstable, where coverage is thin) in team or sprint meetings.

How graduates get in

Graduate software engineering or technology schemes at larger employers - banks, telecoms, retailers, defence, games studios and big tech firms - where you may rotate through teams and can be placed into or move towards a test infrastructure or platform team. Being hired directly into this exact title as a graduate is relatively unusual.
Direct entry as a Graduate QA Engineer, Test Automation Engineer or Software Development Engineer in Test (SDET), then specialising into infrastructure work once you know the codebase and tooling. This is probably the most common route.
Starting in a DevOps, platform engineering or build engineering graduate role and moving sideways into test infrastructure - the skills (pipelines, containers, cloud, scripting) overlap heavily.
A placement year or summer internship with a software team, which matters a lot here because this is a role where hands-on familiarity with a real build system counts for more than coursework.

Show 2 more

Moving up from a manual QA tester or IT support/junior sysadmin position by learning scripting and automation on the job. This route is slower but genuinely common, and employers do hire from it.
Conversion routes - a computing MSc after a non-computing degree, or a Level 4/6 apprenticeship in software/DevOps engineering - are both accepted by many employers, though apprenticeship routes tend to be offered to school leavers rather than graduates.

What employers ask for

A degree in computer science, software engineering or a closely related technical subject is the most common background, but it varies - physics, maths, engineering and even self-taught career changers are hired where the person can demonstrably code. Some employers set a 2:1 threshold, others do not filter on classification at all and rely on a technical test.
Programming ability in at least one language - Python, Java, C#, JavaScript/TypeScript or Go are the usual suspects. You will not be building user-facing products, but you absolutely need to write and read code.
Comfort with Linux and the command line. This is close to non-negotiable, since most test infrastructure runs on Linux servers or containers.
Some exposure to version control (Git) and ideally to a CI tool such as Jenkins, GitLab CI or GitHub Actions. Many graduates get this from a final-year project or placement rather than formal teaching.

Show 2 more

Awareness of containers (Docker), and cloud platforms (AWS, Azure or Google Cloud) is increasingly expected - though for graduate roles this is usually 'you've seen it' rather than 'you can architect it'. Vendor certifications (AWS, Azure) help but are rarely required.
Security clearance (SC or DV) is required for defence, government and some finance roles, which generally means UK residency for a set period. The ISTQB Foundation certificate - a widely recognised entry-level testing qualification - is asked for at some employers, mainly in consultancy and regulated sectors, and is not needed at most product companies.

Skills that matter

Systematic debugging of systems you didn't build

Most of your time goes on working out whether a red build is caused by the code, the test, the environment or the network, and you need a method rather than guesswork.

Scripting and automation

Anything you do manually twice is something you should be scripting, because the whole point of the role is removing manual toil from the testing process.

Reading logs and system output

Pipeline failures usually surface as thousands of lines of log output, and being able to find the one relevant line quickly is a genuinely distinguishing skill.

Understanding of networking and infrastructure basics

Test environments break for DNS, port, certificate and permissions reasons constantly, and you cannot fix what you cannot diagnose.

Patience with interruption and the ability to triage

You are effectively a support function for other engineers, so you need to judge whether something is 'everyone is blocked, drop everything' or 'add it to the backlog'.

Explaining technical problems to other technical people without blame

You frequently have to tell a developer their change broke the pipeline, or admit your infrastructure caused a false failure, and doing that well determines how much the team trusts your results.

Putting these on a CV? We counted which skills 12,914 live graduate adverts ask for, and what to do with the answer — part of our application advice.

Where it leads

Graduate or junior level: working on well-defined tickets, fixing individual flaky tests, maintaining existing pipelines, learning the stack. Expect roughly the first year or two to be this, though it varies by employer and how much you already know.
Mid-level test infrastructure or SDET engineer: owning a test suite or a chunk of the pipeline end to end, making design decisions about how environments are provisioned, mentoring new starters.
Senior engineer: setting the testing strategy for a product area, choosing tooling, leading migrations (for example moving a test estate to the cloud or from one CI tool to another). Timelines to senior vary widely - some people get there in four or five years, others take longer, and job-hopping tends to accelerate it.
From senior, the paths fork. Common moves are into DevOps/platform engineering or Site Reliability Engineering (SRE), into general software development, into QA or engineering management, or into a principal/staff engineer track where you influence testing practice across multiple teams.
Contracting and consultancy are realistic later options, since test automation and CI expertise is in demand on a project basis - though day rates and availability fluctuate with the market, and IR35 rules affect how contracts are structured.

What people get wrong

“QA means manually clicking through an app looking for bugs, so it's the least technical job in software.”

Test infrastructure is one of the more technical corners of software engineering - closer to DevOps than to manual testing. You are writing code, managing servers and cloud resources, and maintaining systems that the whole engineering team depends on.

“It's a stepping stone you take because you weren't good enough to be a 'real' developer.”

It is a recognised specialism with its own senior and principal grades, and the skills transfer directly into DevOps, SRE and platform engineering - which are among the better-paid technical tracks. Plenty of people move into it deliberately from development, not out of it.

“You spend your days writing tests.”

Writing feature tests is usually someone else's job - often the developers themselves. Your work is the layer underneath: the runners, environments, data, pipelines and reporting that make those tests executable and believable.

“Automation means the role will automate itself away, or be replaced by AI test generation tools.”

Automated test suites and AI-generated tests create more infrastructure to maintain, not less - more runs, more environments, more results to make sense of. The maintenance burden is the job.

Where this varies

The job differs a lot by sector. At product software companies and tech-led startups, the line between this role and DevOps or platform engineering is blurry and you may be expected to write production-quality code. In banking, insurance, defence and government, the role is more process-driven, with formal test documentation, change-control approvals and sometimes a requirement for security clearance - and the tooling may be older and more on-premise. In games, test infrastructure often means device labs and build farms for consoles. In consultancies, you may be placed on a client site and change stack every year or so. Team structure also varies: some companies have a dedicated test infrastructure team, while in others a single engineer handles it alongside other work, or the responsibility is spread across a DevOps team with no one holding this exact title.

Search Quality Assurance Test Infrastructure Engineer jobsFrom employers' own careers sites, updated daily Tailor your CV for this roleFree with an account, 3 a month

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.