QA Engineer interview questions
51 questions asked in QA Engineer interviews, on test strategy, automation, bugs and releases. They are built from thousands of real job ads. Under each one: what the interviewer is listening for, and the follow-up they may ask. For the recruiter call, see the HR screen questions.
Behavioral questions
Questions about how you work in this role. More in behavioral questions for any tech role.
-
1
Tell me about a time you pushed back on a release because of quality.
All levels
Listening for Clear facts on the risk, a calm conversation and an alternative offered.
Follow-up Ask how the team felt about it afterwards.
-
2
Tell me about a time a client was unhappy with the quality of a release. What did you do?
All levels
Listening for Owns the QA part without blaming others, fixes the gap in the process.
Follow-up Ask what they told the client and what changed next time.
-
3
Tell me about a time a developer said your bug wasn't really a bug. How did it end?
Junior, Mid
Listening for Uses the spec, user impact and evidence, not ego.
Follow-up Ask who made the final call and whether they agreed with it.
-
4
Tell me about how you moved from manual testing into automation, or helped someone else make that move.
Junior, Mid
Listening for A concrete learning path and patience with a slow start.
Follow-up Ask what they would do differently if they started again.
-
5
Tell me about a time a big change landed right before release and you had very little time to test it.
All levels
Listening for Focuses on risk, tells people what was and was not tested.
Follow-up Ask what they skipped and how they decided.
-
6
Tell me about a time your testing work wasn't very visible to the team. How did you make it count?
Junior
Listening for Shares results and risks in a way others can use.
Follow-up Ask how they report their testing at the end of a sprint.
-
7
Tell me about a time you got developers to take on more of the testing.
Mid, Senior
Listening for Brings developers in by making it easy and showing value, not by demanding.
Follow-up Ask what pushback they got.
-
8
Tell me about a release you signed off that you later wished you hadn't.
Mid, Senior
Listening for Honest about the call and the pressure at the time, and what they changed in their own checks.
Follow-up Ask what signal they missed.
Technical discussion questions
Talking through your experience and decisions, not a coding test. Grouped by topic.
Test automation
-
1
How do you decide which tests to automate and which to keep manual?
All levels
Listening for Weighs how often a test runs, how stable the feature is and the cost to maintain.
Follow-up Ask for a test they chose to keep manual.
-
2
Some of our automated tests fail randomly. How would you deal with that?
All levels
Listening for Finds the cause (timing, data, environment) instead of just re-running.
Follow-up Ask what they do with a flaky test while it is being fixed.
-
3
Tell me about the first automated test you wrote. What did you learn from making it stable?
Junior
Listening for Real lessons like waits, locators and test data.
Follow-up Ask what they would do differently in that test today.
-
4
For a new product, how would you split testing between unit, API and UI tests, and who owns each part?
Senior
Listening for A clear split with most checks below the UI and developers owning unit tests.
Follow-up Ask how they would handle a team that already has only UI tests.
Regression testing
-
5
Tell me about a bug that reached production. Why wasn't it caught?
All levels
Listening for Honest root cause in the process, not only blame, and a concrete change after.
Follow-up Ask what test now covers it.
-
6
Before each release you run regression tests. How do you decide what goes into the regression suite?
Junior, Mid
Listening for Picks by risk, change area and past bugs, and keeps the suite up to date.
Follow-up Ask what they remove from it and when.
-
7
Our regression takes three days and the team wants to release every week. What would you change?
Mid, Senior
Listening for Cuts by risk, automates the stable core, runs in parallel in CI.
Follow-up Ask what they would keep manual and why.
CI/CD
-
8
Your automated tests run in Jenkins or another CI. What happens when they fail, and who acts on it?
All levels
Listening for Knows the flow from failure to owner and how results are shared.
Follow-up Ask what they do when failures are ignored.
-
9
How would you set up a CI pipeline so tests give feedback in minutes, not hours?
Mid, Senior
Listening for Runs fast tests first, parallel runs, containers, test only what changed.
Follow-up Ask what they would do with tests that are still slow.
Test planning
-
10
You get a feature to test with no spec, only a short ticket. How do you work out what to test?
Junior, Mid
Listening for Asks the PO and devs, uses similar features and user flows, writes down assumptions.
Follow-up Ask how they make sure the team agrees with their list.
-
11
You join a team with no test strategy. What do you do in your first month?
Senior
Listening for Listens and maps risk before changing things, then picks a few quick wins.
Follow-up Ask how they would get developers on board.
Api testing
-
12
When a task changes, our Slack integration posts a message to a channel. How would you test that?
All levels
Listening for Thinks about the trigger, the message content, failures and third-party limits.
Follow-up Ask how they would test it without spamming a real channel.
-
13
How do you test an API when there's no UI yet? What do you check in the response?
Junior
Listening for Uses a tool like Postman or REST Assured and checks status, body, errors and auth.
Follow-up Ask how they test an API that needs a login token.
-
14
How would you test a payment API?
Mid, Senior
Listening for Covers amounts, currencies, duplicates, timeouts, security and checks the data behind it.
Follow-up Ask how they would test a payment that times out halfway.
Performance testing
-
15
Tell me about a performance test you ran or helped with. What did you measure?
Junior
Listening for Knows load versus stress and basic numbers like response time and errors.
Follow-up Ask what the results told the team.
-
16
Users say a page feels slow, but all your functional tests pass. How would you check it?
Junior, Mid
Listening for Measures in the browser, compares environments and data sizes.
Follow-up Ask what number they would call too slow.
-
17
How would you check that our app still works when ten times more users arrive?
Mid, Senior
Listening for Defines realistic load, picks what to measure, finds the bottleneck.
Follow-up Ask what result would make them say it is not ready.
-
18
Before a big sale event, how would you plan load testing for our checkout?
Senior
Listening for Realistic traffic model, test environment close to production, clear pass criteria and a plan B.
Follow-up Ask who they would need to involve.
Python
-
19
How do you organise your automation code in Python or Java so one UI change doesn't break fifty tests?
Junior, Mid
Listening for Page objects or similar reuse, clean locators, shared helpers.
Follow-up Ask about a refactor of test code they did.
Manual testing
-
20
How would you test a login screen? Talk me through your approach.
All levels
Listening for Covers happy path, wrong input, security and edge cases in a clear order.
Follow-up Ask how they would choose what to automate here.
Bug tracking
-
21
What makes a good bug report?
All levels
Listening for Steps to reproduce, expected versus actual, environment, evidence, severity.
Follow-up Ask about a bug report of theirs that a developer could not use.
-
22
How do you decide the severity and priority of a bug you report?
Junior
Listening for Knows the difference between severity and priority with an example.
Follow-up Ask what they do when the developer disagrees.
-
23
A client reports a bug that your team already marked as fixed. How do you handle it with the client and the developers?
Mid, Senior
Listening for Checks versions and environments first, then talks openly with the client.
Follow-up Ask what they would change so it does not happen again.
Release management
-
24
It's the day before release and you still have tests left to run. What do you do?
Junior
Listening for Prioritises by risk and tells the lead early what will not be covered.
Follow-up Ask how they would explain that to the team.
-
25
It's release day and you find a bug that isn't a blocker but looks bad. How do you make the call?
Mid, Senior
Listening for Weighs user impact, workaround and who decides, and states the risk clearly.
Follow-up Ask who they would tell first and what they would say.
Quality metrics
-
26
How do you show the team whether quality is getting better or worse? Which numbers do you trust?
Mid, Senior
Listening for A few meaningful numbers like escaped bugs and trends, and knows how numbers get gamed.
Follow-up Ask about a number they stopped tracking.
Java
-
27
If you built a test automation framework from scratch in Java or Python, what would you put in first?
Mid, Senior
Listening for Starts small: structure, config per environment, reporting, CI run.
Follow-up Ask what they would leave out on purpose.
Mobile testing
-
28
How is testing a mobile app different from testing a website?
All levels
Listening for Devices, OS versions, network, interruptions, store releases.
Follow-up Ask which of these caused a real bug for them.
-
29
We support hundreds of Android phones. How would you decide which devices to test on?
Mid, Senior
Listening for Uses real usage data, OS versions and screen sizes, plus a device cloud.
Follow-up Ask how often they would review the list.
SQL
-
30
How do you use SQL when you test? Give me an example where it helped you find a bug.
Junior, Mid
Listening for Checks data behind the UI and sets up test data.
Follow-up Ask what they check in the database after a user places an order.
-
31
Tests keep failing because the test data keeps changing. How would you manage test data?
All levels
Listening for Creates data per test or resets it, avoids shared state.
Follow-up Ask how they would do it when the data comes from a third party.
Ai testing
-
32
Have you used AI tools to help with testing? Where did they help, and where didn't you trust them?
Junior, Mid
Listening for Practical use like drafting test cases or scripts, with checking of the output.
Follow-up Ask about a time the tool got it wrong.
-
33
How would you test a chatbot feature where the answer is a bit different every time?
All levels
Listening for Checks rules and quality instead of exact text, uses examples and reviews.
Follow-up Ask how they would catch the bot saying something harmful.
-
34
We're adding an AI feature that summarises customer tickets. How would you decide it's good enough to release?
Senior
Listening for Sets quality criteria with the product team, a test set of real examples, and monitoring after launch.
Follow-up Ask what would make them block the release.
Selenium
-
35
From your experience with Selenium or Playwright, what makes a UI test easy to maintain?
All levels
Listening for Stable locators, no fixed sleeps, independent tests, clear names.
Follow-up Ask about a test that was painful to maintain and why.
-
36
We're choosing between Selenium and Playwright for a new web project. How would you decide?
Mid, Senior
Listening for Weighs the team's skills, browsers to support, speed and debugging, not hype.
Follow-up Ask how they would try both before deciding.
Docker
-
37
Have you run tests against services in Docker containers? What problem did that solve for you?
Junior, Mid
Listening for Sees why the same setup on every machine and in CI helps.
Follow-up Ask what broke when they first tried it.
-
38
The test environment keeps going down in the middle of your test cycle. What would you do?
All levels
Listening for Tracks the problem with evidence and works with devops on a fix, not only waiting.
Follow-up Ask how they kept testing in the meantime.
Embedded systems
-
39
How would you test software that runs on a device, like a smart lock, where there isn't much of a screen to look at?
All levels
Listening for Thinks about logs, hardware states, power and network loss, and tools to drive the device.
Follow-up Ask how they would automate part of it.
-
40
A bug shows up only on the real device, never in the simulator. How would you narrow it down?
All levels
Listening for Compares conditions, collects logs, changes one thing at a time.
Follow-up Ask what they put in the bug report so a dev can act on it.
Agile
-
41
In a two-week sprint, when do you start testing a story?
Junior, Mid
Listening for Starts early with acceptance criteria and test cases, not only at the end.
Follow-up Ask what happens when stories reach QA on the last day.
-
42
Developers here see testing as only QA's job. How would you change that?
Senior
Listening for Builds shared ownership with small steps and visible results.
Follow-up Ask how they would measure if it worked.
General
-
43
You lead five testers with very different skills. How would you raise the level of the whole team?
Senior
Listening for Knows each person's gaps and goals, uses pairing and reviews.
Follow-up Ask how they would help a manual tester who is nervous about automation.