SoftwareTestPilot
85 Q&A

Software Testing Interview Questions: The Master List (2026 Updated)

The definitive 2026 master list of software testing interview questions covering manual, automation, API, performance, Selenium, JMeter, Cypress, AI testing, ISTQB, and scenario-based Q&A with expert answers.

  • 17 min read
  • Difficulty: Mixed (Easy → Hard)
  • Freshers → Experienced
  • Updated June 20, 2026
  • Avinash Kamble
Start AI mock interview Practice with QA Hub
0 / 85 reviewed
0%

2. Fresher-Level Software Testing Interview Questions

Easy Very Common 1 minQ1 / 85

Q1.What is software testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "software testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Software testing is the process of evaluating a system to find defects, verify that it meets specified requirements, and validate that it solves the user's problem. It is a structured activity that increases confidence in the software, reduces the cost of late defects, and provides objective information about product quality.

Tips to remember
  • Open with a one-sentence definition of software testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise software testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ3
Q2 →
Easy Very Common 1 minQ2 / 85

Q2.What is the difference between QA, QC, and testing?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "difference between QA, QC, and testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

QA (Quality Assurance) is process-focused — the entire set of planned activities that prevent defects. QC (Quality Control) is product-focused — the operational activities that verify the product meets requirements. Testing is one specific QC activity that executes the software to find defects.

Tips to remember
  • Open with a one-sentence definition of difference between QA, QC, and testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between QA, QC, and testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ4
← Q1Q3 →
Easy Very Common 1 minQ3 / 85

Q3.What is the SDLC?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "SDLC" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

SDLC (Software Development Life Cycle) is the end-to-end framework for building software, typically with phases: Requirement Analysis → Planning → Design → Implementation → Testing → Deployment → Maintenance. The most common 2026 variants are Agile/Scrum, SAFe, and Shift-Left DevOps.

Tips to remember
  • Open with a one-sentence definition of SDLC, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise SDLC cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ1Q5
← Q2Q4 →
Easy Very Common 1 minQ4 / 85

Q4.What is the STLC?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "STLC" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

STLC (Software Testing Life Cycle) is the testing-specific subset of the SDLC: Requirement Analysis → Test Planning → Test Case Design → Test Environment Setup → Test Execution → Test Closure. Each phase has specific entry and exit criteria.

Tips to remember
  • Open with a one-sentence definition of STLC, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise STLC cleanly.
  • Explain setup/teardown ordering and what runs per-test vs per-suite; ordering mistakes are the follow-up question.
RelatedQ2Q6
← Q3Q5 →
Easy Very Common 1 minQ5 / 85

Q5.What is verification vs validation?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "verification vs validation" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Verification answers "are we building the product right?" through reviews, walkthroughs, and inspections — done before code. Validation answers "are we building the right product?" through actual execution against user needs — done after code.

Tips to remember
  • Open with a one-sentence definition of verification vs validation, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise verification vs validation cleanly.
RelatedQ3Q7
← Q4Q6 →
Easy Very Common 1 minQ6 / 85

Q6.What is a test case?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "test case" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A test case is a documented set of preconditions, inputs, actions, expected results, and postconditions developed to verify a specific requirement. A good test case has a unique ID, a clear description, traceability to the requirement, repeatable steps, and an unambiguous expected result.

Tips to remember
  • Open with a one-sentence definition of test case, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test case cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ4Q8
← Q5Q7 →
Easy Very Common 1 minQ7 / 85

Q7.What is a test plan?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "test plan" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A test plan is a document that describes the scope, approach, resources, schedule, and deliverables of a testing effort. In Agile teams the test plan is often replaced by a lightweight test strategy inside the Definition of Done and the team's working agreement.

Tips to remember
  • Open with a one-sentence definition of test plan, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test plan cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ5Q9
← Q6Q8 →
Easy Very Common 1 minQ8 / 85

Q8.What is a bug/defect?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "bug/defect" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A bug is any deviation between actual and expected behavior, or any flaw in a software component that may cause it to perform incorrectly. Bugs are categorized as functional (wrong behavior), non-functional (performance, security, usability), or cosmetic.

Tips to remember
  • Open with a one-sentence definition of bug/defect, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise bug/defect cleanly.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ6Q10
← Q7Q9 →
Easy Very Common 1 minQ9 / 85

Q9.What is regression testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "regression testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Regression testing re-executes previously passed tests after a code change to confirm that existing functionality has not broken. In CI/CD it runs automatically on every pull request. The ideal regression suite is small, fast, deterministic, and high-coverage.

Tips to remember
  • Open with a one-sentence definition of regression testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise regression testing cleanly.
  • Describe the pipeline stage order and what makes the build fail — a vague "we run tests in CI" answer stalls here.
RelatedQ7Q11
← Q8Q10 →
Medium Very Common 1 minQ10 / 85

Q10.What is the bug life cycle?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "bug life cycle" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

New → Assigned → Open → Fixed → Pending Retest → Retest → Verified → Closed (or Reopened if the fix fails). Rejected means the developer declines it. Deferred means a later release. Duplicate means another report already covers it.

For a complete walkthrough of these fundamentals with templates and examples, read our Manual Testing Complete Guide for 2026.

Tips to remember
  • Open with a one-sentence definition of bug life cycle, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise bug life cycle cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ8Q12
← Q9Q11 →
Confidence check

If you can confidently answer the Fresher-Level Software Testing Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

3. Manual Testing Interview Questions

Easy Very Common 1 minQ11 / 85

Q11.Explain boundary value analysis with an example.

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Open-ended "explain boundary value analysis with an example" prompts test how you structure a technical answer under pressure. Panels look for a clear opening definition, one worked example, and a closing sentence on the pitfall they were about to ask about next.

Detailed explanation

BVA tests at the boundaries of valid input ranges because defects cluster there. For a field accepting ages 18–60, you test 17, 18, 60, 61 (and the nominal values 30, 45). It pairs naturally with equivalence partitioning.

Tips to remember
  • Use a 3-part frame for boundary value analysis with an example: what it is → how it works → one gotcha you've hit in a real Career & Interview Prep project.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise boundary value analysis with an example cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ9Q13
← Q10Q12 →
Easy Very Common 1 minQ12 / 85

Q12.What is equivalence partitioning?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "equivalence partitioning" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

EP divides inputs into groups (partitions) that should behave the same way, then tests only one value from each group. For a 0–999 numeric field, partitions are <0, 0–999, and >999. You pick one representative from each.

Tips to remember
  • Open with a one-sentence definition of equivalence partitioning, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise equivalence partitioning cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ10Q14
← Q11Q13 →
Easy Very Common 1 minQ13 / 85

