QA Lead / Manager interview questions and answers

9 of 9 questions shown

1. midStrategyWhat is the difference between a test strategy and a test plan?

   Model answer. The strategy is the long-lived approach: test levels, tools, environments, risk model, quality gates and responsibilities. A plan is specific to a release or project: scope, schedule, resources, entry and exit criteria. One strategy supports many plans.

   I can answer this
2. midMetricsWhich metrics do you report to engineering leadership, and which do you avoid?

   Model answer. Report defect escape rate, time from commit to test feedback, flaky-test rate and change failure rate. Avoid bugs per tester, test-case counts and raw pass rate on their own, because they are easy to game and say little about risk.

   I can answer this
3. midPlanningHow do you estimate testing effort for a new feature?

   Model answer. Break the feature into risk areas, add test design, data preparation, automation, regression and at least two rounds of defect verification, and use cycle times from past features. Give a range with stated assumptions and a buffer instead of a single number.

   I can answer this
4. midReleaseWhat are exit criteria? Give examples.

   Model answer. Agreed conditions that must be true before testing ends or a build ships. Examples: no open critical or high defects without an accepted workaround, all critical-path cases executed and passed, regression pass rate above an agreed threshold, performance within SLO, and no known data-loss issue.

   I can answer this
5. seniorHiringHow do you assess an automation engineer candidate beyond trivia?

   Model answer. Use a work sample: write tests for a small app and review a deliberately flaky test. Watch the debugging approach, trade-offs and communication, and score every candidate with the same rubric to reduce bias.

   I can answer this
6. seniorStakeholdersA VP wants to ship on Friday and critical defects are open. What do you do?

   Model answer. Present risk in business terms: who is affected, how likely, what the workaround is and how fast you can roll back. Offer options such as shipping behind a flag, cutting scope or a partial rollout. The decision belongs to the business; your job is to make sure it is informed and documented.

   I can answer this
7. seniorProcessHow do you shift QA left in a team that currently receives builds at the end of the sprint?

   Model answer. Join refinement and write acceptance criteria with examples, hold three-amigos sessions, pair with developers on unit and API tests, test on preview environments during the sprint and include tests in the definition of done. Make pull-request checks the first quality gate.

   I can answer this
8. seniorTeamTwo senior testers disagree on rewriting the Selenium suite in Playwright. How do you decide?

   Model answer. Name the problems with numbers (flake rate, run time, maintenance hours), pilot the new tool on one area with success criteria and a time box, and keep the old suite running. Decide from the pilot data and the team's skills, then plan the migration in slices.

   Tools: Selenium, Playwright

   I can answer this
9. seniorCultureDevelopers say QA is the bottleneck. What changes?

   Model answer. Measure where time goes: queues, environment waits and rework. Move checks earlier so developers own unit and API tests, let QA focus on risk and exploration, test in parallel inside the sprint and shorten CI feedback. Agree working agreements instead of handing off at the end.

   I can answer this

No question matches those filters. Clear the search or choose All.