Software Tester Interview Questions — With Answers
80 questions across 4 experience levels — from your very first interview to a Test Manager role — with concrete, substantive answers instead of "look it up yourself." Question set inspired by the testerzy.pl community; answers are my own.
Universal level — questions about you
These questions don't have one "correct" answer — they test motivation and self-awareness, not technical knowledge. Below are the questions and what's worth mentioning.
- What did your first software test look like? — reach for a concrete example, not a generality.
- What do you know about software testing? — show structured knowledge (levels, types of testing), not just buzzwords.
- What hobbies do you have outside testing? — be honest; if your hobby builds analytical thinking (chess, tinkering), mention it.
- What do you like most about software testing? — an authentic answer says more than "everything."
- What do you like least about software testing? — show self-awareness, not a lack of enthusiasm for the job overall.
- What's your favorite software to use? — any answer works, but be ready to justify it.
- Why did you apply for a tester position at this company? — shows whether you researched the company, not just that you needed a job.
- What are your strongest skills in testing? — concrete, backed by a project example.
- What's your biggest weakness in testing? — honest, with a note on what you're doing to improve it.
- What types of testing do you enjoy the most? — consistent with the experience described in your CV.
- What's your experience in software testing? — a short summary of your path, a starting point for the rest of the conversation.
Junior Tester level
13 questions testing the fundamentals — definitions, the testing and defect life cycle, core concepts.
1.What made you want to become a software tester?▾
A motivation question — a good answer combines a concrete moment (e.g. finding a bug that felt satisfying) with what keeps you in testing: analytical thinking, attention to detail, influencing product quality before it reaches users.
2.What are the phases of testing linked to the software testing life cycle?▾
Requirement analysis → test planning → test case analysis and design → test environment setup → test execution → test cycle closure (reporting, archiving results).
3.What are the different testing methods?▾
Manual and automated testing; and, based on knowledge of the internal structure, black-box, white-box and grey-box testing.
4.What are the different levels of testing?▾
Unit testing, integration testing, system testing, and acceptance testing (UAT).
5.What are the different types of testing?▾
Functional and non-functional (performance, security, usability, compatibility), and within those, e.g. regression, smoke, sanity and exploratory testing.
6.What are the categories of defects?▾
Usually split by severity (critical, high, medium, low) and priority (urgent to fix vs. can wait) — two independent dimensions, not synonyms.
7.Explain the bug/defect life cycle.▾
New → Assigned → Open (being fixed) → Fixed → Retest → Verified → Closed. Alternatively: Reopened if regression testing shows the bug came back, or Rejected/Deferred if the report is dismissed or postponed.
8.What's the difference between functional and non-functional testing?▾
Functional checks what the system does — compliance with business requirements. Non-functional checks how it does it — performance, security, usability, scalability.
9.What are verification and validation in software testing?▾
Verification is "are we building the product right" — checking compliance with the spec at every stage (reviews, inspections). Validation is "are we building the right product" — checking that the finished product actually meets the user's needs.
10.What is usability testing?▾
Evaluating how easily, intuitively and effectively a user can use the product — covers learnability, efficiency of use, memorability of the interface, and user satisfaction.
11.What is a test case?▾
A set of input conditions, execution steps and expected results, used to verify a specific functionality or requirement.
12.What are the typical tasks of a software tester?▾
Requirements analysis, test case design, test execution, defect reporting and tracking, retesting and regression testing, communication with the development and business teams.
13.Have you completed any software testing training?▾
A question about your actual experience and certifications (e.g. ISTQB Foundation Level) — if you don't have one, mention self-study, online courses, and practice on personal or test projects.
Mid-Level Tester
42 questions — practical knowledge: testing techniques, tools, APIs, integration and performance testing.
1.What's the basis for preparing an acceptance test plan?▾
Business/user requirements, acceptance criteria defined with the client, use cases, and the project specification/contract.
2.What's your favorite testing software?▾
A question about your real experience. Name concrete tools you actually know (e.g. Postman, Selenium, Playwright, TestRail) and explain why you like them — specifics matter more than a "correct" answer.
3.What types of software testing have you performed?▾
A question about your experience. Describe the scope matching your CV — functional, regression, API, maybe automation — with a concrete project example.
4.Which automated testing tools have you used before?▾
A question about your experience. List tools you've genuinely used (e.g. Selenium, Cypress, Playwright, JMeter) with brief project context.
5.Have you ever been part of a QA team?▾
A question about your experience. Describe the team structure you worked in and your role in it.
6.Have you ever performed automated software testing?▾
A question about your experience. If yes, describe the scope and tools. If not, show awareness of when automation pays off (see question 20 below).
7.Have you passed a software testing certification exam? Which one?▾
A question about your experience. ISTQB Foundation/Advanced is the most recognized certification in the industry — if you don't have one, you can mention plans to get it.
8.What are some different software tests you can perform?▾
Smoke, sanity, regression, integration, system, acceptance, performance, security, exploratory and ad-hoc testing.
9.What is a code walkthrough?▾
An informal code review where the author walks the team through the logic of a solution step by step, mainly to catch bugs and share knowledge — less formal than an inspection.
10.What does formal testing mean?▾
Testing carried out according to a strictly defined process, documentation, and entry/exit criteria — the opposite of ad-hoc testing.
11.What's the difference between a stress test and a load test?▾
A load test checks system behavior under expected, realistic load. A stress test deliberately exceeds that limit to find the system's breaking point and see how it degrades and recovers.
12.Can you explain the software development life cycle?▾
SDLC: requirements analysis → design → implementation → testing → deployment → maintenance. Models for running this cycle include Waterfall, V-model, and Agile/Scrum.
13.What is performance testing?▾
Checking the speed, responsiveness and stability of a system under a defined load — includes load, stress, spike and endurance/soak testing.
14.What are some possible causes of project failure?▾
Unclear or changing requirements, lack of communication between teams, unrealistic deadlines, underestimating test scope, lack of stakeholder engagement.
15.What would you pay attention to while testing software?▾
Compliance with requirements, edge cases, error handling, UX consistency, performance under typical load, and data security.
16.What's the difference between alpha and beta testing?▾
Alpha: performed internally, by the company's own team/testers, before external release. Beta: performed by a limited group of real external users, after alpha testing, before full launch.
17.What is verified in white-box software testing?▾
The internal structure of the code — logical paths, statement/branch/condition coverage, and correct implementation of algorithms.
18.What's the difference between static and dynamic software testing?▾
Static: analyzing code or documentation without running it (reviews, static analysis, inspections). Dynamic: running the program and observing its actual behavior.
19.Can you compare top-down and bottom-up testing?▾
Top-down: testing starts from higher-level modules, with lower ones replaced by stubs. Bottom-up: starts from lower-level modules, with higher ones simulated by drivers. Both are integration testing strategies.
20.What types of software testing would you automate?▾
Mainly repeatable, stable and time-consuming scenarios: regression, smoke tests, API tests. Less often exploratory or one-off testing, where automation doesn't pay off.
21.Can you explain what you'd include in a test report?▾
Scope and purpose of testing, environment, number of executed/passed/failed cases, list of defects found with priority, risks, and a recommendation on release readiness.
22.What is end-to-end testing and why is it important?▾
Verifying an application's entire flow from start to finish, simulating a real user scenario across all integrated components — important because it catches issues invisible when testing components in isolation.
23.What is exploratory testing?▾
Simultaneously designing and executing tests without detailed pre-written test cases — the tester investigates the application on the fly, relying on experience and intuition to find issues not obvious from test scripts.
24.What is use case testing?▾
Designing tests directly from defined use cases (user interactions with the system), covering the main path and alternative/exception paths.
25.What's the difference between STLC and SDLC?▾
SDLC is the entire software development cycle (from requirements to maintenance). STLC is the subset dealing exclusively with the testing process, run in parallel with the corresponding SDLC phases.
26.What is a traceability matrix?▾
A document mapping requirements to test cases, letting you check that every requirement has test coverage and vice versa.
27.What is equivalence partitioning?▾
A black-box technique that divides input data into classes where the system should behave the same way — you test one representative case from each class instead of every possible value.
28.What is black-box testing? What are the different black-box techniques?▾
Testing without knowledge of the internal code structure, based purely on inputs and expected outputs. Techniques: equivalence partitioning, boundary value analysis, decision tables, state transition testing, use-case-based testing.
29.What's the difference between test scenarios, test cases and test scripts?▾
A test scenario is a high-level description of "what" to test. A test case is the detailed steps, input data and expected result for a specific scenario. A test script is the implementation of a test case as code for automated execution.
30.What is data-driven testing?▾
An automation approach where the same test logic is executed repeatedly with different sets of input data, usually loaded from an external file or spreadsheet.
31.What is a latent defect?▾
A bug that's been present in the system for a long time but hasn't surfaced before, because the conditions needed to trigger it (a specific data combination or load) hadn't occurred.
32.What is mutation testing?▾
A technique for assessing test suite quality by introducing small, deliberate changes ("mutations") into the code and checking whether existing tests catch them — if a test doesn't catch a mutation, the test itself needs improvement.
33.What are the categories of debugging?▾
Includes brute-force debugging (step-by-step tracing), backtracking (from symptom to cause), cause elimination, and debugging using static code analysis.
34.What is error masking? Explain with an example.▾
A situation where one bug hides the existence of another — e.g. a failure in an earlier step prevents reaching the code where a second defect is lurking, so the second one only surfaces after the first is fixed.
35.What steps will you take after finding a defect?▾
Reproduce the bug and confirm it's repeatable, gather diagnostic data (logs, screenshots, reproduction steps), log it in the tracking system with the right priority and severity, then retest and run regression once it's fixed.
36.What is fuzz testing and when is it used?▾
A technique that feeds random, invalid or unexpected data as input to detect crashes, memory leaks or security vulnerabilities — mainly used for robustness and security testing.
37.What does agile testing mean and where is it used?▾
Testing integrated into an iterative, incremental development cycle (Scrum/Kanban) — the tester works in parallel with developers within the same sprint, instead of waiting for a "finished" product at the end.
38.What is an API?▾
An Application Programming Interface — a set of rules and entry points (endpoints) that define how different components or systems communicate with each other.
39.What are the different HTTP status codes?▾
1xx – informational, 2xx – success (200 OK, 201 Created), 3xx – redirection (301, 302), 4xx – client error (400 Bad Request, 401 Unauthorized, 404 Not Found), 5xx – server error (500 Internal Server Error, 503 Service Unavailable).
40.What does browser automation mean?▾
Controlling a browser programmatically (e.g. via Selenium or Playwright) to simulate user actions — clicking, filling forms, navigating — without manual interaction.
41.What is A/B testing?▾
Comparing two variants of a solution (e.g. two versions of a page) across different user groups to measure which variant better achieves a defined business goal.
42.What are the types of integration testing?▾
Big Bang (integrating all modules at once), incremental top-down, incremental bottom-up, and the sandwich/hybrid approach, combining top-down and bottom-up at the same time.
Advanced level — Test Manager
14 questions about organizational skills: planning, risk, estimation, team management.
1.What does a Test Plan consist of?▾
Scope and objectives of testing, strategy and approach, schedule and resources, entry/exit criteria, roles and responsibilities, risks and contingency plan, test environment and tools.
2.Explain what Test Deliverables are.▾
All documents and artifacts produced during the testing process: test plan, test cases and scenarios, test data, execution reports, defect log, final test summary report.
3.What things should you consider before choosing automation tools?▾
Compatibility with the application's technology (web/mobile/desktop/API), license cost vs. budget, the team's learning curve, community/vendor support, and integration with CI/CD and the existing stack.
4.How will you conduct a Risk Analysis?▾
Identify potential risks (product and project risks), assess the probability and impact of each, prioritize them, then match testing intensity to the highest-risk areas.
5.How can you eliminate product risk in your project?▾
Early testing (shift-left), focusing resources on critical/high-risk areas, regular code and requirement reviews, ongoing communication with stakeholders about risk status.
6.What's the basis for estimating the value of a project?▾
The functional scope, technical complexity, available resources and their rates, historical data from similar projects, and estimation techniques (function points, planning poker, comparison to analogous tasks).
7.What things should be considered when monitoring a project?▾
Progress against the schedule, quality (trend in the number and severity of defects), resource utilization, evolving risks, and adherence to scope (scope creep).
8.What are the most common tester mistakes that cause project problems?▾
Underestimating time needed for testing, skipping edge cases, unclear communication about defect status, testing too late in the cycle (no shift-left), insufficient documentation.
9.What does a typical test report contain? What are the benefits of test reports?▾
Contains: scope, executed/passed/failed tests, defects by priority, risks, and a go/no-go recommendation. Benefits: an objective basis for release decisions, an audit trail, and visibility into quality for non-technical stakeholders.
10.When is an RTM (Requirement Traceability Matrix) prepared?▾
It's created during test planning, based on the gathered requirements, and updated throughout the project — used to confirm full requirement coverage by tests.
11.What are stubs and drivers in manual testing?▾
Stubs simulate components called by the module under test (top-down approach). Drivers simulate components that call the module under test (bottom-up approach) — both let you test a module before the whole system is ready.
12.How will you handle conflict among team members?▾
A 1:1 conversation with those involved to understand the source of the conflict, keeping the discussion focused on facts and the project's goal rather than emotions, seeking a compromise, and escalating to a manager only if a direct conversation fails.
13.Explain how a test coverage tool works.▾
It instruments the code during test execution and records which lines, branches and conditions were actually executed, generating a report showing the percentage and location of uncovered code.
14.How is the level of risk determined?▾
As a product or combination of the probability of a problem occurring and the weight of its impact on the product/business — the result lets you rank risks and decide where to focus testing effort.