Interview questionsUpdated 12 Oct 2026 · Team InterviewPlan

QA Engineer Interview Questions and Answers

QA engineer interviews test how you think about quality: how you design tests, find the defects that matter and work with developers in fast Agile releases. These questions reflect what manual and hybrid QA engineers are asked in 2026 at services firms, banks and product companies, with model answers based on real testing work.

What interviewers test in a QA engineer interview

Interviewers want to see a tester's mindset: curiosity, attention to detail and the ability to prioritise. Many rounds give you a feature, like a login page or a payment form, and ask you to list test cases on the spot.

Expect questions about collaboration too: how you handle a developer who rejects your bug, and how you decide what to test when time is short.

  • Fundamentals: STLC, SDLC, test levels and test types
  • Test design: BVA, equivalence partitioning, decision tables and state transitions
  • Defects: lifecycle, severity, priority and clear reporting
  • Technical skills: API testing, SQL, browser dev tools and logs
  • Process: Agile QA, regression planning and release sign-off

Technical topics to revise

Practise writing test cases for everyday features and testing a public API with Postman. Be ready to explain how you would test something without written requirements.

  • Boundary value analysis, equivalence partitioning and pairwise testing
  • Smoke, sanity, regression, integration, system and UAT
  • Jira and test management tools like Zephyr, Xray or TestRail
  • Postman: requests, status codes, assertions, environments and collections
  • SQL: SELECT, JOIN and validating backend data after UI actions
  • Browser dev tools: network tab, console errors and responsive modes
  • Basics of automation with Selenium or Playwright
  • Performance and security testing awareness: JMeter and OWASP basics

How to structure your answers

For test design questions, group cases by type: functional positive, negative, boundary, UI, security, performance and compatibility. This shows structure and coverage.

For scenario questions, use STAR and quantify impact, such as defects found before release, reduced leakage to production or time saved in regression.

How InterviewPlan AI helps you prepare

QA mock interviews ask test design, scenario and tool questions and give feedback on coverage and clarity. Resume AI helps show impact, like lower defect leakage, and the Behavioral Coach prepares stories about disagreements with developers.

Interview Copilot provides live speaker-labelled transcription and resume-based drafts during interviews. After joining, QA Testing Job Support gives expert-plus-AI help in your first 90 days. Start free with 5 live Copilot minutes and 100 AI credits.

Questions and model answers

