Interview questions
QA engineer interview questions
QA interviews are about how you think about risk. Interviewers want to see that you can find the bugs that matter, describe them so developers can fix them, and decide when a release is good enough to ship.
Questions by stage and what a strong answer includes
- 01
Is your experience mostly manual testing, automation or both?
Strong answer: An honest split with tools: Playwright, Cypress, Selenium, Postman, JMeter, and the language you write tests in. Say how many tests you maintained and how often they ran.
- 02
What products and platforms have you tested?
Strong answer: Web, mobile, APIs, payments, data pipelines. Mention the release cadence: weekly mobile releases call for different habits than quarterly enterprise drops.
- 03
Tell me about the most important bug you found.
Strong answer: How you found it, why it mattered (money, data, security, many users), how you reported it and what happened. Bonus if it changed how the team tests.
- 04
Describe a time a developer said your bug was not a bug.
Strong answer: How you checked the requirement, gathered evidence, involved the product owner if needed, and kept the relationship professional.
- 05
Write test cases for a login form.
Strong answer: Positive and negative paths, boundaries, empty fields, wrong password lockout, password reset link, session handling, security (SQL injection, rate limiting) and accessibility. Prioritize by risk.
- 06
What makes a good bug report?
Strong answer: Clear title, steps to reproduce, expected versus actual result, environment and build, severity and priority, logs or a screen recording. One bug per report.
- 07
How do you decide what to automate?
Strong answer: Stable, repeated, high-value flows such as regression and smoke tests. Not features still changing weekly or one-off checks. Mention the test pyramid and flaky test handling.
- 08
How would you test a REST API endpoint that creates an order?
Strong answer: Status codes, schema validation, required and invalid fields, authorization, idempotency, concurrency and side effects in the database or downstream services.
- 09
The release is tomorrow and you found a medium-severity bug. What do you do?
Strong answer: Assess impact and workaround, share facts with the product owner and engineering lead, recommend ship, fix forward or delay, and document the decision. QA informs, the team decides.
- 10
Our automated suite is flaky. Where do you start?
Strong answer: Measure which tests fail and how often, quarantine the worst, fix waits and test data isolation, and track flakiness as a team metric.
- 11
Where do you want to grow: automation, performance, a lead role?
Strong answer: A concrete direction and what you are learning toward it. It helps the company place you and justify the level.
One answer, before and after
Tell me about the most important bug you found.
Weak answer
I found a lot of critical bugs. One was in payments and it was very serious. I reported it and the developers fixed it before release.
Strong answer in STAR
- Situation
- During regression for a subscription app, I was testing plan upgrades on a staging build two days before release.
- Task
- My task was the standard upgrade checklist, but I wanted to check what happened when a user upgraded and downgraded within the same billing period.
- Action
- I found that a downgrade on the same day refunded the full price of the higher plan while keeping its features active until the end of the period. I reproduced it three times, attached API logs and a short recording, marked it critical and flagged it in the release channel with an estimate of exposure.
- Result
- The release was held for one day and the fix shipped with it. Finance estimated that, at the previous month's upgrade volume, the bug could have cost around $8,000 a month. I added the scenario to the automated regression suite.
Why it works
The weak answer claims importance without showing it. The strong one shows curiosity beyond the checklist, a reproducible report, business impact and prevention. Numbers in the example are illustrative: use your own.
How a practice session works
- 01
Pick a stage, paste the job posting
Recruiter screen, HR interview, hiring manager, final round or offer talk. Add the posting and your resume so the questions are about your role, not generic.
- 02
Talk it through by voice
The interviewer speaks the language you chose, interrupts, follows up and digs into details like on a real call. If the connection drops, you pick up where you stopped.
- 03
Get the review and drills
A score, 7 skills, what you said next to a stronger way to say it, plus pace, filler words and talk share. Weak spots turn into short drills.