QA Engineer interview questions
A QA engineer interview should test how the candidate thinks about risk, finds edge cases, and writes bug reports and automated tests that developers trust. Give them a real feature or form to test and listen for the breadth and prioritization of their ideas.
What to assess
Behavioral questions
Tell me about the most important bug you caught before release.
What it reveals: Shows impact and testing instincts.
A strong answer: Explains how they found it, why it mattered to users or revenue, and how it was resolved.
Describe a time a serious bug slipped through to production. What did you learn?
What it reveals: Tests accountability and process improvement.
A strong answer: Owns their part without blame and describes a specific test or process change afterward.
Give an example of when a developer disagreed that something was a bug.
What it reveals: Reveals communication and diplomacy.
A strong answer: Refers back to requirements or user impact, stays factual, and involves the product owner if needed.
Tell me about a test automation suite you built or improved.
What it reveals: Shows automation experience and judgment.
A strong answer: Describes framework, what they chose to automate, flakiness reduction, and time saved.
Describe a time you had very little time to test before a release.
What it reveals: Tests prioritization under pressure.
A strong answer: Focused on highest-risk areas, communicated what was not tested, and documented the risk.
Role-specific questions
How would you test a login page? List as many test cases as you can.
What it reveals: Tests breadth of test design thinking.
A strong answer: Covers valid and invalid inputs, security, lockout, accessibility, password reset, sessions, and devices.
What makes a good bug report?
What it reveals: Checks a core QA skill.
A strong answer: Includes clear title, steps to reproduce, expected versus actual results, environment, severity, and evidence.
How do you decide which tests to automate and which to keep manual?
What it reveals: Tests automation strategy.
A strong answer: Automates stable, repetitive, high-value paths and keeps exploratory and rapidly changing areas manual.
How would you deal with a flaky automated test that fails randomly?
What it reveals: Tests maintenance discipline.
A strong answer: Investigates timing, test data, and dependencies, quarantines if needed, and fixes rather than ignores it.
How do you test a REST API endpoint?
What it reveals: Tests API testing knowledge.
A strong answer: Checks status codes, schemas, auth, invalid inputs, boundaries, and performance using tools like Postman or code.
Situational questions
The release is tomorrow and you find a moderate bug that affects a small group of users. What do you do?
What it reveals: Shows risk communication judgment.
A strong answer: Documents impact clearly and gives decision-makers the facts to choose whether to ship, fix, or mitigate.
You join a team with no test plan and no automated tests. What are your first 30 days?
What it reveals: Reveals planning and prioritization.
A strong answer: Learns the product, identifies critical user flows, adds smoke tests, and builds a practical test strategy.
Requirements for a feature are vague and the developer is already building. How do you proceed?
What it reveals: Tests proactive quality advocacy.
A strong answer: Asks clarifying questions early, writes acceptance criteria with the team, and shares test ideas upfront.
Motivation and fit
What do you enjoy most about quality work?
What it reveals: Shows motivation for the role.
A strong answer: Gives a genuine reason such as protecting users or the satisfaction of finding tricky problems.
How do you like to work with developers so quality is a shared responsibility?
What it reveals: Reveals collaboration style.
A strong answer: Describes involvement early in planning, pairing, and positive working relationships.
Red flags
- Only tests the happy path
- Writes vague bug reports like 'it does not work'
- Sees QA as gatekeeping rather than collaboration
- Automates everything without regard to maintenance cost
Questions not to ask
- Do you have any learning disabilities that affect attention to detail? — disability questions before an offer violate the ADA
- Will you need time off for childcare during release crunch? — family status and sex discrimination risk
- Where were you born? — national origin discrimination risk
- Are you over 40? — age discrimination risk under the ADEA
Interviewing for qa engineer roles?
Generate a structured kit with scoring guidance for your exact role in seconds.
Frequently asked questions
What is a good practical exercise for a QA engineer interview?
Ask the candidate to test a simple form or feature and list test cases, then write one bug report. This quickly shows edge-case thinking, prioritization, and communication.
Should a QA engineer job description focus on manual or automated testing?
Describe the real mix. Many teams need both, so state the percentage of time on automation and the frameworks used so candidates can self-select.
How many QA engineers does a small software team need?
It varies, but many small teams start with one QA engineer per four to eight developers while building a culture where developers write tests too. Your release frequency and risk level matter more than a fixed ratio.