Q13.What is decision table testing?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "decision table testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A decision table captures combinations of inputs and their corresponding actions, useful when business rules depend on multiple conditions. For a discount engine (member + coupon code + order value), a table lists each combo and the resulting discount.

Tips to remember
  • Open with a one-sentence definition of decision table testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise decision table testing cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ11Q15
← Q12Q14 →
Easy Very Common 1 minQ14 / 85

Q14.What is state transition testing?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "state transition testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Used when system behavior depends on the sequence of events. You model the valid states (New → Approved → Active → Cancelled), the events that trigger transitions, and the guards that allow them. It catches defects around illegal transitions.

Tips to remember
  • Open with a one-sentence definition of state transition testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise state transition testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ12Q16
← Q13Q15 →
Easy Very Common 1 minQ15 / 85

Q15.What is use case testing?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "use case testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

You derive test cases from use cases, identifying the actor, preconditions, main flow, alternate flows, and exception flows. Each flow becomes at least one test case.

Tips to remember
  • Open with a one-sentence definition of use case testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise use case testing cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ13Q17
← Q14Q16 →
Easy Very Common 1 minQ16 / 85

Q16.How do you decide severity vs priority?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Comparison questions like this test whether you understand decide severity vs priority at a design level — not just that both exist, but when to pick one over the other. Panels use it to see if you can defend a trade-off with a real project example.

Detailed explanation

Severity = technical impact (set by tester). Priority = business urgency (set by product owner). A typo on a pricing page is low severity but very high priority. A crash in a rarely-used admin filter is high severity but very low priority.

Tips to remember
  • Structure the answer as a small table in your head: dimension, option A, option B — and close with "I'd pick X when Y".
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise decide severity vs priority cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ14Q18
← Q15Q17 →
Easy Very Common 1 minQ17 / 85

Q17.Walk me through how you write a good bug report.

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on Walk me through how you write a good bug report and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Title (one line, what & where), environment, preconditions, exact steps to reproduce, expected result, actual result, screenshots/video/logs, severity/priority, build/version, and a workaround if known. The goal: a developer can reproduce it in under 5 minutes without contacting you.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on Walk me through how you write a good bug report over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Walk me through how you write a good bug report cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ15Q19
← Q16Q18 →
Easy Very Common 1 minQ18 / 85

Q18.What is exploratory testing?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "exploratory testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A simultaneous learning, test design, and execution activity where the tester charters a mission (e.g., "explore the new checkout on mobile for 90 minutes") and adapts based on what they find. It complements scripted testing and is excellent for finding usability and edge-case bugs.

Tips to remember
  • Open with a one-sentence definition of exploratory testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise exploratory testing cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ16Q20
← Q17Q19 →
Easy Very Common 1 minQ19 / 85

Q19.What is session-based test management (SBTM)?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "session-based test management (SBTM)" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

SBTM structures exploratory testing into time-boxed sessions with charters, notes, and debriefs. Output is a session sheet that captures what was tested, what was found, and a coverage map. It provides accountability for exploratory work.

Tips to remember
  • Open with a one-sentence definition of session-based test management (SBTM), then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise session-based test management (SBTM) cleanly.
RelatedQ17Q21
← Q18Q20 →
Medium Very Common 1 minQ20 / 85

Q20.What is a test matrix?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "test matrix" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A test matrix tracks test coverage across a grid of variables (e.g., browsers × OS × devices). It is the foundation for prioritization when coverage is impossible on every cell and is the input for cloud testing platforms like BrowserStack and Sauce Labs.

For deeper coverage of test design techniques, see our complete manual testing interview Q&A.

Tips to remember
  • Open with a one-sentence definition of test matrix, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test matrix cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ18Q22
← Q19Q21 →
Confidence check

If you can confidently answer the Manual Testing Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

4. Automation Testing Interview Questions

Easy Very Common 1 minQ21 / 85

Q21.What is the test automation pyramid?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "test automation pyramid" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Popularized by Mike Cohn: many fast unit tests at the bottom, a moderate layer of integration/API tests in the middle, and a small layer of end-to-end UI tests at the top. The shape tells you to invest more in fast, cheap tests and less in slow, brittle end-to-end tests.

Tips to remember
  • Open with a one-sentence definition of test automation pyramid, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test automation pyramid cleanly.
RelatedQ19Q23
← Q20Q22 →
Easy Very Common 1 minQ22 / 85

Q22.What is data-driven testing?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "data-driven testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Executing the same test logic against multiple data sets stored externally (CSV, Excel, JSON, database). Tools like Selenium, Cypress, and Playwright integrate with parameterized fixtures and data providers.

Tips to remember
  • Open with a one-sentence definition of data-driven testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise data-driven testing cleanly.
  • Say how you clean up or roll back the data you touch — DB questions are really data-hygiene questions.
RelatedQ20Q24
← Q21Q23 →
Easy Very Common 1 minQ23 / 85

Q23.What is keyword-driven testing?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "keyword-driven testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Tests are built from reusable keywords (e.g., openBrowser, loginAs, clickButton) abstracted from the test code. Robot Framework is the most popular keyword-driven tool and is widely used in enterprise QA.

Tips to remember
  • Open with a one-sentence definition of keyword-driven testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise keyword-driven testing cleanly.
RelatedQ21Q25
← Q22Q24 →
Easy Very Common 1 minQ24 / 85

Q24.What is the Page Object Model (POM)?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "Page Object Model (POM)" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A design pattern where each web page is represented by a class that encapsulates the page's locators and high-level actions. Tests interact with page objects, never raw locators. Benefits: maintainability, readability, parallel authoring of tests and locators.

Tips to remember
  • Open with a one-sentence definition of Page Object Model (POM), then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Page Object Model (POM) cleanly.
  • Add one sentence on what does NOT belong in a page object (assertions, test data) — that boundary is what separates mid from senior answers.
RelatedQ22Q26
← Q23Q25 →
Easy Very Common 1 minQ25 / 85

Q25.What is a flaky test?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "flaky test" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A test that sometimes passes and sometimes fails without any code change. Causes: shared test data, hard-coded waits, race conditions, network instability, animation timing. The right response is to triage, fix the root cause, and quarantine if necessary.

Tips to remember
  • Open with a one-sentence definition of flaky test, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise flaky test cleanly.
  • Quote a real flake-rate number before and after your fix; measured outcomes score far higher than "we added retries".
RelatedQ23Q27
← Q24Q26 →
Medium Very Common 1 minQ26 / 85

Q26.How do you reduce flakiness?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Hands-on "how would you reduce flakiness" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use explicit waits instead of sleep, isolate test data, design for parallelism from day one, run on containerized environments, and add retry only as a last resort — with quarantining and dashboards to monitor flake rate.

