QA Engineer mock interview questions
19 questions a QA Engineer panel actually asks, with what each one tests and what a strong answer contains, then practice any of them live. Test design, automation and release judgment rounds for QA engineer interviews.
Answer one real QA Engineer question now
A question a QA Engineer panel actually asks, answered out loud, scored on what you said and how you said it. Under two minutes, and nothing to sign up for.
“We are adding a discount code field to checkout. How would you test it?”
We never store the audio. Your answer is deleted within 24 hours unless you save the result.
- Adaptive follow-ups, not a fixed question list
- Rubric scorecard with evidence from your answers
- Voice or text, with delivery coaching on voice sessions
Thinking past the interview? Carmen can help with your whole QA Engineer career: a switch, a raise, or what comes next.
19 qa engineer mock interview questions
The questions a QA Engineer panel actually asks, with what each one is testing and what a strong answer contains. Click any question to run it in a live session: your AI interviewer will cover it and score how you answer.
- 1.
We are adding a discount code field to checkout. How would you test it?
Why they ask it: The classic QA test design question. It shows whether you think in risks and cases, not just the happy path.
A strong answer: Start by asking about the rules: stacking, expiry, minimum order, per-user limits, currency and case sensitivity. Then cover valid and invalid codes, boundary values, expired and future codes, codes applied then items removed, rounding of totals, concurrency such as a single-use code used twice at once, security such as brute forcing codes, accessibility, and how it looks on mobile. Decide which cases to automate at the API level and which to test manually.
- 2.
A test in the CI pipeline fails about one run in ten. What do you do?
Why they ask it: Flaky tests damage trust in automation. The interviewer wants investigation, not endless retries.
A strong answer: Quarantine it so it stops blocking others while tracked, gather failure logs, screenshots and timing, look for common causes such as fixed sleeps instead of waiting for conditions, shared test data, dependence on test order, time zones, or real network calls, fix the cause, and track flakiness across the suite so it does not build up.
- 3.
How do you decide what to automate and at which level?
Why they ask it: Tests understanding of test strategy and cost.
A strong answer: Automate stable, repeated and high-risk checks. Put most logic checks at the unit and API level where tests are fast and reliable, keep end to end UI tests for a small set of critical user journeys, and leave exploratory testing for new or changing features. Consider maintenance cost and how quickly tests give feedback.
- 4.
Write a good bug report for a checkout that sometimes charges the customer but shows an error.
Why they ask it: Bug reporting quality affects how quickly issues get fixed.
A strong answer: A clear title, environment and version, exact steps, expected and actual results, how often it happens, evidence such as screenshots, logs, request IDs and timestamps, the business impact such as double charges, and a severity level with reasoning. Note what you have already ruled out.
- 5.
The release is tomorrow and you have found several bugs, and there is not time to test everything. What do you do?
Why they ask it: Release pressure is the real test of a QA engineer's judgment.
A strong answer: Prioritise testing by risk and user impact, summarise the open bugs with severity and impact in plain language, give the team clear information about what was and was not tested, recommend which bugs must block the release, and let the decision be made with full information rather than hiding risk or blocking by default.
- 6.
How do you test an API, and what do you check beyond the response status?
Why they ask it: API testing is a core skill that catches bugs before the UI.
A strong answer: Check response bodies against the contract or schema, data correctness in the database, error handling for invalid input, authentication and authorisation for different roles, idempotency where relevant, pagination and edge cases, performance of key endpoints, and behaviour when dependencies fail.
- 7.
Tell me about a bug you found that others missed. How did you find it?
Why they ask it: Tests curiosity and exploratory skill.
A strong answer: The feature, the thinking that led you to the bug such as questioning an assumption, trying unusual data or combining features, the impact had it shipped, and how you made sure similar bugs would be caught in future.
How the QA Engineer interview runs
Usually a recruiter screen, then a technical round on test design where you are given a feature or a product and asked how you would test it. Most loops include an automation exercise, such as writing UI or API tests in a common framework, and questions on flaky tests and test strategy. Later rounds cover working with developers and product managers, reporting bugs, and making release decisions under time pressure.
What the panel scores
Test design
Whether you find the important cases for a feature.
- Asks about requirements before testing
- Covers boundaries, errors and concurrency
- Thinks about security and accessibility
Automation
Whether automated tests are reliable and valuable.
- Chooses the right test level
- Fixes the root cause of flaky tests
- Writes maintainable test code
Risk and release judgment
Whether you help teams make good release decisions.
- Prioritises testing by risk
- Communicates what was not tested
- Recommends clearly without hiding risk
Communication
Whether bugs and findings lead to action.
- Writes clear, reproducible bug reports
- Explains business impact
- Works constructively with developers
Common questions in every interview
These come up in almost every QA Engineer interview regardless of the company or the round.
- 8.
Tell me about yourself.
Why they ask it: Opens the interview and sets the frame. The interviewer is checking whether you can select what matters for this job rather than narrate your whole history.
A strong answer: A 60-90 second arc: where you are now, one or two proof points that match the posting, and why this role is the logical next step. Present, past, then future.
- 9.
Why do you want this role?
Why they ask it: Tests whether you read the job description or mass-applied. Weak answers are about what the candidate gets; strong answers connect to the work itself.
A strong answer: Two specifics from the posting or the company's actual work, plus an honest line about what you want to get better at here.
- 10.
Walk me through your resume.
Why they ask it: Checks that your story holds together and that the transitions were deliberate rather than accidental.
A strong answer: Chronological but fast, with a reason attached to each move and more time on the roles closest to this one.
- 11.
Tell me about a time you failed.
Why they ask it: Tests self-awareness and whether you own outcomes. Interviewers are listening for a real failure, not a disguised strength.
A strong answer: A genuine miss, what you specifically got wrong, the cost, and the concrete thing you changed afterwards that has since held up.
- 12.
Tell me about a conflict with a coworker or manager.
Why they ask it: Predicts how you behave when the team disagrees. The trap is blaming the other person.
A strong answer: The substance of the disagreement, what you did to understand their position, how it resolved, and what the working relationship looked like after.
- 13.
What's your greatest strength?
Why they ask it: Checks whether you know what you're actually good at and can prove it.
A strong answer: One strength that maps to the posting, plus a short example where it produced a measurable result.
- 14.
What's your greatest weakness?
Why they ask it: Tests honesty and whether you're actively working on something. Rehearsed non-answers ('I work too hard') read as evasive.
A strong answer: A real limitation that isn't core to the job, the system you built to manage it, and evidence it's improving.
- 15.
Tell me about a time you had to influence someone without authority.
Why they ask it: Almost every role depends on getting people who don't report to you to change course.
A strong answer: What you wanted, why they resisted, the evidence or framing that moved them, and what actually shipped as a result.
- 16.
Where do you see yourself in five years?
Why they ask it: Tests whether this job fits your trajectory, which is a retention question in disguise.
A strong answer: A direction rather than a title, and a line about the skills this role would build toward it. Vague ambition and rigid title-chasing both land badly.
- 17.
Why are you leaving your current job?
Why they ask it: Screens for red flags. Interviewers listen for how you talk about people you no longer work with.
A strong answer: Forward-looking and specific about what you're moving toward. Criticism of a former employer costs you more than it gains, even when it's deserved.
- 18.
What are your salary expectations?
Why they ask it: Checks whether you've done market research and whether you're in range before anyone spends more time.
A strong answer: A researched range with your target near the bottom of it, framed against the scope of the role. Deflect once if the posting has no band, then answer.
- 19.
Do you have any questions for us?
Why they ask it: The most under-prepared question in the interview, and the one that most changes the final impression.
A strong answer: Two or three questions about how the team actually works: what the first 90 days look like, how success is measured, what the hardest part of the job is.
Every round ends in a scorecard like this
Your QA Engineer answers, quoted back, scored on what this role is judged on, with the line to say instead.
Real screen from the app. Sample from a product design round.
Related roles
All Engineering →No spam. Unsubscribe anytime.
Ready to practice as a QA Engineer?
Sign up free, no card. 30 voice minutes and unlimited typed interviews, each ending in the complete scorecard: rubric scores, strengths, and what to fix next. Nothing is blurred.
- ✓ Predefined role or paste any job description
- ✓ Rubric scores with evidence quotes
- ✓ 888+ roles to choose from
Questions & answers
- Is the QA Engineer mock interview free?
- Yes. 30 voice minutes and unlimited typed QA Engineer interviews, no card. You get the complete rubric scorecard every time, with the evidence quoted from your own answers. Nothing is blurred.
- Can I use my own job description instead?
- Yes. Predefined roles are starting points. Paste any JD in the setup form and your AI interviewer will tailor questions to that posting.
- How is scoring tailored to this role?
- We pre-fill a realistic QA Engineer job description and interview format so questions and the scorecard match how this role is actually interviewed.
- Should I tailor my resume before practicing?
- Run a resume fit check against a QA Engineer job description first, then practice the interview with the same JD for a tighter loop.