QA Interview Questions for Manual and Automation Roles

Whether you are preparing for a QA interview or hiring a QA engineer, strong questions reveal how someone thinks about risk, evidence, and collaboration — not whether they memorized definitions. Below is a practical question bank I recommend for manual QA, automation, and senior/lead conversations, with notes on what a solid answer usually includes.

Fundamentals

1. What is the difference between verification and validation?
2. How do you decide what not to test when time is limited?
3. Explain severity vs priority with a real example.
4. What is a good regression strategy for a weekly release?
5. How do you know a build is “good enough” to ship?

Test design & planning

1. How do you write a lightweight test plan for a feature release?
2. Walk me through boundary value and equivalence partitioning with an example.
3. How do you approach exploratory testing without making it random?
4. What artifacts do you produce before UAT?
5. How do you handle changing requirements mid-cycle?

Bug reporting & communication

1. What makes a bug report easy for a developer to act on?
2. How do you report an intermittent defect?
3. Tell me about a time you disagreed with a “low priority” decision.
4. How do you communicate release risk to a non-technical stakeholder?
5. What evidence do you attach by default (and why)?

Web, API & data

1. How do you test authentication and session expiry?
2. What is Broken Object Level Authorization, and how would you test for it?
3. How do you combine Postman checks with SQL validation?
4. What do you look for in API error responses?
5. How would you validate an export/download feature end-to-end?

Mobile QA

1. What do you test on real devices that emulators often miss?
2. How do you validate permission deny paths on iOS/Android?
3. What is your approach to background/foreground and interruption testing?
4. How do you plan a device/OS matrix with limited time?
5. What does a TestFlight / APK smoke checklist include before release?

Automation & Playwright

1. What should be automated first in a mature product?
2. How do you choose locators in Playwright?
3. How do you reduce flaky tests?
4. Explain smoke vs regression automation in CI.
5. When would you not automate a scenario?
6. How do you debug a failing CI test with traces/reports?

Sample prompt in an interview:
"Design a smoke pack for an eCommerce checkout redesign.
What 8–12 checks do you automate in Playwright, and what do you keep manual?"

Security & accessibility awareness

1. What security checks can QA perform without being a penetration tester?
2. How would you test for basic privilege escalation?
3. What accessibility checks can you run in a normal regression cycle?
4. How do you handle a suspected privacy/security issue during testing?

Senior / lead judgment

1. How do you mentor junior QA engineers on bug quality?
2. How do you balance speed and quality under release pressure?
3. Describe a production bug you helped prevent — what signal did you trust?
4. How do you measure whether QA is effective for a team?
5. How do you partner with developers and product managers day to day?

What interviewers should listen for

• Clear risk-based thinking
• Reproducible examples from real work
• Comfort with both manual depth and automation judgment
• Collaboration tone (not “QA vs Dev”)
• Honesty about tradeoffs and unknowns

If you are preparing as a candidate, practice answering with a short story: context → action → result → what you would improve next time. If you are hiring, ask follow-ups on those stories — that is where real seniority shows.