Tips to remember
  • Walk through reduce flakiness as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the reduce flakiness snippet live — panels often ask you to type it, not describe it.
  • State that you never mix wait strategies and never use a hard sleep, then give the timeout value you actually run in CI.
RelatedQ24Q28
← Q25Q27 →
Easy Very Common 1 minQ27 / 85

Q27.What is shift-left testing?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "shift-left testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A practice of moving testing earlier into the SDLC — static analysis on PRs, unit tests on every commit, contract tests on every merge, and feature-flagged canaries in production. It catches defects when they are cheapest to fix.

Tips to remember
  • Open with a one-sentence definition of shift-left testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise shift-left testing cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ25Q29
← Q26Q28 →
Easy Very Common 1 minQ28 / 85

Q28.What is shift-right testing?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "shift-right testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

The complementary practice of testing in production through canary releases, feature flags, synthetic monitoring, A/B testing, and chaos engineering. It catches issues that only appear at scale or under real-world variance.

Tips to remember
  • Open with a one-sentence definition of shift-right testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise shift-right testing cleanly.
RelatedQ26Q30
← Q27Q29 →
Easy Very Common 1 minQ29 / 85

Q29.What is contract testing?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "contract testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A test that verifies the agreement between a consumer (frontend, mobile, other service) and a provider (API). Tools like Pact let each side define its expectations, then validate compatibility in CI without spinning up the full system.

Tips to remember
  • Open with a one-sentence definition of contract testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise contract testing cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ27Q31
← Q28Q30 →
Medium Very Common 1 minQ30 / 85

Q30.What is the difference between TDD and BDD?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "difference between TDD and BDD" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

TDD writes a failing unit test before the code (red → green → refactor). BDD expresses behavior as scenarios in natural language (Given/When/Then) that non-technical stakeholders can read. BDD frameworks (Cucumber, SpecFlow, Behave) map those scenarios to executable steps.

Build your automation skills with our Cypress Testing Complete Beginner's Guide.

Tips to remember
  • Open with a one-sentence definition of difference between TDD and BDD, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between TDD and BDD cleanly.
RelatedQ28Q32
← Q29Q31 →
Confidence check

If you can confidently answer the Automation Testing Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

5. Selenium Interview Questions

Easy Very Common 1 minQ31 / 85

Q31.What are the components of the Selenium suite?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "components of the Selenium suite" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Selenium WebDriver (browser automation API), Selenium IDE (record-and-playback Chrome/Firefox plugin), Selenium Grid (parallel/distributed execution), and Selenium Manager (driver and browser management, default since Selenium 4.11).

Tips to remember
  • Open with a one-sentence definition of components of the Selenium suite, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise components of the Selenium suite cleanly.
  • Call out test isolation and shared-state risk (data, sessions, ports) before you talk about worker counts.
RelatedQ29Q33
← Q30Q32 →
Medium Very Common 1 minQ32 / 85

Q32.What is the difference between findElement and findElements?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "difference between findElement and findElements" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

findElement returns the first matching WebElement or throws NoSuchElementException. findElements returns a (possibly empty) list of all matching elements and never throws.

Tips to remember
  • Open with a one-sentence definition of difference between findElement and findElements, then a concrete Career & Interview Prep example — never start with history or theory.
  • Be ready to whiteboard the difference between findElement and findElements snippet live — panels often ask you to type it, not describe it.
RelatedQ30Q34
← Q31Q33 →
Easy Very Common 1 minQ33 / 85

Q33.What are the different locator strategies in Selenium?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "different locator strategies" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

ID, Name, ClassName, TagName, LinkText, PartialLinkText, CSS Selector, and XPath. The recommended priority order is ID > CSS > XPath for stability and speed.

Tips to remember
  • Open with a one-sentence definition of different locator strategies, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise different locator strategies cleanly.
  • Say explicitly that you prefer CSS/relative locators and only fall back to XPath for text or axes — panels grade locator hygiene here.
RelatedQ31Q35
← Q32Q34 →
Medium Common 1 minQ34 / 85

Q34.What is the difference between driver.close() and driver.quit()?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "difference between driver.close() and driver.quit()" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

close() closes the currently focused browser window. quit() closes all windows opened by the WebDriver session and ends the driver process.

Tips to remember
  • Open with a one-sentence definition of difference between driver.close() and driver.quit(), then a concrete Career & Interview Prep example — never start with history or theory.
  • Be ready to whiteboard the difference between driver.close() and driver.quit() snippet live — panels often ask you to type it, not describe it.
RelatedQ32Q36
← Q33Q35 →
Easy Common 1 minQ35 / 85

Q35.What is an implicit vs explicit wait?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "implicit vs explicit wait" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Implicit wait tells WebDriver to poll the DOM for a specified time when finding elements. Explicit wait (WebDriverWait + ExpectedConditions) waits for a specific condition on a specific element. Best practice in 2026 is to avoid implicit waits entirely and use only explicit waits.

Tips to remember
  • Open with a one-sentence definition of implicit vs explicit wait, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise implicit vs explicit wait cleanly.
  • State that you never mix wait strategies and never use a hard sleep, then give the timeout value you actually run in CI.
RelatedQ33Q37
← Q34Q36 →
Medium Common 1 minQ36 / 85

Q36.What is the Page Factory?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "Page Factory" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A deprecated-but-still-common pattern that initializes Page Object elements using @FindBy annotations. Modern codebases prefer the constructor-based Page Object pattern without Page Factory because it is simpler and faster.

Tips to remember
  • Open with a one-sentence definition of Page Factory, then a concrete Career & Interview Prep example — never start with history or theory.
  • Be ready to whiteboard the Page Factory snippet live — panels often ask you to type it, not describe it.
  • Add one sentence on what does NOT belong in a page object (assertions, test data) — that boundary is what separates mid from senior answers.
RelatedQ34Q38
← Q35Q37 →
Easy Common 1 minQ37 / 85

Q37.How do you handle dynamic elements in Selenium?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Hands-on "how would you handle dynamic elements" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use stable, semantic locators (data-testid attributes), explicit waits with ExpectedConditions, JavaScript-based scrolling into view, and custom JavaScriptExecutor snippets. Avoid XPath with absolute indices.

Tips to remember
  • Walk through handle dynamic elements as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise handle dynamic elements cleanly.
  • Say explicitly that you prefer CSS/relative locators and only fall back to XPath for text or axes — panels grade locator hygiene here.
RelatedQ35Q39
← Q36Q38 →
Medium Common 1 minQ38 / 85

Q38.What is Selenium 4's relative locator?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "Selenium 4's relative locator" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Locator strategies like above, below, toLeftOf, toRightOf, and near that find elements based on their position relative to another element. Useful when stable IDs are unavailable.

