QA Engineer Interview Questions and Answers
QA and test automation interview questions with answers: testing fundamentals, test design techniques, bug reports, API testing, Selenium and Playwright, CI, performance and practical scenarios.
Key takeaways
- QA interviews start with fundamentals: test levels, test design techniques and a good bug report.
- Automation roles add Playwright or Selenium, API testing and CI, plus a live coding task.
- A classic exercise is “How would you test this?”: interviewers grade coverage and prioritization.
- Senior candidates are asked about test strategy, flaky tests and quality processes, not only tools.
Contents
QA interviews check whether you think like a tester: finding what could go wrong, prioritizing by risk and communicating clearly. Automation roles add coding and tooling. Below are 32 common questions grouped by topic and level.
The test pyramid
An illustrative target, not a rule; the shape matters more than exact numbers.
Manual vs automation roles
| Manual / functional QA | QA automation (SDET) | |
|---|---|---|
| Main skills | Test design, exploratory testing, domain knowledge | Programming, frameworks, CI, test architecture |
| Typical tools | Jira, TestRail, Postman, DevTools | Playwright, Selenium, Cypress, REST clients, CI |
| Interview tasks | “How would you test this?”, bug report | Live automation task, code review, API tests |
Testing fundamentals
1What is the difference between QA, QC and testing?
JuniorQuality assurance is about processes that prevent defects (reviews, standards). Quality control checks the product for defects. Testing is the activity of executing the product to find problems. In practice, QA engineers do all three to some degree.
2What are the levels of testing?
JuniorUnit tests check small pieces of code in isolation. Integration tests check how components work together. System / end-to-end tests check complete user flows. Acceptance tests confirm the product meets business requirements.
3What is the test pyramid?
JuniorMany fast unit tests at the bottom, fewer integration tests in the middle, and a small number of slow end-to-end tests at the top. It keeps feedback fast and test suites stable. An “ice cream cone” (mostly manual and UI tests) is the anti-pattern.
4Functional vs non-functional testing?
JuniorFunctional testing checks what the system does (features, business rules). Non-functional testing checks how well it does it: performance, security, usability, accessibility, reliability and compatibility.
5Smoke vs sanity vs regression testing?
JuniorSmoke: a quick check that the main functions work after a build. Sanity: a narrow check that a specific fix or change works. Regression: re-running tests to make sure existing functionality wasn’t broken by changes.
6Severity vs priority?
JuniorSeverity is the technical impact of a bug; priority is how soon it should be fixed. A typo in the company name on the homepage is low severity but high priority; a crash in a rarely used admin report may be high severity but lower priority.
Test design
7What are equivalence partitioning and boundary value analysis?
JuniorEquivalence partitioning groups inputs that should behave the same and tests one value from each group. Boundary value analysis tests at and around the edges of those groups, where bugs are most common. For an age field accepting 18–65: test 17, 18, 65, 66, plus a typical value and invalid input.
8What are decision tables and state transition testing?
MidDecision tables list combinations of conditions and the expected result, useful for business rules such as discounts. State transition testing models states and transitions (order: created → paid → shipped → delivered) and checks valid and invalid transitions.
9How do you test a login page?
MidFunctional: valid and invalid credentials, empty fields, case sensitivity, remember me, password reset, lockout after failed attempts. Security: SQL injection, brute-force protection, password masking, HTTPS, no credentials in URLs or logs. Usability and accessibility: keyboard navigation, error messages, screen readers. Also cross-browser and mobile.
10How would you test a pen (or an elevator, or a vending machine)?
MidThe interviewer wants structure: clarify requirements and users, then cover functional tests, boundaries, negative cases, performance and durability, usability, safety and compatibility. Prioritize the most important tests and say why.
11What makes a good test case?
MidA clear title and purpose, preconditions, specific steps, test data and an expected result. It should be independent of other tests, repeatable and traceable to a requirement.
Get QA Engineer answer points in real time during your interview
Sottena listens to the interviewer, detects each question and shows short answer points in about a second. 150 free credits, no card required.
Bugs and process
12What makes a good bug report?
JuniorA concise title, environment (version, browser, device), exact steps to reproduce, expected vs actual result, severity, and evidence (screenshots, logs, video). One bug per report. A developer should be able to reproduce it without asking questions.
13Describe the bug life cycle.
JuniorNew → assigned → in progress → fixed → ready for testing → verified → closed. Alternative paths: rejected, duplicate, deferred, or reopened if the fix doesn’t work.
14A developer says your bug can’t be reproduced. What do you do?
MidRe-check the steps and environment, try to reproduce it again, gather more evidence (logs, network requests, video), compare environments and data, and reproduce it together with the developer. Stay factual: the goal is a fix, not winning the argument.
15What is shift-left testing?
MidMoving testing earlier in development: reviewing requirements, testing in pull requests, writing automated tests alongside code. Defects found earlier are cheaper to fix.
16How do you decide when testing is done?
SeniorTesting is never complete; you decide when the risk is acceptable. Use exit criteria: critical flows pass, no open high-severity bugs, coverage of high-risk areas, and stakeholder agreement on known issues.
API testing
17What do you check when testing a REST API?
JuniorStatus codes, response body and schema, headers, error messages, authentication and authorization, input validation (missing, invalid, boundary values), idempotency of methods, pagination and performance.
18What do HTTP status codes 200, 201, 400, 401, 403, 404 and 500 mean?
Junior200 OK, 201 Created, 400 Bad Request (invalid input), 401 Unauthorized (not authenticated), 403 Forbidden (authenticated but not allowed), 404 Not Found, 500 Internal Server Error.
19Write an automated API test.
MidWith Playwright’s API testing:
import { test, expect } from "@playwright/test";
test("creates an order", async ({ request }) => {
const res = await request.post("/api/orders", { data: { productId: 42, qty: 2 } });
expect(res.status()).toBe(201);
const body = await res.json();
expect(body).toMatchObject({ productId: 42, qty: 2, status: "created" });
});
20What is contract testing?
MidVerifying that a service and its consumers agree on the API contract (requests and responses), without running the full system. Tools like Pact let consumers define expectations that the provider checks in its pipeline, catching breaking changes early.
Test automation
21Selenium vs Playwright vs Cypress?
MidSelenium supports many languages and browsers via WebDriver and has the largest ecosystem. Playwright has automatic waiting, parallel execution, multiple browsers and good tracing. Cypress runs inside the browser with an excellent developer experience, but with some limits on multi-tab and cross-origin scenarios.
22What is the Page Object Model?
MidA pattern where each page or component is a class exposing actions (login(user)) and hiding selectors. Tests become readable and a UI change is fixed in one place instead of in every test.
23How do you choose good selectors?
MidPrefer user-facing attributes: roles and accessible names (getByRole('button', { name: 'Pay' })), labels, or dedicated data-testid attributes. Avoid long CSS or XPath chains tied to layout, which break with every redesign.
24Why are tests flaky, and how do you fix them?
MidCommon causes: fixed sleeps instead of waiting for conditions, shared test data, order dependence, unstable environments and animations. Fix them with explicit waits on state, isolated test data, independent tests, mocked external services and retries only as a last resort, while tracking flaky tests.
25What should and shouldn’t be automated?
MidAutomate stable, repetitive, high-value checks: regression suites, smoke tests, API tests, data-driven cases. Keep manual or exploratory testing for new features still changing, usability, visual judgment and one-off checks.
26How do tests fit into CI/CD?
MidFast unit and API tests run on every pull request; a smoke suite runs on each deployment; the full regression suite runs nightly or before release. Failures block merging, and reports with traces and screenshots make investigation quick.
Performance and security
27Load vs stress vs soak testing?
MidLoad: expected traffic, to check response times. Stress: beyond expected traffic, to find the breaking point and how the system fails. Soak: steady load over a long period, to find memory leaks and degradation. Tools: k6, JMeter, Gatling, Locust.
28Which security issues should a QA engineer check?
MidAuthentication and session handling, authorization (can user A see user B’s data?), input validation against injection and XSS, sensitive data in logs or URLs, and HTTPS everywhere. The OWASP Top 10 is the standard reference.
Scenarios and strategy
29You have one day to test a release. What do you do?
MidPrioritize by risk: the changed areas, critical user flows (sign-up, payment), and areas with a history of bugs. Run automated regression, do focused exploratory testing on new changes, and communicate clearly what was and wasn’t tested.
30How would you build a test strategy for a new product?
SeniorUnderstand the product, users and risks; define the test levels and the automation pyramid; choose tools; agree on environments and test data; integrate testing into CI; define quality metrics (escaped defects, flaky rate, coverage of critical flows); and plan exploratory, performance and security testing.
31Which quality metrics do you track?
SeniorEscaped defects (bugs found in production) and their severity, time to detect and fix, flaky test rate, automated coverage of critical flows, and test suite duration. Use them to improve the process, not to judge individuals.
32Tell me about the most interesting bug you found.
MidPick one that shows skill: how you noticed it, how you narrowed it down, the root cause, the impact, and what you changed to catch similar bugs earlier. Use the STAR method.
How to prepare
- Practice “how would you test…” questionsStructure: requirements, functional, boundaries, negative, non-functional, priorities.
- Bring a strong bug report exampleClear steps, expected vs actual, evidence.
- Write automation liveA Playwright or Selenium UI test and an API test, with good selectors and assertions.
- Know your pipelineHow tests run in CI and how you deal with flaky tests.
- Prepare a strategy storyHow you improved quality on a team, with a metric.
Get answer points in real time during your interview
Sottena listens to the interviewer, detects each question and shows short answer points in about a second. 150 free credits, no card required.