Home · Interview questions · QA Engineer

QA Engineer interview questions

QA interviews test how you think about risk. It's less about how many tests you write and more about whether you find what matters before customers do.

What interviewers look for

Test design. Boundary cases and thinking about risk.
Automation. Stable, maintainable tests.
Communication. Bug reports developers can act on.

How the interview usually runs

Recruiter call.
Testing fundamentals interview.
Practical automation or test-writing task.
Team interview.

Stages vary by company, so ask the recruiter what to expect before you start preparing.

8 QA Engineer interview questions, and how to answer them

1. How would you test a login page?

What they want to see: Test thinking.

How to answer: Cover valid and invalid input, lockout, security, accessibility and mobile.

2. What's in a good bug report?

What they want to see: Clarity.

How to answer: Steps, expected and actual results, environment, evidence and severity.

3. Severity or priority?

What they want to see: Fundamentals.

How to answer: How bad it is against how soon to fix it, with an example of each differing.

4. What would you automate first?

What they want to see: Judgement.

How to answer: Stable, valuable, repeated flows. Leave changing UI to manual checks.

5. How do you handle a flaky test?

What they want to see: Automation maturity.

How to answer: Quarantine it, find the cause and fix waits or data.

6. You don't have enough time to test everything.

What they want to see: Risk-based testing.

How to answer: Prioritise by user impact and recent change, and state what wasn't tested.

7. How do you test an API?

What they want to see: Technical skill.

How to answer: Check contracts, status codes, errors, auth and data with Postman or code.

8. Tell me about a bug you're proud of finding.

What they want to see: Curiosity.

How to answer: Say how you found it and what it would have cost.

A sample answer

You don't have enough time to test everything.

Before one release we had a day for two days of testing. I listed what changed, ranked by risk and focused on payments and login. I ran the automated regression, then explored the new discount logic by hand, which is where I found a rounding bug. I told the team which low-risk areas weren't covered, and they accepted that.

A made-up example to show the structure. Use your own experience and real numbers.

Common mistakes

Only testing the happy path.
Bug reports with no steps.
Treating automation as a goal in itself.
Not saying what was left untested.

Practise this out loud

Run a mock interview for a QA Engineer role. Questions change every time, you answer by voice or typing, and each answer gets a score with feedback.

Start a free mock interview See how Ghostpilot works

Frequently asked questions

Do QA engineers need to code?

For automation roles, yes. Manual QA roles need less, though basic SQL and API skills help.

Which tools should I learn?

Playwright or Cypress, Postman and a CI tool cover most job adverts.