Tips to remember
  • Open with a one-sentence definition of Selenium 4's relative locator, then a concrete Career & Interview Prep example — never start with history or theory.
  • Be ready to whiteboard the Selenium 4's relative locator snippet live — panels often ask you to type it, not describe it.
RelatedQ36Q40
← Q37Q39 →
Easy Common 1 minQ39 / 85

Q39.How do you run Selenium tests in parallel?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Hands-on "how would you run Selenium tests in parallel" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Options: Selenium Grid (Hub + Nodes) on local VMs, Selenium Grid on Kubernetes, cloud providers (BrowserStack, Sauce Labs, LambdaTest), or TestNG/JUnit parallel attributes on a single machine. In 2026 most teams use cloud grids or containers.

Tips to remember
  • Walk through run Selenium tests in parallel as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise run Selenium tests in parallel cleanly.
  • Call out test isolation and shared-state risk (data, sessions, ports) before you talk about worker counts.
RelatedQ37Q41
← Q38Q40 →
Easy Common 1 minQ40 / 85

Q40.Selenium vs Playwright vs Cypress — how do you choose?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Comparison questions like this test whether you understand Selenium vs Playwright vs Cypress — how do you choose at a design level — not just that both exist, but when to pick one over the other. Panels use it to see if you can defend a trade-off with a real project example.

Detailed explanation

Selenium: broadest language and browser support, mature. Playwright: best-in-class for new greenfield projects that need auto-waiting, tracing, and multi-tab. Cypress: best developer experience for front-end-heavy teams. The choice is usually ecosystem fit, not raw capability.

Drill deeper at Selenium interview questions hub.

Tips to remember
  • Structure the answer as a small table in your head: dimension, option A, option B — and close with "I'd pick X when Y".
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Selenium vs Playwright vs Cypress — how do you choose cleanly.
  • State that you never mix wait strategies and never use a hard sleep, then give the timeout value you actually run in CI.
RelatedQ38Q42
← Q39Q41 →
Confidence check

If you can confidently answer the Selenium Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

6. Cypress Interview Questions

Medium Common 1 minQ41 / 85

Q41.What makes Cypress different from Selenium?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on What makes Cypress different from Selenium and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Cypress runs inside the browser (not as a remote WebDriver), so it has native access to the DOM, network, storage, and timers. This enables auto-waiting, time-travel debugging, real-time reloads, and stubbing of network calls. The trade-off is a smaller set of supported browsers (Chrome, Edge, Firefox, WebKit) and no native support for multiple tabs or cross-origin iframes.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on What makes Cypress different from Selenium over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise What makes Cypress different from Selenium cleanly.
  • Finish by saying you always return to the default content after frame work — forgetting that is the classic failure this question hunts for.
RelatedQ39Q43
← Q40Q42 →
Medium Common 1 minQ42 / 85

Q42.What is a Cypress fixture?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "Cypress fixture" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A static file (typically JSON) in the cypress/fixtures directory that holds test data. Loaded with cy.fixture('users.json'). Use fixtures for reusable, deterministic data; use factories for unique-per-test data.

Tips to remember
  • Open with a one-sentence definition of Cypress fixture, then a concrete Career & Interview Prep example — never start with history or theory.
  • Be ready to whiteboard the Cypress fixture snippet live — panels often ask you to type it, not describe it.
  • Explain setup/teardown ordering and what runs per-test vs per-suite; ordering mistakes are the follow-up question.
RelatedQ40Q44
← Q41Q43 →
Medium Common 1 minQ43 / 85

Q43.What are Cypress custom commands?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "Cypress custom commands" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Reusable functions defined in cypress/support/commands.js that wrap sequences of Cypress commands. cy.login('admin') is a custom command. They are the Cypress equivalent of POM helper methods.

Tips to remember
  • Open with a one-sentence definition of Cypress custom commands, then a concrete Career & Interview Prep example — never start with history or theory.
  • Be ready to whiteboard the Cypress custom commands snippet live — panels often ask you to type it, not describe it.
  • Add one sentence on what does NOT belong in a page object (assertions, test data) — that boundary is what separates mid from senior answers.
RelatedQ41Q45
← Q42Q44 →
Medium Common 1 minQ44 / 85

Q44.How do you intercept network calls in Cypress?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Hands-on "how would you intercept network calls" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use cy.intercept('GET', '/api/users', { fixture: 'users.json' }) to stub a response, or cy.intercept('POST', '/api/orders').as('createOrder') and then cy.wait('@createOrder') to assert on a real call.

Tips to remember
  • Walk through intercept network calls as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the intercept network calls snippet live — panels often ask you to type it, not describe it.
  • Say when you'd mock versus hit the real dependency; unconditional mocking is a red flag for integration coverage.
RelatedQ42Q46
← Q43Q45 →
Medium Common 1 minQ45 / 85

Q45.How do you run Cypress in CI?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Hands-on "how would you run Cypress in CI" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use cypress run --headless --browser chrome --record --key <key> with the Cypress Dashboard, or run in your own CI pipeline (GitHub Actions, GitLab CI, Jenkins) and publish JUnit/Mochawesome reports. Cache ~/.cache/Cypress to speed up builds.

Tips to remember
  • Walk through run Cypress in CI as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the run Cypress in CI snippet live — panels often ask you to type it, not describe it.
  • Describe the pipeline stage order and what makes the build fail — a vague "we run tests in CI" answer stalls here.
RelatedQ43Q47
← Q44Q46 →
Easy Common 1 minQ46 / 85

Q46.What is component testing in Cypress?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "component testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Cypress can mount individual React, Vue, Angular, or Svelte components in isolation and test them against their props, events, and rendered output. It is faster than full E2E and lets you test components without spinning up the whole app.

To go deeper, follow our Cypress Testing Complete Beginner's Guide.

Tips to remember
  • Open with a one-sentence definition of component testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise component testing cleanly.
RelatedQ44Q48
← Q45Q47 →
Confidence check

If you can confidently answer the Cypress Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

7. API Testing Interview Questions

Easy Common 1 minQ47 / 85

Q47.What is REST?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "REST" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

REST (Representational State Transfer) is an architectural style for distributed systems. Constraints include statelessness, uniform interface, client-server separation, cacheability, layered system, and code-on-demand (optional). REST APIs typically use HTTP and JSON.

Tips to remember
  • Open with a one-sentence definition of REST, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise REST cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ45Q49
← Q46Q48 →
Easy Common 1 minQ48 / 85

Q48.What are the main HTTP methods?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "main HTTP methods" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

