↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

27 Selective QA Interview Questions for Managers to Ask

The page presents QA interview questions as a practical way to judge whether a candidate is qualified, fits the company’s tech culture, and can work with the team. It mixes higher-level process questions with technical basics, and it also stresses communication, organization, and adaptability.

Reading notes
#

  • Use early interview questions to confirm résumé claims and basic domain knowledge.
  • Evaluate whether the candidate knows QA methodologies such as agile and waterfall, and can explain preferences.
  • Ask about test scripts and testing tools to see how well the candidate matches current company tools.
  • Compare experience with automated and manual testing to understand flexibility and openness to change.
  • Use questions about the best catch or the toughest bug to get concrete examples of problem solving.
  • Ask how the candidate would test an arbitrary object, such as a soda machine, to observe their approach to different functions and user needs.
  • Ask how a test case is written and what questions the candidate raises about supported platforms and device or browser combinations.
  • Learn how the candidate organizes work, sets priorities, and uses checklists.
  • Ask how much time is enough for a release to understand expectations under pressure.
  • Check whether the candidate expects to join planning sessions and use them to assess risk and complexity.
  • Confirm understanding of quality assurance, quality control, and testing as different responsibilities.
  • Check whether the candidate thinks QA should start at the beginning of a project.
  • Look for a balanced view of how much testing is sufficient and why exhaustive testing is impossible.
  • Verify understanding of validation and verification.
  • Compare developer and tester mindsets when the article asks why developers may make poor testers.
  • Check knowledge of the QA testing life cycle, from requirement analysis and planning to execution and closure.
  • Ask about data driven testing and the use of files such as Excel sheets or CSV files.
  • Ask what a test strategy includes, including scope, schedule, resources, and priorities.
  • Confirm knowledge of white box, black box, and grey box testing.
  • Ask how the candidate manages time and deadlines in testing.
  • Check the difference between stress testing and load testing.
  • Distinguish functional testing from non-functional testing.
  • Distinguish retesting from regression testing.
  • Ask what common mistakes the candidate watches for, such as resource allocation and scheduling problems.
  • Ask about monkey testing and its random inputs.
  • Ask how the candidate estimates how much testing a software needs, including complexity.
  • Ask for an ideal progression of testing techniques from unit testing to acceptance testing.