Answer structure
Definition, context, example, risk, and conclusion.
Mock interview
QA interview question bank by topic
Practice popular manual QA, automation, API, documentation, Agile, and AI-for-QA questions with answer anchors and short drills.
9
topic groups
29
questions
Evidence mindset
Tie answers to requirements, expected results, and user impact.
Hiring signal
Show how you think, not only what terms you memorized.
QA Foundations
Core vocabulary, QA mindset, and risk-based thinking.
1. What is the difference between QA, QC, and testing?
Strong answer anchor
QA improves the process that creates quality, QC evaluates the product quality, and testing is one QC activity that finds information about product risk.
Practice drill
Give one example of a QA activity and one example of a testing activity from a sprint.
2. Why is software testing important?
Strong answer anchor
Testing reduces uncertainty before release by checking critical user flows, finding defects, validating requirements, and giving stakeholders evidence for decisions.
Practice drill
Explain testing value without saying that testers guarantee a bug-free product.
3. What is a defect, error, failure, and root cause?
Strong answer anchor
An error is a human mistake, a defect is the flaw introduced into the product, a failure is incorrect behavior observed during execution, and a root cause is the deeper reason the problem happened.
Practice drill
Use a checkout validation bug to connect all four terms.
SDLC and STLC
How QA work fits into delivery and release flow.
1. What are the main STLC phases?
Strong answer anchor
Requirement analysis, test planning, test design, test environment setup, test execution, defect tracking, retesting, regression, and test closure.
Practice drill
Name one deliverable from each phase.
2. When should QA start testing work?
Strong answer anchor
QA should start as early as possible during requirement analysis, before code is ready, because many defects can be prevented by clarifying assumptions and risks early.
Practice drill
Describe what you would ask during a story refinement meeting.
3. What are entry and exit criteria?
Strong answer anchor
Entry criteria define what must be ready before testing starts. Exit criteria define the conditions for finishing testing or recommending release.
Practice drill
Create entry and exit criteria for a login feature.
Test Design
Scenarios, cases, coverage, and test techniques.
1. What is the difference between a test scenario and a test case?
Strong answer anchor
A scenario is a high-level user situation or flow to test. A test case is detailed and includes preconditions, steps, data, and expected results.
Practice drill
Turn 'user resets password' into two scenarios and one detailed test case.
2. How do equivalence partitioning and boundary value analysis work?
Strong answer anchor
Equivalence partitioning groups inputs expected to behave similarly. Boundary value analysis checks values at and around edges where defects are common.
Practice drill
Apply both techniques to an age field that accepts 18 through 65.
3. What is a decision table?
Strong answer anchor
A decision table maps combinations of conditions to expected actions, making complex business rules easier to cover without missing important combinations.
Practice drill
Draft a decision table for free shipping based on country, cart total, and membership.
4. What is a traceability matrix?
Strong answer anchor
A traceability matrix connects requirements to scenarios, test cases, defects, and execution status so the team can see coverage and impact of changes.
Practice drill
Explain how you would use it when a requirement changes.
QA Documentation
Checklists, test plans, test cases, bug reports, and summary reports.
1. What makes a good test case?
Strong answer anchor
It has a clear objective, preconditions, reliable test data, precise steps, observable expected results, priority, and enough detail for another tester to execute it.
Practice drill
Improve a vague expected result like 'works correctly'.
2. When would you use a checklist instead of detailed test cases?
Strong answer anchor
Use a checklist for exploratory, smoke, regression, or repeated lightweight checks where experienced testers need coverage guidance without heavy step-by-step scripts.
Practice drill
Create five smoke checklist items for a course catalog.
3. What should a test plan include?
Strong answer anchor
Objective, scope, out-of-scope areas, approach, environments, test data, roles, schedule, risks, entry criteria, exit criteria, and deliverables.
Practice drill
Name three risks for testing payments.
4. What makes a bug report useful?
Strong answer anchor
A useful bug report is reproducible, factual, specific, prioritized by impact, and includes environment, steps, actual result, expected result, and evidence.
Practice drill
Rewrite 'button broken' as a professional bug title.
Testing Types
Functional, non-functional, smoke, sanity, regression, retesting, usability, and compatibility.
1. What is the difference between smoke and sanity testing?
Strong answer anchor
Smoke testing checks whether a build is stable enough for deeper testing. Sanity testing checks whether a specific change or fix behaves reasonably.
Practice drill
Give one smoke check and one sanity check after a login bug fix.
2. What is the difference between regression testing and retesting?
Strong answer anchor
Retesting verifies that a specific defect was fixed. Regression testing checks that recent changes did not break existing functionality.
Practice drill
Explain why both can be needed after fixing checkout.
3. What non-functional testing types do you know?
Strong answer anchor
Performance, security, usability, accessibility, reliability, compatibility, localization, scalability, and maintainability-related checks.
Practice drill
Pick three non-functional risks for a learning platform.
API and Web Testing
HTTP, REST, Postman, JSON, status codes, and browser behavior.
1. What do common HTTP methods mean?
Strong answer anchor
GET reads data, POST creates or submits data, PUT replaces a resource, PATCH updates part of a resource, and DELETE removes a resource.
Practice drill
Choose methods for login, update profile, and delete homework draft.
2. How do you test an API endpoint?
Strong answer anchor
Check status code, response schema, required fields, validation, authorization, negative cases, boundary data, error messages, headers, and side effects in the system.
Practice drill
List negative API tests for registration.
3. What is the difference between 400, 401, 403, 404, and 500?
Strong answer anchor
400 means bad request, 401 unauthenticated, 403 authenticated but forbidden, 404 not found, and 500 server-side failure.
Practice drill
Map each status code to a realistic user profile API case.
SQL, Git, Jira, and Agile
Daily tools expected from a manual QA engineer.
1. Why does a QA engineer need basic SQL?
Strong answer anchor
SQL helps verify stored data, prepare test data, investigate defects, and confirm backend state when UI behavior is not enough evidence.
Practice drill
Explain when you would use SELECT and JOIN during testing.
2. How do QA engineers use Git?
Strong answer anchor
QA engineers use Git to read changes, switch branches, run test builds, review test automation, and understand what changed before regression testing.
Practice drill
Describe how a changed branch can affect your test scope.
3. What information should QA add to a Jira ticket?
Strong answer anchor
QA should add test notes, questions, acceptance criteria gaps, linked test cases, found defects, retest results, and release risk comments.
Practice drill
Write a short QA comment for a story with unclear validation rules.
Automation Basics
Selectors, assertions, waits, test structure, and maintainability.
1. What makes a good locator?
Strong answer anchor
A good locator is stable, readable, close to user intent, and resistant to visual or layout changes. Test IDs, roles, labels, and accessible names are often better than brittle XPath.
Practice drill
Compare CSS class, XPath by index, and data-testid for a login button.
2. Why are assertions important in automation?
Strong answer anchor
Assertions turn actions into checks. Without assertions, a script may click through the app without proving the expected behavior happened.
Practice drill
Add three assertions to an automated login test.
3. How do you reduce flaky tests?
Strong answer anchor
Use stable locators, meaningful waits, isolated test data, clear assertions, independent tests, controlled environment setup, and good failure evidence.
Practice drill
Name two reasons a UI test may pass locally but fail in CI.
AI for QA
Using AI responsibly for analysis, test generation, and review.
1. How can QA engineers use AI safely?
Strong answer anchor
Use AI for drafts, brainstorming, edge cases, summaries, and test data ideas, but verify output against requirements, product behavior, privacy rules, and QA judgment.
Practice drill
Name two things you must never paste into an AI tool.
2. How do you verify AI-generated test cases?
Strong answer anchor
Check requirement coverage, assumptions, expected results, duplicates, missing negative cases, realistic data, and whether each case is executable.
Practice drill
Create a review checklist for AI-generated registration tests.
3. What are the risks of AI in QA?
Strong answer anchor
AI may invent requirements, miss product context, expose confidential data, produce shallow cases, or create false confidence if the output is not reviewed.
Practice drill
Give an example of a hallucinated requirement.