GET (read, safe, idempotent), POST (create, not idempotent), PUT (replace, idempotent), PATCH (partial update), DELETE (delete, idempotent), HEAD (headers only), OPTIONS (capabilities).

Tips to remember
  • Open with a one-sentence definition of main HTTP methods, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise main HTTP methods cleanly.
RelatedQ46Q50
← Q47Q49 →
Easy Common 1 minQ49 / 85

Q49.What is the difference between authentication and authorization?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "difference between authentication and authorization" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Authentication verifies who you are (login, JWT, OAuth token). Authorization verifies what you can do (RBAC, ABAC, scopes, claims). A user can authenticate successfully but be unauthorized to access a resource.

Tips to remember
  • Open with a one-sentence definition of difference between authentication and authorization, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between authentication and authorization cleanly.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ47Q51
← Q48Q50 →
Easy Common 1 minQ50 / 85

Q50.What status codes do you assert against?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on What status codes do you assert against and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

1xx informational, 2xx success (200 OK, 201 Created, 204 No Content), 3xx redirection, 4xx client error (400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 409 Conflict, 429 Too Many Requests), 5xx server error (500 Internal, 502 Bad Gateway, 503 Unavailable, 504 Gateway Timeout).

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on What status codes do you assert against over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise What status codes do you assert against cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ48Q52
← Q49Q51 →
Easy Common 1 minQ51 / 85

Q51.What is a contract test?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "contract test" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A test that validates the API matches its published specification (OpenAPI/Swagger). Tools: Pact, Dredd, Spectral, Prism. Contract tests catch breaking changes before they hit consumers.

Tips to remember
  • Open with a one-sentence definition of contract test, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise contract test cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ49Q53
← Q50Q52 →
Easy Common 1 minQ52 / 85

Q52.What is schema validation?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "schema validation" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Asserting that the API response matches the expected JSON schema (data types, required fields, formats). Tools: Ajv (Node), jsonschema (Python), RestAssured + Hamcrest matchers (Java), JSON Schema validators in Postman.

Tips to remember
  • Open with a one-sentence definition of schema validation, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise schema validation cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ50Q54
← Q51Q53 →
Easy Common 1 minQ53 / 85

Q53.How do you test GraphQL APIs?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Hands-on "how would you test GraphQL APIs" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Validate queries (correct shape), mutations (correct side effects), subscriptions (real-time events), error handling, performance (depth, complexity), and security (introspection off in production, query depth limits).

Tips to remember
  • Walk through test GraphQL APIs as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test GraphQL APIs cleanly.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ51Q55
← Q52Q54 →
Medium Common 1 minQ54 / 85

Q54.What is the difference between Postman and REST Assured?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "difference between Postman and REST Assured" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Postman is a GUI + CLI (Newman) tool great for exploration, manual testing, and shared collections. REST Assured is a Java DSL for automated API tests integrated with JUnit/TestNG. In 2026 most teams use both: Postman for exploration, REST Assured or Pact for automation.

For a hands-on walkthrough, see our API testing Q&A hub and API testing pillar guide.

Tips to remember
  • Open with a one-sentence definition of difference between Postman and REST Assured, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between Postman and REST Assured cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ52Q56
← Q53Q55 →
Confidence check

If you can confidently answer the API Testing Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

8. JMeter & Performance Testing Interview Questions

Easy Common 1 minQ55 / 85

Q55.What are the types of performance testing?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "types of performance testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Load — expected load. Stress — beyond expected load until failure. Spike — sudden bursts. Soak/Endurance — sustained load over hours/days to find memory leaks. Capacity — gradual ramp to find the maximum sustainable users.

Tips to remember
  • Open with a one-sentence definition of types of performance testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise types of performance testing cleanly.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ53Q57
← Q54Q56 →
Easy Common 1 minQ56 / 85

Q56.What is the difference between throughput and response time?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "difference between throughput and response time" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Throughput = transactions per second the system serves. Response time = time to serve one transaction. They are inversely related under load until saturation, after which response time climbs while throughput plateaus or drops.

Tips to remember
  • Open with a one-sentence definition of difference between throughput and response time, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between throughput and response time cleanly.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ54Q58
← Q55Q57 →
Easy Common 1 minQ57 / 85

Q57.What are the JMeter components you use daily?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "JMeter components you use daily" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Thread Group, Samplers (HTTP Request, JDBC), Listeners (View Results Tree, Summary Report, Aggregate Report, Backend Listener), Assertions (Response, Duration, JSON), Controllers (Loop, Transaction, If), Timers, and Config Elements (HTTP Header, CSV Data Set).

Tips to remember
  • Open with a one-sentence definition of JMeter components you use daily, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise JMeter components you use daily cleanly.
  • Call out test isolation and shared-state risk (data, sessions, ports) before you talk about worker counts.
RelatedQ55Q59
← Q56Q58 →
Medium Common 1 minQ58 / 85

Q58.How do you run JMeter in CI/CD?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Hands-on "how would you run JMeter in CI/CD" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use the JMeter Maven Plugin, JMeter Gradle Plugin, or jmeter -n -t test.jmx -l result.jtl -e -o report/ in headless mode. Publish the HTML report as a CI artifact and fail the build when SLA thresholds are violated.

Tips to remember
  • Walk through run JMeter in CI/CD as numbered steps and call out the tool, command, or API used at each step.
  • Be ready to whiteboard the run JMeter in CI/CD snippet live — panels often ask you to type it, not describe it.
  • Describe the pipeline stage order and what makes the build fail — a vague "we run tests in CI" answer stalls here.
RelatedQ56Q60
← Q57Q59 →
Easy Common 1 minQ59 / 85

Q59.JMeter vs Gatling vs k6 — when to choose which?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Comparison questions like this test whether you understand JMeter vs Gatling vs k6 — when to choose which at a design level — not just that both exist, but when to pick one over the other. Panels use it to see if you can defend a trade-off with a real project example.

Detailed explanation

JMeter — GUI-rich, broad protocol support, mature. Gatling — code-as-config in Scala, very high throughput. k6 — JavaScript, great developer experience, native Kubernetes integration. Pick by team skills and CI/CD integration.

Tips to remember
  • Structure the answer as a small table in your head: dimension, option A, option B — and close with "I'd pick X when Y".
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise JMeter vs Gatling vs k6 — when to choose which cleanly.
  • Mention pinned browser images and cleanup of containers between runs — panels look for CI cost awareness.
RelatedQ57Q61
← Q58Q60 →
Medium Common 1 minQ60 / 85

Q60.What is correlation?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "correlation" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Extracting dynamic values from a server response (session ID, CSRF token, OTP) and feeding them into subsequent requests. In JMeter use the Regular Expression Extractor, JSON Extractor, Boundary Extractor, or the __regexFunction. Without correlation, recorded scripts fail on replay.

