QA and software testing interviews test something subtle: a testing mindset. Beyond knowing tools and terminology, interviewers want to see whether you think about edge cases, ambiguity, and what could break — and whether you can communicate a bug clearly. Here are the QA tester interview questions that actually get asked, with answers.
Testing fundamentals
- Difference between verification and validation.
- SDLC vs STLC (software testing life cycle).
- Functional vs non-functional testing.
- Smoke vs sanity testing; regression vs retesting.
- Black-box vs white-box vs grey-box testing.
Test design
- What is a test case, and what makes a good one?
- Test case vs test scenario vs test plan.
- Boundary value analysis and equivalence partitioning.
- "How would you test a login page / a pen / a lift?" — the classic edge-case thinking question.
Bug reporting
- What does a good bug report contain?
- Bug life cycle (states from new to closed).
- Severity vs priority — with examples.
- What do you do when developers say "it's not a bug"?
Automation
- When should you automate vs test manually?
- Selenium basics; what is a framework (data-driven, keyword-driven, BDD)?
- What makes a test flaky, and how do you fix it?
How to prepare
The "how would you test X" and bug-communication questions are verbal and judgment-based. Practise reasoning through test scenarios out loud. Greenroom runs spoken technical interviews that follow up on your reasoning and give feedback on clarity. Pair it with our explain-your-project guide.
Frequently asked questions
What questions are asked in a QA tester interview?
QA interviews cover testing fundamentals (verification vs validation, SDLC vs STLC, functional vs non-functional, smoke vs sanity, black-box vs white-box), test design (good test cases, boundary value analysis, equivalence partitioning, 'how would you test X'), bug reporting (bug life cycle, severity vs priority), and automation basics (when to automate, Selenium, test frameworks and flaky tests).
What is the difference between severity and priority?
Severity describes the technical impact of a bug on the system — how badly it breaks functionality — while priority describes how urgently it should be fixed from a business perspective. A crash on a rarely used screen may be high severity but low priority, whereas a misspelled company name on the homepage may be low severity but high priority.
How would you test a login page?
Cover positive cases (valid credentials log in), negative cases (wrong password, empty fields, invalid email format), boundary and security cases (very long inputs, SQL injection, brute-force lockout), UI/UX (error messages, password masking, remember-me), and non-functional aspects (load time, behavior on slow networks, accessibility). The question tests how many edge cases you naturally surface and how clearly you organize them.
How should I prepare for a QA interview?
Learn testing fundamentals, test design techniques and the bug life cycle, but focus on developing a testing mindset — surfacing edge cases and ambiguity — since 'how would you test X' and bug-communication questions carry real weight. Practise reasoning through test scenarios out loud, ideally with a voice-based mock interview that follows up on your reasoning.