What does a QA engineer do?
A QA engineer finds out whether software works before users do. The job covers planning what to test, designing test cases, running manual and automated tests, reporting defects clearly, and telling the team whether a release is ready. Many QA engineers also write and maintain test automation code.
The Bureau of Labor Statistics has no profile for the title QA engineer. The nearest is software quality assurance analysts and testers, who BLS says "design and execute software tests to identify problems." BLS gives their median annual wage as $104,300 in May 2025. It projects overall employment of software developers, quality assurance analysts, and testers to grow 10 percent from 2025 to 2035.
The O*NET OnLine profile for software quality assurance analysts and testers (15-1253.00) lists "Quality Assurance Engineer (QA Engineer)" among its reported titles. Its tasks include "Design test plans, scenarios, scripts, or procedures" and "Develop or specify standards, methods, or procedures to determine product quality or release readiness."
How were these QA engineer questions chosen?
Each QA engineer question here comes from a duty that BLS or O*NET publishes, matched to what an interviewer would test. The questions are drawn from the job's published duties, not from a survey of real interviews, and nothing here claims to be the most asked list or to describe a named company's process.
| Duty (BLS, O*NET) | Question it tends to produce | What the interviewer is checking |
|---|---|---|
| Create test plans, scenarios, and procedures | "How would you test this feature?" | Coverage by risk, beyond the happy path |
| Develop tests covering regression and negative testing | "What negative tests would you write?" | Bad input, limits and failure paths |
| Document and report defects | "Write a bug report for this." | Steps someone else can repeat, and severity |
| Update automated test scripts | "What would you automate first?" | Speed, stability and upkeep cost |
| Determine product quality or release readiness | "Is this build ready to ship?" | A clear call with the risks stated |
| Identify project risks and recommend steps | "Testing time was cut in half. What now?" | Priorities you can defend |
What test design questions come up?
Test design questions check whether a QA engineer thinks in risks and cases, beyond clicking through screens. Interviewers want to hear how you split a feature into inputs, states and users, which cases you would run first, and what you would leave out. O*NET lists regression testing, negative testing and usability among the areas a testing program covers.
1. How would you test a login page?
What they listen for: a plan that starts with the riskiest cases and covers function, security, accessibility and different devices. Follow-up that tends to come next: "Which five would you run if you had ten minutes?"
This question best shows the role, so here is a weak answer and the same answer fixed. Both are made-up examples.
Weak made-up example: "I'd enter a valid username and password and check that I get in. Then I'd try a wrong password and check that I get an error."
The weak answer stops at two cases and never asks what the page must do. It skips lockout, security, accessibility and the many ways input can be wrong.
Fixed made-up example: "First I'd ask about the rules: lockout after failed attempts, password reset, single sign-on, and which browsers matter. Then I'd group cases. Function: valid login, wrong password, unknown user, empty fields, very long input, and spaces before or after the email. Security: the error shouldn't reveal whether the account exists, lockout works, and the password isn't in the URL or logs. Accessibility: labels, keyboard only, and errors announced to a screen reader. I'd automate the main paths as regression tests and keep exploratory time for the odd cases."
2. What is the difference between a test plan and a test case?
What they listen for: a plan covers scope, approach, environments, risks and exit criteria; a case covers steps, data and the expected result. Follow-up: "Show me how you would write one case for a password reset."
3. How do you choose test data for a field that accepts ages 18 to 65?
What they listen for: boundary values (17, 18, 65, 66), a value inside the range, and invalid types such as letters, blanks and negatives. Follow-up: "How many cases is enough?"
What bug reporting questions should you expect?
Bug report questions test whether a QA engineer writes defects a developer can act on without a meeting. BLS lists "Document and report defects or problems with software" among the duties. Interviewers look for a clear title, exact steps, expected and actual results, environment details, evidence, and a severity you can explain.
4. Write a bug report for this broken checkout button.
What they listen for: a short title, numbered steps from a clean start, what you expected and what happened, browser and build, a screenshot or log, and how often it happens. Follow-up: "How would you rate its severity and priority?"
5. A developer says the bug can't be reproduced. What do you do?
What they listen for: you retest on a clean setup, add missing details such as data or timing, and sit with the developer if needed. O*NET lists "Perform initial debugging procedures by reviewing configuration files, logs, or code pieces to determine breakdown source." Follow-up: "What if it happens only one time in twenty?"
6. What is the difference between severity and priority?
What they listen for: severity is the harm to the user or system; priority is how soon the team should fix it. Give an example where the two differ. Follow-up: "Who decides priority on your team?"
What automation questions come up?
Automation questions check whether a QA engineer can build tests that stay fast and trustworthy. Google's book Software Engineering at Google says "small tests run in a single process, medium tests run on a single machine, and large tests run wherever they want." Interviewers want the right mix, and a plan for flaky tests.
7. Which tests would you automate first?
What they listen for: stable, high-value paths that run often, such as the main user flows and past regressions, before rarely used screens. Follow-up: "What would you keep manual, and why?"
8. What is a flaky test, and what do you do about one?
What they listen for: a definition and a plan. Google's testing blog post on flaky tests defines a flaky result as "a test that exhibits both a passing and a failing result with the same code." In 2016 Google reported a continual rate of about 1.5% of all test runs giving a flaky result. Quarantine the test, find the cause (timing, shared data, order), and fix or delete it. Follow-up: "Why not just rerun it until it passes?"
9. How do you balance unit, integration and end-to-end tests?
What they listen for: many fast small tests, fewer integration tests, and a small set of end-to-end tests for key journeys. The same book shows its suite as a pyramid and notes that "every team’s mix will be a little different." Follow-up: "Your end-to-end suite takes two hours. What do you change?"
What release and risk questions come up?
Release questions test whether a QA engineer can make a clear quality call under time pressure. O*NET lists determining "product quality or release readiness" among the tasks, and BLS lists identifying "project risks" and recommending steps to reduce them. Interviewers want a call, the evidence behind it and the risks you would accept.
10. Is this build ready to ship?
What they listen for: exit criteria agreed in advance, the open defects and their severity, what was not tested, and a clear recommendation. Follow-up: "The product manager wants to ship anyway. What do you say?"
11. Testing time was cut from two weeks to one. How do you plan?
What they listen for: test by risk, run the regression suite, focus on changed areas, and tell the team in writing what will not be covered. Follow-up: "What would you need to feel safe?"
12. A bug you missed reached production. What do you do?
What they listen for: help fix it, find why it slipped through, and add a test or check so it cannot recur. The guide to tell me about a mistake you made helps with structure. Follow-up: "Whose fault was it?"
Which behavioral questions should you expect?
Behavioral questions ask a QA engineer about real events with developers and managers, so answer each in STAR order: situation, task, action, result. Interviewers listen for how you argued for quality without blocking the team. The STAR method guide covers the structure.
13. Tell me about a time a developer disagreed with your bug report.
What they listen for: the evidence you brought, how you kept it about the user, and what was decided. The page on conflict with a coworker fits this question. Follow-up: "Would you handle it the same way now?"
14. Tell me about a process change you made that improved quality.
What they listen for: the problem, the change, how others adopted it and a measure of the result. Follow-up: "What did it cost the team?"
What follow-up questions tend to come next?
Follow-ups test whether your plan holds when something changes. A QA interviewer may add a new browser, remove a test environment, change a requirement late or cut your time, then ask what you would drop. Prepare by deciding in advance what your top ten tests are for each project you describe.
- "How do you know your tests cover the risk?"
- "What did your last regression run catch?"
- "How long does your automated suite take?"
- "How do you test something with no written requirements?"
- "What would you change about your last team's test process?"
How should you prepare for a QA engineer interview?
Prepare four STAR stories: a bug you found that mattered, a bug you missed, a disagreement with a developer and an automation you built. Practise designing tests for an everyday object or page out loud with a timer. Bring numbers you can stand behind, such as suite run time or defects found before release.
The free interview question generator takes the posting and the round you pick, and returns likely questions, why they come up and what the interviewer listens for. QA loops overlap with nearby roles, so compare this page with the questions for a software engineer, a front-end developer and a DevOps engineer.
Put test results on your resume, not only tool names. The guide to resume bullet points shows how. Prept's Mock room lets you answer out loud on a clock, scores each answer out of 10 and checks it against your resume, and it is included in the free plan.