9 questions you are likely to hear.

  1. How would you test a login page?

    Why they ask: This classic question tests coverage, structure and security awareness.

    Sample answer: I would group test cases. Functional: valid login, invalid password, unregistered email, empty fields, case sensitivity and password reset link. Boundary: minimum and maximum password lengths. Security: password masked, SQL injection and script inputs rejected, account lockout after several failures, session timeout and no credentials in URLs. UI and accessibility: tab order, error messages and screen reader labels. Compatibility: major browsers and mobile. Performance: response time under load. I would also check the backend with SQL to confirm failed attempts are logged. On a banking project, the lockout tests found that the counter reset on page refresh.

  2. What is the difference between severity and priority? Give examples.

    Why they ask: This checks defect triage understanding.

    Sample answer: Severity is the technical impact of a defect on the system, while priority is how urgently the business needs it fixed. A crash in a rarely used admin report is high severity but may be low priority if nobody needs that report this month. A spelling mistake in the company name on the homepage is low severity but high priority because of brand impact. I set severity myself based on impact, and agree priority with the product owner in triage. Keeping them separate makes release decisions much clearer.

  3. How do you write a good bug report?

    Why they ask: Bug report quality directly affects how fast defects are fixed.

    Sample answer: A good report has a clear title stating what is wrong and where, for example payment fails with UPI on Android checkout. It includes the environment and build, precise steps to reproduce, expected versus actual results, and evidence like screenshots, screen recordings, console errors or network responses. I add severity, test data used and whether it is a regression. I keep one defect per report. Developers in my team said they could usually fix my bugs without asking questions, which cut the back-and-forth significantly during busy release weeks.

  4. Explain boundary value analysis with an example.

    Why they ask: Interviewers check practical knowledge of test design techniques.

    Sample answer: Boundary value analysis tests at and around the edges of valid input ranges, because defects cluster there. If an age field accepts 18 to 60, I test 17, 18, 19, 59, 60 and 61. Combined with equivalence partitioning, I also pick one value from each class, like 35 as valid and negative numbers or text as invalid. In a loan application, BVA on the amount field found that the maximum of 10 lakh was rejected because the developer used less than instead of less than or equal to, which would have blocked real customers.

  5. Release is tomorrow and you have found a major defect. What do you do?

    Why they ask: This scenario tests communication and risk judgement.

    Sample answer: I would reproduce it reliably, document impact clearly and inform the developer and product owner immediately, not wait for the daily stand-up. I would explain who is affected, how often and whether a workaround exists. The decision to delay, release with a fix, or release with the feature disabled belongs to the product owner, but I provide the facts. In one release, a defect broke invoice downloads for a specific browser. We shipped with a feature flag disabling that path, added a notice, and fixed it in a patch two days later.

  6. How do you test an API with Postman?

    Why they ask: API testing is now expected even for manual QA roles.

    Sample answer: I set up an environment with base URLs and tokens, then build a collection covering each endpoint. For each request I check the status code, response time, response body schema and key field values with Postman test scripts. I cover positive cases, missing or invalid fields, wrong data types, unauthorised access and boundary values. I chain requests using variables, for example creating an order and then fetching it by the returned ID. I run collections with Newman in the CI pipeline. API tests caught several issues earlier than UI testing would have in my last project.

  7. How do you decide what to include in regression testing when time is limited?

    Why they ask: Risk-based prioritisation is a key senior QA skill.

    Sample answer: I use risk-based testing. I prioritise areas touched by the current changes, core business flows like login, search, checkout and payments, areas with a history of defects and integrations with external systems. I check with developers which modules their changes affect. Lower-risk areas get a quick sanity check. I keep the regression suite tagged by priority so I can run P1 tests in a few hours. At an ecommerce client, this approach let us cut a three-day regression cycle to one day for hotfix releases without production escapes.

  8. A developer says your bug is not a bug. How do you handle it?

    Why they ask: This tests collaboration and evidence-based communication.

    Sample answer: I first make sure I understand their view, then go back to the source of truth: the requirements, acceptance criteria or design. If the expected behaviour is documented, I share it calmly with my evidence. If it is not documented, I bring in the product owner or BA to decide, because it is a requirement question rather than an argument between us. In one case a developer argued that a date filter excluding the end date was correct; the BA confirmed users expected it to be inclusive, and we also updated the acceptance criteria to avoid repeats.

  9. Tell me about a critical defect you found that others missed.

    Why they ask: This shows thoroughness and the impact of your testing.

    Sample answer: While testing a fund transfer feature at a banking client, all functional tests passed. I tried a double-click on the confirm button with network throttling in dev tools, and the transfer was submitted twice. Nobody had tested slow network behaviour. I logged it as critical with a screen recording and network evidence. The developers added button disabling and an idempotency key on the API. That defect would have caused duplicate debits in production. I added slow network and double-submit checks to our standard test checklist for all transaction features.

FAQ

Questions people ask about qa engineer.

Do QA engineers need automation skills in 2026?

Most QA roles now expect at least basic automation or API testing. Manual testing skills remain important for exploratory and UAT work, but knowing Selenium, Playwright or Postman and some SQL makes you far more competitive.

Is ISTQB certification useful for QA interviews?

ISTQB Foundation helps with terminology and screening, especially at large services companies. Interviewers still focus on practical test design and real examples, so pair the certification with stories from projects.

What tools should QA freshers learn?

Learn Jira for defect tracking, a test management tool, Postman for APIs, basic SQL, browser dev tools and the basics of Selenium or Playwright. Practise on public demo sites and document test cases as a portfolio.

Is QA job support available after I get hired?

Yes. InterviewPlan AI's QA Testing and Selenium Job Support offer live expert-plus-AI help in your first 90 days with test plans, scripts and tickets. It costs $5 per hour with 200 AI credits included.

P.S.

Reading helps. Practising out loud helps more.

Start free with 5 live minutes and 100 AI credits for Resume AI, Job Search, Auto-Apply, mock interviews and Behavioral Coach.