Engineering and IT · Interview questions
QA Engineer interview questions
These questions check whether a candidate can design a test strategy, automate the right things and give honest release advice. Ask every candidate the same questions and score each against the notes.
The questions
Ask every candidate the same questions in the same order, and score each answer against the notes before you talk it over with the panel.
Our product is a web app where shops take online orders and payments. Outline how you would split testing between unit, integration, end-to-end and manual checks.
- What it tests
- Test strategy outcome, scenario.
- A strong answer
- They put most checks at the unit and integration level, keep end-to-end tests for core journeys such as ordering and paying, and use manual exploratory testing for new or risky areas. They explain the reasoning in terms of speed and risk.
- Watch for
- Planning to test everything through the browser.
Here is an automated test that clicks Login, waits five seconds, then checks for the dashboard. It fails about one run in ten. What is wrong and how would you fix it?
- What it tests
- Automation skill, practical code review.
- A strong answer
- They point to the fixed wait as the cause and replace it with waiting for a specific element or network response. They also check for shared test data or order dependence.
- Watch for
- Increasing the wait to ten seconds.
Tell me about an automated test suite you built. How did you keep it fast and trusted by developers?
- What it tests
- Regression suite outcome.
- A strong answer
- They describe choosing the journeys that matter, running tests in parallel and dealing with flaky tests quickly. Developers relied on the results because failures meant real problems.
- Watch for
- A large suite that developers routinely ignore or re-run until it passes.
Tell me about a bug that reached customers even though it should have been caught. What did you change afterwards?
- What it tests
- Reducing customer-found bugs.
- A strong answer
- They explain the gap honestly, such as no test for a payment edge case, and how they closed it. They changed a process, not only added one test.
- Watch for
- Blaming developers for not testing their own code.
It is release day. You have found a bug where the discount code is ignored for one rarely used payment method. The product owner wants to ship. What do you do?
- What it tests
- Release judgement and sign-off.
- A strong answer
- They give a clear view of impact and frequency, offer options such as shipping with the method hidden or a quick fix, and record the decision in the sign-off note. They respect that the product owner makes the final call.
- Watch for
- Either blocking without explaining impact or staying silent to avoid conflict.
How do you get involved in a feature before any code is written?
- What it tests
- Quality earlier in the process.
- A strong answer
- They review the requirements, ask about edge cases and write test cases with the developer at the start. They catch unclear rules before they become bugs.
- Watch for
- Only seeing features when developers say they are finished.
Write a bug report for this: the Save button on the profile page does nothing on Safari but works on Chrome.
- What it tests
- Clear bug reporting, work sample.
- A strong answer
- The report has a clear title, steps, expected and actual results, browser and device versions, and any console errors. It states severity and who is affected.
- Watch for
- A one-line report with no steps to reproduce.
How would you test an API endpoint that creates an order, without using the interface?
- What it tests
- API testing skill.
- A strong answer
- They test valid requests, missing and invalid fields, wrong permissions and duplicate submissions, and check the database result. They automate the important cases.
- Watch for
- Only testing the happy path with valid data.
New to structured interviews? Read how to run structured interviews and how to build an interview scorecard.
Start from the job description
These questions follow the first-year outcomes in the matching template.
QA Engineer job description templateSimilar roles
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.