QA Engineer Interview Questions: Complete 2026 Guide, Costly Gap

Screen showing code reviewed during qa engineer interview questions
Spread the love

Over the six months to 22 August 2026, the median UK salary for a QA Engineer was £45,000. For a QA Automation Engineer it was £60,500.

Same discipline. Same industry. One word of difference in the job title, worth £15,500.

That gap is the most reliable thing anyone can tell you about qa engineer interview questions right now — more reliable, as it turns out, than the interview evidence itself. This guide covers both, and is explicit about which is which.

Tester working through qa engineer interview questions and a defect report

The Title Ladder Behind QA Engineer Interview Questions

UK medians from ITJobsWatch, six months to 22 August 2026. These pages recompute daily, so treat them as a snapshot rather than a constant.

  • Software Engineer — £70,000 (5,198 advertised roles)
  • QA Automation Engineer — £60,500, up 0.8% year on year (46 roles)
  • SDET — £55,000 (74 roles)
  • Test Engineer — £50,000 (817 roles)
  • QA Engineer — £45,000, down 21.7% (318 roles)

Two caveats worth stating, because most pages quoting these numbers do not. The QA Automation Engineer and SDET medians rest on only 46 and 74 advertised roles respectively, against 5,198 for Software Engineer. Thin bases move around.

And the QA Engineer vacancy count itself has been unstable: 196 in 2024, 84 in 2025, 318 in 2026. A near-fourfold rebound off a collapsed base looks more like a classification change than real demand.

What the ladder does show consistently is direction. The automation-titled role rose slightly while the plain QA Engineer title fell more than a fifth in a year — which is worth holding in mind while you prepare qa engineer interview questions for a role you have not yet accepted.

Do QA Engineer Interview Questions Include a Coding Round?

Sometimes — and the honest answer is that the job title predicts it better than anything else you can check in advance.

Roles that genuinely do not require programming still exist. In the postings we reviewed they cluster away from the words “QA Engineer” and toward QA Analyst, Manual QA Tester and Test Analyst. If you are searching only for qa engineer interview questions, you may be preparing for the version of this job with the highest coding expectations and the lowest pay.

Where the engineer title does come without code, what substitutes for it is usually deep domain knowledge — hardware, trading systems, regulated environments. That is the trade being made.

One warning about titles in the other direction. A posting headed “QA Manual Engineer,” which closed in November 2024, required “Solid knowledge of SQL and scripting” plus automated-tool experience. The word “manual” in a job title is not a promise.

We cannot give you a proportion. Our sample was gathered by searching deliberately toward the no-coding end, so it is biased by construction, and several listings we found came from board summaries rather than opened requisitions. Anyone quoting you a percentage here is guessing more confidently than we are.

What Candidates Report Being Asked

This is where honesty costs something, so here it is up front: the public evidence about these interviews is thin, dated, and scattered. We worked from roughly a dozen candidate accounts across ten employers. Only six are from 2025 or 2026. Blind was unreachable throughout, so most came via Glassdoor.

With that stated, here are the shapes that recur across reported qa engineer interview questions:

Scenario work. An Indeed candidate in November 2021 was asked how they would test a coffee machine. Take an everyday object, produce a strategy. It is the oldest pattern in testing interviews and it has not gone away.

Artefact discussion. An Amazon candidate reporting in February 2025 described multiple rounds covering “test plan, test case, different testing techniques, Behavioural Qs, Programming Q.” Test design led — but note that programming was in the mix.

Tool experience, asked concretely. An Indeed candidate in March 2023: “Which tools did you use for mobile debugging?” Not a definition — a request for specifics about work you have done.

Take-home assignments. Two QA Wolf candidates, in December 2025 and April 2026, describe Playwright take-homes. Both also reported their submission appearing to go unreviewed — one wrote “They didn’t even watch my Loom,” another “0 views on the Loom you required that I upload.”

That is two accounts out of 32 on the company’s Glassdoor page. Read it as a complaint that exists, not a pattern we have established.

Coding, at some employers. Three NVIDIA candidates in 2026 all faced it — “a leetcode question about arrays” in two accounts, two Python questions in a third. Two of the three were based in Israel and the third did not state a location, so we cannot assume the US loop matches.

The Definitions Every Guide Drills

Nearly every competing page of qa engineer interview questions is built from definitional theory — severity versus priority, the bug life cycle, SDLC versus STLC. One widely-cited page lists seventy-six questions in that mould.

None of the accounts in our sample reported being asked one. But we went looking specifically for counterexamples, and they exist: a QA Engineer candidate at Enzigma in March 2021 reported being asked about “severity and priority,” and one at Qualys in November 2016 reported “bug cycle.”

