Mock Interview Copilot Interview questions by role
QA tester interview questions
QA tester and software testing interviews check whether you can find the problems that matter before users do, and communicate them clearly. Expect a "how would you test this?" exercise, questions on writing bug reports, choosing what to automate, testing under time pressure and working with developers who disagree with your findings.
How the interview usually runs
After a screening call, most QA interviews include a practical test-design exercise: test a login form, a lift, a search box or a feature from the company's own product. Automation roles add questions on frameworks, flaky tests and where automation fits in the pipeline. A final round usually covers teamwork with developers and product owners.
The exercise is where candidates win or lose. Listing fifty test cases is less impressive than grouping them, starting with the riskiest, and asking what the feature is supposed to do before testing it.
Common questions and what the interviewer is checking
How would you test a login page?
What they are checking: Breadth and prioritisation: valid and invalid credentials, lockout, password reset, accessibility, security basics, different browsers and devices, and which tests you would run first.
What makes a good bug report?
What they are checking: Clear title, steps to reproduce, expected and actual results, environment, evidence, and a sensible severity, written so a developer can act without asking questions.
How do you decide what to automate?
What they are checking: Automating stable, repeated, high-value checks, keeping exploratory testing for new or changing areas, and awareness of the maintenance cost.
A developer says your bug is not a bug. What do you do?
What they are checking: Going back to the requirement or the user impact, involving the product owner if needed, and keeping the relationship constructive.
You have one day to test a release that needed a week. What do you do?
What they are checking: Risk-based testing: focus on the changed areas and critical user journeys, communicate what will not be tested, and let the team make an informed decision.
How do you deal with flaky automated tests?
What they are checking: Investigating the cause (timing, test data, environment) rather than adding retries, and quarantining tests so the suite stays trusted.
What is the difference between regression, smoke and exploratory testing?
What they are checking: Fundamentals, and knowing when each one is the right tool.
Tell me about the most important bug you found.
What they are checking: What made it important (user or business impact), how you found it, and how you made sure it was fixed and stayed fixed.
How do you test something with no written requirements?
What they are checking: Asking questions, using comparable products and user expectations, writing down your assumptions and getting them confirmed.
How to structure a strong answer
For "how would you test this" questions, start by asking what the feature must do and who uses it. Then group your tests into categories and say which you would run first and why. For experience questions, emphasise the impact of what you found.
- Clarify the requirement and the users.
- Group tests: functional, edge cases, negative, non-functional.
- Prioritise by risk and say what you would run first.
- Say how you would report and track what you find.
Example answer
Tell me about the most important bug you found.
Just before a release, I was exploring the checkout on a slow mobile connection rather than office Wi-Fi. If you pressed "Pay" and the response took a few seconds, the button stayed active, and pressing it again created a second order and a second charge.
I recorded a video, wrote the steps with the network throttling settings, and marked it as critical because it charged customers twice. The developer fixed it by disabling the button and making the payment request idempotent on the server. I added an automated test that simulated a slow response and a double tap, so it would be caught if it ever came back. It changed how we test: slow networks became part of our standard checklist.
Mistakes to avoid
- Listing test cases at random without grouping or prioritising them.
- Writing bug reports that say "it doesn't work" with no steps or evidence.
- Saying you would automate everything.
- Treating developers as opponents rather than teammates.
- Quietly skipping tests under pressure instead of telling the team what was not covered.
Frequently asked questions
What questions are asked in a QA tester interview?
Expect a test-design exercise such as testing a login page, questions about writing bug reports, types of testing, what to automate, flaky tests, testing under tight deadlines, and handling disagreements with developers.
How do I answer "how would you test a pen" or a lift?
Ask about the requirements and the users first, then group your tests: core function, edge cases, misuse, durability or performance, safety and accessibility. Prioritise and explain why. Interviewers are checking how you think, not how many cases you list.
Do QA interviews include coding?
Manual testing roles usually do not. Automation roles often ask you to write or read test code, discuss a framework and explain how you keep tests reliable.
What should a beginner say without testing experience?
Show the tester's mindset with examples: bugs you noticed in apps you use, how you would report them, and any practice projects where you wrote test cases or automated tests.