Build a full JMeter plan step by step in our JMeter Performance Testing Step-by-Step Guide.

Tips to remember
  • Open with a one-sentence definition of correlation, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise correlation cleanly.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ58Q62
← Q59Q61 →
Confidence check

If you can confidently answer the JMeter & Performance Testing Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

9. AI in Testing Interview Questions

Easy Common 1 minQ61 / 85

Q61.How is AI used in software testing in 2026?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on How is AI used in software testing in 2026 and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Test case generation from requirements and code, automated test repair when locators break, visual regression detection, log anomaly detection, predictive defect analytics, AI-generated test data, autonomous exploratory testing agents, and natural-language test authoring.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on How is AI used in software testing in 2026 over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise How is AI used in software testing in 2026 cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ59Q63
← Q60Q62 →
Easy Common 1 minQ62 / 85

Q62.What is self-healing test automation?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "self-healing test automation" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

When a locator breaks, AI engines analyze alternative locators, DOM structure, and historical runs to recover automatically. Tools: Healenium, Mabl, Testim, Functionize. Self-healing reduces maintenance but must be audited — silent healing can hide real bugs.

Tips to remember
  • Open with a one-sentence definition of self-healing test automation, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise self-healing test automation cleanly.
RelatedQ60Q64
← Q61Q63 →
Easy Common 1 minQ63 / 85

Q63.What are the risks of AI in testing?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "risks of AI in testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Hallucinated test logic, biased training data, opaque decisions (hard to debug), over-reliance on flaky AI suggestions, license and IP concerns around generated code, and the false sense of coverage when AI-generated tests are shallow.

Tips to remember
  • Open with a one-sentence definition of risks of AI in testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise risks of AI in testing cleanly.
  • Quote a real flake-rate number before and after your fix; measured outcomes score far higher than "we added retries".
RelatedQ61Q65
← Q62Q64 →
Medium Occasional 1 minQ64 / 85

Q64.What is an AI testing agent?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "AI testing agent" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

An LLM-powered agent that can navigate a UI, observe state, decide actions, and verify outcomes to achieve a high-level goal (e.g., "create a customer and verify the welcome email"). Examples in 2026: Anthropic Computer Use, OpenAI Operator, Microsoft Magentic-One, custom Selenium/Cypress agents.

Read the full landscape in our AI in Software Testing: Tools, Trends, and Careers.

Tips to remember
  • Open with a one-sentence definition of AI testing agent, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise AI testing agent cleanly.
RelatedQ62Q66
← Q63Q65 →
Confidence check

If you can confidently answer the AI in Testing Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

10. ISTQB Certification Interview Questions

Easy Occasional 1 minQ65 / 85

Q65.What are the seven testing principles?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "seven testing principles" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

1) Testing shows the presence of defects, not their absence. 2) Exhaustive testing is impossible. 3) Early testing saves time and money. 4) Defects cluster together. 5) Beware of the pesticide paradox. 6) Testing is context-dependent. 7) Absence-of-errors is a fallacy.

Tips to remember
  • Open with a one-sentence definition of seven testing principles, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise seven testing principles cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ63Q67
← Q64Q66 →
Easy Occasional 1 minQ66 / 85

Q66.What is the pesticide paradox?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "pesticide paradox" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

If the same tests are repeated, they stop finding new bugs. To overcome it, regularly review and update tests, target new and modified areas, and use exploratory testing.

Tips to remember
  • Open with a one-sentence definition of pesticide paradox, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise pesticide paradox cleanly.
RelatedQ64Q68
← Q65Q67 →
Easy Occasional 1 minQ67 / 85

Q67.What is the difference between root cause and symptom in testing?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "difference between root cause and symptom in testing" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A symptom is the observable failure (a 500 error on checkout). The root cause is the underlying defect (a null pointer in the discount service when the cart has zero items). Root cause analysis prevents recurrence.

Tips to remember
  • Open with a one-sentence definition of difference between root cause and symptom in testing, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between root cause and symptom in testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ65Q69
← Q66Q68 →
Easy Occasional 1 minQ68 / 85

Q68.What are the test types in ISTQB?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "test types in ISTQB" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Functional (what the system does), non-functional (how well it does it — performance, security, usability, compatibility), structural (white-box coverage), and change-related (confirmatory & regression).

Tips to remember
  • Open with a one-sentence definition of test types in ISTQB, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test types in ISTQB cleanly.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ66Q70
← Q67Q69 →
Easy Occasional 1 minQ69 / 85

Q69.What is the V-model?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "V-model" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

An extension of the waterfall where each development phase has a corresponding testing phase: Requirements → Acceptance Testing, System Design → System Testing, Component Design → Integration Testing, Coding → Unit Testing. It emphasizes test planning in parallel with development.

Tips to remember
  • Open with a one-sentence definition of V-model, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise V-model cleanly.
  • Call out test isolation and shared-state risk (data, sessions, ports) before you talk about worker counts.
RelatedQ67Q71
← Q68Q70 →
Confidence check

If you can confidently answer the ISTQB Certification Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

11. Scenario-Based Software Testing Interview Questions

Easy Occasional 1 minQ70 / 85

Q70.You join a new project with no documentation and no automation. Where do you start in your first week?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on You join a new project with no documentation and no automation. Where do you start in your first week and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Day 1–2: charter exploratory testing sessions to map the product. Day 3–4: identify the top 5 user journeys and build a smoke checklist. Day 5: write 10 critical regression test cases. Week 2: propose a test strategy, automation pyramid, and tooling decisions to the team.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on You join a new project with no documentation and no automation. Where do you start in your first week over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise You join a new project with no documentation and no automation. Where do you start in your first week cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ68Q72
← Q69Q71 →
Easy Occasional 1 minQ71 / 85

Q71.A senior developer says your bug is "not a bug." How do you respond?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on A senior developer says your bug is "not a bug." How do you respond and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Step back, re-read the requirement and acceptance criteria, reproduce the bug calmly, gather logs/screenshots, ask them which step they disagree with, and escalate politely to the PM if needed. Never let ego drive the discussion — facts and the spec decide.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on A senior developer says your bug is "not a bug." How do you respond over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise A senior developer says your bug is "not a bug." How do you respond cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ69Q73
← Q70Q72 →
Easy Occasional 1 minQ72 / 85

Q72.Production is down. Walk me through your first 15 minutes.

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on Production is down. Walk me through your first 15 minutes and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Confirm impact (users, severity), open a war room, check recent deployments, run the smoke suite, attach logs to the incident, communicate status to stakeholders every 5–10 minutes, and write the timeline for the post-incident review.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on Production is down. Walk me through your first 15 minutes over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Production is down. Walk me through your first 15 minutes cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ70Q74
← Q71Q73 →
Easy Occasional 1 minQ73 / 85