So the honest position is narrower than “nobody asks these.” It is that the definitional questions show up in older accounts and at smaller employers, while recent accounts skew heavily toward scenario work, artefacts and tools. An hour of revision on the classic definitions is cheap insurance. A weekend of it, at the expense of practising a test strategy out loud, is a bad trade.

Is ISTQB Actually a Gate?

Rarely — and it is not the route around the coding side of qa engineer interview questions that it is often sold as.

UK permanent roles citing ISTQB have fallen to 103 from 155 year on year, dropping 146 places in the rankings. More telling: 73.8% of the ads that do cite ISTQB also cite test automation. The certification increasingly travels alongside code rather than instead of it.

The one posting we found listing ISTQB Foundation as essential carried the escape clause “or willingness to work to equivalent standards,” and has since closed.

The Tooling Has Shifted

If you are on the automation track, this is worth knowing before you pick a course or a practice project.

Playwright now appears on 12.6% of UK QA Engineer advertisements. Selenium sits at 8.5%. Selenium is not gone — it is four points behind, on a tool that dominated this field for a decade. Both QA Wolf take-homes in our sample were Playwright.

One Thing Nobody Can Tell You

What happens to manual testers when their employer automates — retrained, retitled, or let go?

We searched specifically for first-person accounts. We found none. Every result was vendor content — “Manual Testing Is Dead,” “Why AI QA Engineers Are Replacing Traditional Testing Teams” — published by companies selling automation tooling. The closest thing to a real account was a blog post recounting other people’s forum posts.

The confident answer is available everywhere. The evidence for it is not. If your career decision depends on knowing, weigh who is paying for each source you read — including pages ranking for qa engineer interview questions.

The forecasts disagree too

US Bureau of Labor Statistics projections have software quality assurance analysts and testers growing from 201,700 in 2024 to 221,900 by 2034 — about 10%, or roughly 20,200 added jobs over the decade. BLS’s “much faster than average” label applies to the wider Software Developers, QA Analysts and Testers group, projected at 15%, not to the QA line specifically.

Meanwhile UK median pay for the QA Engineer title fell 21.7% over the six months we measured. Different countries, different metrics, different horizons — and most pages quote whichever suits the argument they are making.

Preparing for QA Engineer Interview Questions

Read the requisition, not the title. It is the only reliable signal of whether a coding round is coming, and no list of qa engineer interview questions substitutes for it. Titles mislead in both directions.

Ask the recruiter directly whether there is a coding round. It is a reasonable question, and the answer reshapes a whole week of preparing qa engineer interview questions.

Rehearse one scenario out loud. Take something you use daily and talk through a strategy in ten minutes — happy path, boundaries, failure modes, data integrity. That shape appears more than anything else across the reported accounts.

Prepare concrete tool answers. “Which tools did you use for X” comes up. Have specifics, including what went wrong and what you would change.

Give the definitions an hour, not a weekend. They are asked occasionally. They are not what recent accounts describe.

Frequently Asked Questions

What are the most common qa engineer interview questions?
Across the accounts we reviewed: scenario prompts such as how you would test a given product, discussion of test plans and test cases, and concrete questions about tools you have used. Coding appears at some employers.

Can I get a QA job without learning to code?
Roles without a programming requirement still exist, but they cluster under QA Analyst, Manual QA Tester and Test Analyst rather than QA Engineer. Under the engineer title, deep domain expertise is usually what substitutes for code.

Are qa engineer interview questions the same as SDET questions?
No. SDET loops centre on a coding bar equivalent to software engineering. QA loops centre on test design, with coding appearing at some employers. The £10,000 median pay gap between the two titles is consistent with that difference.

Will I be asked to define severity versus priority?
Possibly. It did not appear in our sample, but candidate reports of it do exist — mostly older ones and at smaller employers. Worth an hour of revision, not a weekend.

Is ISTQB worth getting?
UK demand for it is falling, and nearly three quarters of ads citing it also want test automation. It will not shield you from a coding requirement.

Is manual testing a dead end?
We could not find first-hand evidence either way, and the loudest voices on the question sell automation tools. What we can say: UK pay for the QA Engineer title fell sharply this year, while US projections show the occupation growing.

Do interviewers ask about AI testing tools?
No candidate in our sample reported it, though prep content asserts it confidently. The same gap appeared in our SDET research.

Before You Prepare Anything

The single highest-value move when facing qa engineer interview questions is not revising definitions. It is checking which version of this job you have actually applied for — because the title determines the coding expectation, the interview shape, and, on the UK numbers, about £15,500 of salary.

For the occupation-level picture, the US Bureau of Labor Statistics outlook breaks out software quality assurance analysts and testers, and carries none of the commercial interest attached to most writing on this subject.

If your target role leans automation, our guide to SDET interview questions covers the loop with the higher coding bar. For how loops differ across every job we cover, start from interview questions by role.

Leave a Reply

Your email address will not be published. Required fields are marked *