What interviewers expect
Interviewers usually listen for how you break down the problem: happy path, negative cases, edge cases, security, data, backend behavior, UX, accessibility, performance, and how clearly you explain tradeoffs.
QA interview guide
QA interview test design questions
Many QA interviews include broad prompts such as: how would you test this feature? The strongest answers are structured, risk-based, and specific enough to show real testing judgment.
Checklist
What to include in your answer
Start with the core user goal
- Explain the main happy path before jumping into edge cases.
- Name the expected result and what data should change.
- Mention the most important user or business risk.
Add negative and edge cases
- Cover empty, invalid, duplicate, expired, slow, retry, and interrupted states.
- Include account states, permissions, or role boundaries where relevant.
- Think about what happens after refresh, back button, duplicate submit, or network failure.
Go deeper than UI
- Mention API status codes, backend validation, persistence, events, logs, and data consistency.
- Include security risks like authorization, brute force, sensitive data exposure, or mass assignment.
- Add performance and observability checks for critical flows.
Explain user experience
- Cover loading states, clear errors, recovery paths, mobile layout, and accessibility.
- Mention keyboard navigation, labels, focus states, and screen reader behavior.
- Keep the answer organized instead of listing random cases.
“I would test valid and invalid inputs.”
What it misses
This is too broad. It does not show feature-specific risks, backend thinking, security awareness, data consistency, or user recovery.
“I would start with the core happy path and expected data changes, then cover validation, negative cases, edge cases, permissions, security, backend status codes, persistence, API failures, duplicate submit, retries, UX messages, loading states, accessibility, mobile behavior, performance, and observability. I would prioritize the risks that can block users, leak data, corrupt data, or create money/security impact.”
Ready to practice?
Write your own answer, get scored, see what you missed, and compare it with junior, middle, and senior QA thinking.