Q73.Your test suite takes 6 hours. How do you cut it to 1 hour?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on Your test suite takes 6 hours. How do you cut it to 1 hour and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Profile to find slow tests, run them in parallel, move API coverage up the pyramid, remove redundant tests, quarantine flaky ones, run smoke on every PR and full suite nightly, and use test impact analysis to run only the tests touching changed code.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on Your test suite takes 6 hours. How do you cut it to 1 hour over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Your test suite takes 6 hours. How do you cut it to 1 hour cleanly.
  • Quote a real flake-rate number before and after your fix; measured outcomes score far higher than "we added retries".
RelatedQ71Q75
← Q72Q74 →
Easy Occasional 1 minQ74 / 85

Q74.How would you test a login page?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Hands-on "how would you test a login page" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Functional: valid creds, invalid creds, locked account, forgot password, MFA, OAuth, SSO. Validation: empty fields, SQL injection, XSS, long strings, special characters. Non-functional: rate limiting, brute force protection, accessibility (screen reader), performance under 10k concurrent logins. Security: cookie flags, session timeout, CSRF.

Tips to remember
  • Walk through test a login page as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test a login page cleanly.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ72Q76
← Q73Q75 →
Easy Occasional 1 minQ75 / 85

Q75.How would you test an e-commerce checkout flow?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Hands-on "how would you test an e-commerce checkout flow" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Map every path: guest checkout, registered checkout, saved cards, new cards, Apple Pay, PayPal, BNPL, promo codes, gift cards, taxes, shipping methods, address validation, partial failures (payment fails after inventory reserved), idempotency on retries, refunds, and 3DS/SCA.

Tips to remember
  • Walk through test an e-commerce checkout flow as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise test an e-commerce checkout flow cleanly.
RelatedQ73Q77
← Q74Q76 →
Confidence check

If you can confidently answer the Scenario-Based Software Testing Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

12. QA Lead / Manager Interview Questions

Easy Occasional 1 minQ76 / 85

Q76.What metrics do you track?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on What metrics do you track and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Defect density (per KLOC or per story point), defect leakage to production, mean time to detect (MTTD), mean time to repair (MTTR), test coverage by requirement, automation coverage, flake rate, and cycle time from PR to deploy. Avoid vanity metrics like "bugs found."

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on What metrics do you track over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise What metrics do you track cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ74Q78
← Q75Q77 →
Easy Occasional 1 minQ77 / 85

Q77.How do you scale QA from 3 to 15 testers?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Hands-on "how would you scale QA from 3 to 15 testers" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Invest in the test pyramid, establish clear test strategy templates, build self-service test data tooling, train on domain knowledge, define a code review process for automation, and create centers of excellence (mobile, performance, security).

Tips to remember
  • Walk through scale QA from 3 to 15 testers as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise scale QA from 3 to 15 testers cleanly.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ75Q79
← Q76Q78 →
Easy Occasional 1 minQ78 / 85

Q78.How do you handle a tester who refuses to automate?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Hands-on "how would you handle a tester who refuses to automate" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Understand the "why" first — fear, lack of training, unclear value. Pair-program with them, give small wins, show time saved, and tie automation outcomes to their goals. Avoid mandates; build believers.

Tips to remember
  • Walk through handle a tester who refuses to automate as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise handle a tester who refuses to automate cleanly.
RelatedQ76Q80
← Q77Q79 →
Easy Occasional 1 minQ79 / 85

Q79.How do you prioritize test efforts?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Hands-on "how would you prioritize test efforts" questions reveal whether you've actually shipped Career & Interview Prep code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Use risk-based testing: combine likelihood of failure (complexity, churn, defect history) with business impact (revenue, customer trust, compliance). Test the highest-risk areas first, then taper off. Re-prioritize weekly.

Tips to remember
  • Walk through prioritize test efforts as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise prioritize test efforts cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ77Q81
← Q78Q80 →
Easy Occasional 1 minQ80 / 85

Q80.What is your test strategy for a greenfield project?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "your test strategy for a greenfield project" to confirm you can define the concept in one crisp line before going deeper. In Career & Interview Prep rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

T-shape: deep unit tests from day one, contract tests between services, smoke E2E for top journeys, performance baselines from the first release, and production observability (synthetic checks, RUM, error budgets).

Tips to remember
  • Open with a one-sentence definition of your test strategy for a greenfield project, then a concrete Career & Interview Prep example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise your test strategy for a greenfield project cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ78Q82
← Q79Q81 →
Confidence check

If you can confidently answer the QA Lead / Manager Interview Questions questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

13. Behavioral & HR Interview Questions for QA

Easy Occasional 1 minQ81 / 85

Q81.Tell me about a bug you found that nobody else did.

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on Tell me about a bug you found that nobody else did and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Pick a real story with measurable impact (revenue saved, customer trust protected). Show your curiosity — the extra test you designed that found it.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on Tell me about a bug you found that nobody else did over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Tell me about a bug you found that nobody else did cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ79Q83
← Q80Q82 →
Easy Occasional 1 minQ82 / 85

Q82.Describe a disagreement with a developer and how you resolved it.

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Open-ended "explain disagreement with a developer and how you resolved it" prompts test how you structure a technical answer under pressure. Panels look for a clear opening definition, one worked example, and a closing sentence on the pitfall they were about to ask about next.

Detailed explanation

Show respect for the developer, the data you gathered, and the resolution. Avoid "I won" framing — show collaboration.

Tips to remember
  • Use a 3-part frame for disagreement with a developer and how you resolved it: what it is → how it works → one gotcha you've hit in a real Career & Interview Prep project.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise disagreement with a developer and how you resolved it cleanly.
RelatedQ80Q84
← Q81Q83 →
Easy Occasional 1 minQ83 / 85

Q83.Tell me about a time you missed a critical bug.

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on Tell me about a time you missed a critical bug and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Own it. Explain the root cause, what you changed in process to prevent recurrence (new test technique, automation, review step), and the lesson learned.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on Tell me about a time you missed a critical bug over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Tell me about a time you missed a critical bug cleanly.
  • Explain how you test asynchronous flows (polling, consumer assertions, timeouts) rather than treating it as a sync call.
RelatedQ81Q85
← Q82Q84 →
Easy Occasional 1 minQ84 / 85

Q84.Why do you want to work in QA / test?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

"Why" questions on you want to work in QA / test probe your reasoning, not your memory. Strong candidates connect the choice to a business or reliability outcome — flaky tests, slower feedback loop, or missed defects — instead of parroting a rule.

Detailed explanation

Connect your curiosity, systems thinking, and care for users to the role. Mention specific recent advances (AI testing, shift-left) that excite you.

Tips to remember
  • Tie the "why" for you want to work in QA / test back to a measurable outcome — flake rate, execution time, defect leakage — instead of an opinion.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise you want to work in QA / test cleanly.
RelatedQ82
← Q83Q85 →
Easy Occasional 1 minQ85 / 85

Q85.Where do you see yourself in 3 years?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

This Career & Interview Prep question checks whether you can go beyond textbook knowledge on Where do you see yourself in 3 years and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Describe a growth path that fits the company — senior SDET, test architect, engineering manager, or platform QA. Show ambition and loyalty.

Tips to remember
  • Anchor the answer in a real Career & Interview Prep project — panels reward specificity on Where do you see yourself in 3 years over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Where do you see yourself in 3 years cleanly.
RelatedQ83
← Q84
Confidence check

If you can confidently answer the Behavioral & HR Interview Questions for QA questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

Quick revision

  1. Q1: What is software testing — Software testing is the process of evaluating a system to find defects, verify that it meets specified requirements, and validate that it solves the user's problem.
  2. Q2: What is the difference between QA, QC, and testing — QA (Quality Assurance) is process-focused — the entire set of planned activities that prevent defects.
  3. Q3: What is the SDLC — SDLC (Software Development Life Cycle) is the end-to-end framework for building software, typically with phases: Requirement Analysis → Planning → Design → Implementation → Testing
  4. Q4: What is the STLC — STLC (Software Testing Life Cycle) is the testing-specific subset of the SDLC: Requirement Analysis → Test Planning → Test Case Design → Test Environment Setup → Test Execution → T
  5. Q5: What is verification vs validation — Verification answers "are we building the product right?" through reviews, walkthroughs, and inspections — done before code.

Frequently asked questions

1.How many software testing interview questions should I prepare for?
Quality over quantity. Prepare 60–80 strong answers across categories, but rehearse them out loud. Interviewers ask 8–15 questions per round, so being confident and articulate on the fundamentals matters more than memorizing 500 questions.
2.Are these questions valid for freshers as well as experienced testers?
Yes — the guide is tagged by experience level. Freshers should master sections 2–4 and 10. Mid-level candidates should add 5–8 and 11. Senior and lead candidates should focus on 9, 11, and 12 plus 13 (behavioral).
3.Do companies still ask ISTQB questions in 2026?
Yes, especially in enterprise, finance, and government roles. Section 10 covers the most frequently asked syllabus items.
4.Should I memorize answers?
No. Internalize concepts, then express them in your own words with a real example from your work. Memorized answers sound mechanical and interviewers spot them instantly.
5.What tools should I be hands-on with?
Pick at least one from each category: test management (Jira + Zephyr/Xray), automation (Playwright, Cypress, or Selenium), API (Postman or REST Assured), performance (JMeter or k6), CI (GitHub Actions or GitLab CI), and one AI-assisted tool (Mabl, Testim, or Healenium).
6.How long does preparation take?
For a focused 2–3 hour daily schedule, 7–10 days is enough to feel confident for most mid-level interviews. For senior roles, add 2 weeks of mock interviews with peers.
7.Where can I practice live?
Use platforms like HackerRank, LeetCode (for coding-heavy SDET roles), InterviewBit, and our own AI Mock Interview at /ai-mock-interview.

Was this article helpful?

Cluster · QA Career

More from QA Interview Questions

Behavioral, framework, coding — full interview prep.

Pillar guide · 11 articles
More in this cluster
From the QA Career pillar
Topic mapConcepts · Tools · People · Standards

Related concepts, tools & standards around Career & Interview Prep

A quick reference of the people, companies, frameworks and technologies most often mentioned alongside Career & Interview Prep in real QA teams — useful when you're mapping a learning path, preparing for interviews, or scoping a new project.

Core testing concepts
Prompt Engineering for QALLM-Assisted Test GenerationTest PyramidShift-Left TestingBehavior-Driven DevelopmentTest-Driven DevelopmentPage Object ModelContract TestingExploratory TestingRisk-Based Testing
Testing tools
GitHub CopilotCursorPlaywright MCPSeleniumPlaywrightCypressAppiumJMeterPostmanTestRail
Programming languages
JavaPythonJavaScriptTypeScriptC#SQL
Test frameworks
TestNGJUnit 5pytestCucumber (BDD)REST AssuredRobot Framework
Automation tools
WebDriverIOPuppeteerKarate DSLDetox (React Native)Nightwatch.js
API testing tools
GraphQL PlaygroundgRPCurlWireMockPostmanInsomniaREST AssuredSwagger / OpenAPIPact (Contract Testing)
DevOps & CI/CD
JenkinsGitHub ActionsGitLab CI/CDCircleCIDockerKubernetes
Cloud & device platforms
AWSGoogle CloudMicrosoft AzureSauce LabsLambdaTest
Certifications worth knowing
ISTQB Foundation LevelISTQB Advanced — Test AnalystISTQB Agile TesterCertified Selenium ProfessionalAWS Certified DevOps EngineerCertified ScrumMaster (CSM)
Related interview topics
Selenium Interview Q&APlaywright Interview Q&AAPI Testing Interview Q&ASQL Interview Q&ASDET Interview Q&AManual Testing Interview Q&A
Thought leaders to follow
Kent BeckLisa CrispinJanet GregoryJames BachMichael BoltonAngie Jones
Companies hiring for this skill
GoogleMicrosoftAmazonMetaNetflixAtlassianThoughtWorksInfosysTCSWipro

Key takeaways

  • Master the fundamentals before tackling advanced Career & Interview Prep scenarios.
  • Always explain trade-offs — interviewers reward judgement, not memorisation.
  • Use real project examples; generic answers blend in.
  • Practice answers out loud — written prep doesn't transfer to live rounds.
  • Revise the 30-second cheat sheet the night before your interview.
  • Keep one strong scenario story ready for every section above.
Start a free AI mock interview
Run a live QA mock interview tailored to this topic and get per-skill scoring in minutes.
Read Start a free AI mock interview
ATS Resume Review
Free resume scan tuned for QA roles.
Read ATS Resume Review
QA Practice Hub
Hands-on labs for test design and automation.
Read QA Practice Hub
QA Jobs Radar
Fresh SDET & QA roles, updated daily.
Read QA Jobs Radar

Career & Interview Prep jobs hiring now

Live, indexable Career & Interview Prep openings — updated daily in Jobs Radar.

Browse all QA jobs on Jobs Radar

Loading current openings…

Home

Discussion

Ask a question, share your experience, or correct us. Be kind — real people are reading.

?
Sign in to join the discussion →