What should you focus on for a manual testing interview?
Can you explain testing terms and when to use them?
The question about testing types and their uses appeared in 9 of 245 interviews. Check whether you can explain when you would use each type, not just name it. Other common questions ask you to compare ideas:
- How do verification and validation differ?
- How does white-box testing differ from black-box testing?
- When would you use unit, integration, or end-to-end tests?
- What is the difference between smoke, sanity, and regression testing?
For each comparison, can you explain both the meaning and when you would use it?
Can you explain how you would plan the work?
Test planning and QA process came up in 54 of 245 interviews. The questions cover requirements, acceptance criteria, test plans, and team responsibilities. Check whether you can explain how you would set up testing from scratch, not just define a test plan.
- What belongs in a test plan, and how does it differ from a test strategy?
- How would you use requirements and acceptance criteria to choose tests?
- Which testing work would you own, and where would you work with the team?
Can you choose what to automate and what to keep manual?
This question appeared in 9 of 245 interviews and includes working under tight deadlines. Explain when a test is ready to automate. Reviews of real answers noted a missing link between feature stability, frequency of change, and the decision to automate.
Can you explain how your choice changes when a feature changes often? What would you keep manual under a tight deadline? Check whether your answer also covers test maintenance, unstable tests, and where tests run in CI/CD.
Can you choose which login tests to run first?
The login-page question asks for positive, negative, edge-case, and security scenarios. Reviews of real answers noted missing priorities based on security risk and user impact, and missing explanations of what to test first with limited time.
Give your tests a clear order. Which would you run first? Which would you leave until later? Explain that order using security risk and user impact, rather than stopping at a list of tests.
Can you explain checks beyond the screen?
The questions also cover data, bugs, releases, and AI. Check whether you can answer these:
- How would you check reporting accuracy and permissions?
- What would you put in a bug report so engineering can reproduce the issue?
- Which quality measures and test results would you report to support release sign-off?
- How do you use AI in testing, and where is human judgment still essential?
Who gets asked Manual Testing
The 20 most asked Manual Testing questions
Counted by interview, not by mention: a question asked twice in one conversation counts once.
What types of software testing do you know, and when would you use each?
Asked in 9 of 245 interviews · last asked Oct 19 · Concept · Junior
Show answer
Unit testing checks small code parts; integration testing checks how parts work together. System testing checks the complete product, while acceptance testing checks whether it meets user and business needs. Functional testing checks features; non-functional testing checks qualities like speed, security, and usability. Regression testing checks that changes have not broken existing behavior.
- Smoke testing checks critical functions before deeper testing of a build.
- Retesting checks whether a specific defect is fixed; regression testing looks for problems caused by changes.
- Exploratory testing combines learning, test design, and execution to find problems beyond prepared test cases.
- Testing levels describe scope; testing types describe purpose. Functional and non-functional tests can run at different levels.
What the interviewer checks: The interviewer checks whether you understand testing levels and types and can choose them for the right purpose.
Other ways it was asked
- “What types of software testing do you know?”
- “What are the different types of software testing?”
- “How would you explain the different types of software testing, with examples?”
How do you decide which tests to automate and which to keep manual, especially under tight deadlines?
Asked in 9 of 245 interviews · last asked Oct 18 · Concept · Senior
Show answer
I automate stable, repeatable tests that run often and protect important features. I keep exploratory, usability, and fast-changing tests manual. Under tight deadlines, I test the biggest risks first and automate only where setup and upkeep are worth the time saved. I stop automating a test when its cost outweighs its value.
- Good automation candidates have clear expected results and frequent reuse, such as core regression tests.
- Wait for features to stabilize if frequent changes would cause repeated script updates.
- Keep tests manual when they need human judgment or will rarely run.
- Under tight deadlines, prioritize risk coverage over building new automation.
What the interviewer checks: The interviewer checks whether you balance risk, feature stability, time saved, and maintenance effort.
Common mistake (in 3 of 6 reviewed answers): Many answers forget that fast-changing features may be better tested manually until they stabilize.
Other ways it was asked
- “How do you decide what to automate and what to test manually? What is worth automating?”
- “How do you decide what to automate, what not to automate, and when to stop automating a test?”
- “How do you decide what to automate versus what you keep manual?”
What are verification and validation, and how do they differ?
Asked in 7 of 245 interviews · last asked Oct 1 · Concept · Junior
Show answer
Verification checks whether a product meets its specified requirements. Validation checks whether it meets user needs and works for its intended use. In simple terms, verification asks, “Are we building the product right?” Validation asks, “Are we building the right product?”
- Verification can use reviews and tests; it is not limited to checking documents.
- Validation often includes testing real user tasks, such as acceptance testing.
- A product can meet its specification but still fail to meet user needs.
What the interviewer checks: The interviewer checks whether you understand the difference between meeting specifications and meeting user needs.
Other ways it was asked
- “What is the difference between verification and validation?”
- “What is the difference between validation and verification?”
- “What do you mean by verification and validation?”
How would you test a login page, including positive, negative, edge-case, and security scenarios?
Asked in 6 of 245 interviews · last asked Oct 12 · Scenario · Junior
Show answer
I would test successful login first, then failed login and access to protected pages without signing in. Next, I would check input limits, repeated attempts, and session handling against the requirements. With limited time, I would prioritize unauthorized access, password exposure, and failures that block valid users.
- Positive: Valid credentials open the correct account; logout ends the session and blocks protected pages.
- Negative: Wrong passwords, unknown users, empty fields, and disabled accounts fail without revealing whether an account exists.
- Edge cases: Check input length limits, spaces, case rules, repeated clicks, and expired sessions.
- Security: Check HTTPS, hidden passwords, login attempt limits, injection attempts, and passwords staying out of URLs and logs.
What the interviewer checks: The interviewer is checking whether you cover normal use, failures, boundaries, and security while prioritizing risk and user impact.
Common mistake (in 3 of 9 reviewed answers): Many answers forget that time may be limited, so explain which tests you would run first and why.
Other ways it was asked
- “How would you approach testing a new login feature to ensure it is both secure and functional?”
- “Could you walk me through how you would test a new login feature to make sure it works correctly and keeps user data safe?”
- “Which edge cases would you prioritize when testing a login feature?”
What is white-box testing, and how does it differ from black-box testing?
Asked in 5 of 245 interviews · last asked Aug 25 · Concept · Junior
Show answer
White-box testing uses knowledge of the code to design tests for internal logic, such as conditions and branches. Black-box testing checks inputs and outputs against requirements without using knowledge of the code. White-box testing checks how the software works; black-box testing checks what it does.
- White-box tests target code structure and logic.
- Black-box tests target expected behavior from requirements.
- Both approaches can find defects the other may miss.
- White-box testing usually needs programming knowledge.
What the interviewer checks: The interviewer is checking whether you understand how code knowledge changes test design.
Other ways it was asked
- “What is the difference between black-box and white-box testing?”
- “Can you compare black-box testing and white-box testing?”
- “Can you compare black-box and white-box testing?”
What is a test plan, and how does it differ from a test strategy?
Asked in 5 of 245 interviews · last asked Oct 1 · Concept · Mid-level
Show answer
A test plan describes what will be tested, how, by whom, and when for a project or release. A test strategy sets the high-level testing approach and principles. The plan applies that approach to specific work; the strategy may guide several projects or be part of the plan.
- A plan includes scope, objectives, people, schedule, test environments, risks, and criteria for starting and finishing testing.
- A strategy defines test levels, test types, techniques, and priorities based on risk.
- The document names and structure can vary between teams.
What the interviewer checks: The interviewer checks whether you can separate the overall testing approach from the details needed to organize testing.
Other ways it was asked
- “What is the difference between a test plan and a test strategy?”
- “What are a test plan and a test strategy?”
- “What’s the difference between a test plan and a test strategy?”
How do you write an actionable bug report and communicate it to engineering?
Asked in 5 of 245 interviews · last asked Oct 12 · Concept · Junior
Show answer
I write a bug report with a clear title, environment and build, setup, exact steps, and expected versus actual results. I include impact, severity, how often it happens, and useful screenshots or logs. I send it to the responsible engineering team, flag urgent issues, and answer questions to help reproduce it.
- Include test data and setup so another person can repeat the steps.
- Describe expected and actual results clearly; attach evidence without exposing passwords or personal data.
- Severity describes impact; agree on priority with the team based on urgency.
- Check for duplicates, track the report, and retest the fix.
What the interviewer checks: The interviewer checks whether you provide enough detail to reproduce the bug and help engineering act on it.
Other ways it was asked
- “What information should a well-written defect report include?”
- “What makes a good bug report?”
- “What fields should a good defect report include to help reproduce and fix the issue?”
How do you use AI in testing, and where is human judgment still essential?
Asked in 5 of 245 interviews · last asked Oct 13 · Behavioral · Mid-level
Show answer
I use AI to suggest test cases, draft test data, and summarize logs or bug reports. I check its output against requirements and actual system behavior before using it. Human judgment is still essential for setting priorities, exploring unexpected behavior, judging usability, and deciding whether a risk is acceptable.
- Treat AI output as a draft, not proof that a feature works.
- Review suggested tests for missing cases, wrong assumptions, and relevance.
- Use approved tools and avoid sharing sensitive data without permission.
- People remain responsible for test decisions and risk acceptance.
What the interviewer checks: The interviewer wants to see practical uses of AI, clear limits, and human responsibility for testing decisions.
Other ways it was asked
- “How do you use AI in your daily work, especially for testing?”
- “How are you currently using AI tools in your testing work, or how might you use them in the future?”
- “How does AI fit into your QA workflow?”
How do unit, integration, and end-to-end tests differ, and when would you use each?
Asked in 4 of 245 interviews · last asked Oct 22 · Concept · Junior
Show answer
Unit tests check one small piece of code in isolation; use them to check logic quickly. Integration tests check whether parts work together; use them to find problems between components. End-to-end tests check a complete user flow through the system; use them for important tasks such as signing in or buying an item.
- Unit tests are usually fast and help locate bugs precisely.
- Integration tests check connections, such as an application reading from a database.
- End-to-end tests cover full workflows but are usually slower and harder to maintain.
- Use many focused tests and fewer end-to-end tests for critical user flows.
What the interviewer checks: The interviewer checks whether you understand each test level and can choose the right scope and cost.
Other ways it was asked
- “What is the difference between an integration test and an end-to-end test?”
- “What is the difference between end-to-end tests and integration tests?”
- “What are end-to-end tests, and when should you use them?”
What is the difference between smoke, sanity, and regression testing?
Asked in 4 of 245 interviews · last asked Oct 24 · Concept · Junior
Show answer
Smoke testing checks the main features to see if a build is ready for deeper testing. Sanity testing usually checks a specific change and closely related features. Regression testing checks that changes have not broken existing features. Teams may use these terms differently, especially sanity testing.
- Smoke testing is broad but shallow and helps reject unstable builds early.
- Sanity testing is narrow and focused, often after a small change or fix.
- Regression testing covers areas at risk from changes; it does not always mean retesting everything.
- These tests can overlap and can be manual or automated.
CodeAfter a change to checkout: Smoke: Check login, product search, and a basic purchase. Sanity: Check the changed checkout step and related behavior. Regression: Check existing discounts, payments, and order history.What the interviewer checks: The interviewer is checking whether you understand each test's purpose, scope, and when to use it.
Other ways it was asked
- “What’s the difference between smoke testing and sanity testing?”
- “What is the difference between smoke testing and sanity testing?”
- “What is the difference between regression testing and sanity testing?”
Can you explain the software testing life cycle and how test cases fit into it?
Asked in 4 of 245 interviews · last asked Sep 17 · Concept · Junior
Show answer
The software testing life cycle (STLC) is the process used to plan, prepare, run, and complete testing. Its main phases are requirement analysis, test planning, test case design, environment setup, test execution, and test closure. Test cases link requirements to steps and expected results; we run them, compare actual results, and report defects.
- During test design, prepare test cases and test data, and review requirement coverage.
- During execution, record pass or fail results, report defects, retest fixes, and run regression tests.
- At closure, summarize results, unresolved defects, and lessons learned.
- Phases can overlap or repeat, and test cases change when requirements change.
What the interviewer checks: The interviewer checks whether you understand the testing process and how test cases support requirement coverage and execution.
Other ways it was asked
- “What is STLC, and what are its different phases?”
- “What is STLC?”
- “What is the STLC process?”
What is the difference between functional and non-functional testing?
Asked in 4 of 245 interviews · last asked Sep 24 · Concept · Junior
Show answer
Functional testing checks what the system does, such as whether login works correctly. Non-functional testing checks how well the system works, such as its speed, reliability, and ease of use. Both are needed because a feature can work correctly but still be slow or hard to use.
- Functional requirements describe features and expected results; non-functional requirements describe quality goals and limits.
- Functional tests compare actual results with expected behavior.
- Non-functional tests assess qualities such as performance, usability, and reliability against defined criteria.
- Both types can be tested manually, but some checks need tools, such as load testing.
What the interviewer checks: The interviewer checks whether you can separate correct behavior from quality expectations and explain why both matter.
Other ways it was asked
- “What are functional and nonfunctional tests, and how do they differ?”
- “What is the difference between functional and non-functional requirements?”
- “What are the fundamental differences between functional and nonfunctional testing, and why do those distinctions matter in QA?”
What is software testing?
Asked in 4 of 245 interviews · last asked Oct 1 · Concept · Junior
Show answer
Software testing means checking software to find defects and see whether it meets requirements and user needs. It helps assess quality and reduce the risk of failures. The process includes reviewing requirements, planning tests, running them, comparing actual and expected results, and reporting defects.
- Testing checks both stated requirements and real user needs.
- Testing includes reviews without running software, as well as tests that run it.
- Testing can find defects, but it cannot prove that no defects remain.
- After fixes, testers check the fix and test for unintended effects.
What the interviewer checks: The interviewer is checking whether you understand the purpose, basic activities, and limits of software testing.
Other ways it was asked
- “What is testing in software engineering?”
- “What is software testing, and what does the testing process involve?”
- “What is the actual definition and purpose of software testing?”
Which testing strategies would you use for a software project?
Asked in 4 of 245 interviews · last asked Sep 30 · Scenario · Junior
Show answer
I would use a risk-based testing strategy, based on the requirements, users, and project limits. I would test the most critical features first, using functional, integration, system, and acceptance testing as needed. I would also plan relevant non-functional checks, explore unexpected behavior, retest fixes, and run regression tests.
- Agree on scope, priorities, test data, environments, and completion criteria.
- Cover expected behavior, invalid inputs, and boundary values.
- Choose performance, security, usability, and compatibility checks based on project risks.
- Track defects and results; automate stable, repeated checks where useful.
What the interviewer checks: The interviewer checks whether you can build a practical test plan around project risks rather than list testing types.
Other ways it was asked
- “How do you plan testing for a new software project?”
- “What software testing process would you follow on a project?”
- “How do you test a software product, and what testing strategy do you use?”
Can you explain boundary value analysis with a suitable example?
Asked in 4 of 245 interviews · last asked Oct 24 · Concept · Junior
Show answer
Boundary value analysis is a test design technique that checks values at and just next to the limits of an input range. Errors often occur where accepted values change to rejected values. For a whole-number age field that accepts 18 to 60 inclusive, I would test 17, 18, 19, 59, 60, and 61.
- Test both the lower and upper limits.
- Check values just below, at, and just above each limit.
- Equivalence partitioning groups inputs with similar expected behavior; boundary value analysis focuses on their edges.
CodeRule: Accept whole-number ages from 18 to 60 inclusive. 17: Reject 18, 19: Accept 59, 60: Accept 61: Reject Equivalence partitions: below 18, 18–60, above 60.What the interviewer checks: The interviewer checks whether you can identify boundaries, choose nearby test values, and state the expected results.
Other ways it was asked
- “What is boundary value analysis?”
- “Can you explain boundary value analysis?”
- “Can you give me an example of boundary value analysis and equivalence partitioning?”
What is exploratory testing, and what guides it?
Asked in 4 of 245 interviews · last asked Oct 13 · Concept · Junior
Show answer
Exploratory testing means learning about the software, designing tests, and running them at the same time. It is guided by test goals, product risks, tester experience, and what each test reveals. It is flexible, but not random, and helps find problems that scripted tests may miss.
- Learning and test results guide what to test next.
- A test charter can define the goal and scope of a session.
- Testers record what they tested, what they found, and questions to follow up.
- It complements scripted testing, especially for new or changed features.
What the interviewer checks: The interviewer checks whether you understand that exploratory testing is guided investigation, not random clicking.
Other ways it was asked
- “What is exploratory testing?”
- “What does the term exploratory testing mean?”
- “What is exploratory testing, and when would you use it?”
What is a test case?
Asked in 4 of 245 interviews · last asked Oct 1 · Concept · Junior
Show answer
A test case is a set of conditions, inputs, steps, and expected results used to check a specific behavior of software. It usually includes an ID, a title, preconditions, test data, steps, and expected results. After running it, the tester records the actual result and whether it passed or failed.
- Preconditions describe what must be ready before the test starts.
- Steps and test data should be clear enough for another tester to follow.
- Expected results define the correct behavior.
- Compare actual results with expected results to decide whether the test passes or fails.
What the interviewer checks: The interviewer checks whether you understand how to define a clear, repeatable test with a measurable result.
Other ways it was asked
- “Can you define a test case?”
- “What is a test case, and what are its key components?”
How do severity and priority differ, and can you give an example?
Asked in 4 of 245 interviews · last asked Oct 12 · Concept · Junior
Show answer
Severity is how badly a bug affects the software or users. Priority is how urgently it needs fixing. For example, a crash in a rarely used game mode may have high severity but low priority, while a spelling error on the launch screen may have low severity but high priority before release.
- Severity measures impact, such as crashes, data loss, or blocked tasks.
- Priority reflects urgency, business needs, deadlines, and how many users are affected.
- A severe bug is not always the first bug to fix.
What the interviewer checks: The interviewer checks whether you can separate a bug’s impact from the urgency of fixing it.
Other ways it was asked
- “What is the difference between severity and priority?”
- “What is the difference between severity and priority in software testing?”
- “Can you give an example of how severity and priority can differ for a bug in a game?”
What is the testing pyramid?
Asked in 4 of 245 interviews · last asked Oct 8 · Concept · Junior
Show answer
The testing pyramid is a guide for balancing automated tests. It suggests many unit tests at the base, fewer integration tests in the middle, and a small number of end-to-end tests at the top. API tests often sit in the middle. This balance gives fast feedback while limiting slow, costly tests.
- Unit tests check small pieces of code in isolation.
- Integration tests check that parts work together; API tests often fit here.
- End-to-end tests check complete user flows, often through the user interface.
- The pyramid is a guide, not a fixed ratio; API tests can also be end-to-end.
What the interviewer checks: The interviewer checks whether you can balance test coverage, speed, and maintenance cost.
Other ways it was asked
- “What is the testing pyramid, and what levels does it typically include?”
- “What is the test pyramid, and how does it guide the balance of different types of tests?”
- “What is the testing pyramid and how does API testing fit into it?”
How would you define or refine QA standards or acceptance criteria for a data project, and how would you justify changes?
Asked in 3 of 245 interviews · last asked Oct 15 · Behavioral · Mid-level
Show answer
I would agree on clear, measurable data quality rules with business users and the data team. These would cover accuracy, completeness, freshness, and valid values. I would justify changes using defects, business impact, and test results, then get approval and update the tests. I would track whether related defects decreased without causing unnecessary failures.
- Base acceptance criteria on business needs, source data, and agreed update times.
- Set clear pass or fail rules, including how to handle missing or late data.
- Use defect evidence and business risk to justify stricter or more flexible rules.
- Compare quality before and after the change, and document approval.
CodeExample proposal: A dashboard passes even when a region's data is missing. Change: Require every expected region before the daily release. Agree with business users how to handle late regional data. Justification: Missing regions make sales totals misleading. Measure: Track missing-region incidents and unnecessary release blocks.What the interviewer checks: The interviewer is checking whether you can turn business needs into testable rules and justify changes with evidence.
Other ways it was asked
- “Have you ever defined or refined QA standards or acceptance criteria for a data project? What did you change and why?”
- “Describe a time you refined QA standards or acceptance criteria for a data project. What specific change did you make, and how did you measure that it improved quality?”
- “Have you ever defined or refined QA standards or acceptance criteria for a data pipeline or dashboard? What did you change and why?”
Software testing basics interview questions
Questions cover testing terms, principles, types, levels, verification and validation, software reviews, and development life cycles. 62 questions.
Why do you think software testing is important?
Asked in 2 of 245 interviews · last asked Jul 22 · Concept · Junior
Other ways it was asked
- “What is software testing and why is it important?”
What is the shift-left testing approach?
Asked in 2 of 245 interviews · last asked Aug 4 · Concept · Mid-level
Other ways it was asked
- “What is shift-left testing, and when would you use it?”
What are the fundamentals of software testing?
Asked in 2 of 245 interviews · last asked Oct 17 · Concept · Junior
Other ways it was asked
- “What are the principles of software testing?”
What is the difference between positive and negative testing?
Asked in 2 of 245 interviews · last asked Oct 3 · Concept · Junior
What are the types of validation?
Asked in 2 of 245 interviews · last asked Mar 26 · Concept · Junior
Other ways it was asked
- “What are the types of software validation?”
What does quality mean to you in a digital product?
Asked once · last asked Feb 9 · Concept
What is the difference between statement coverage and branch coverage?
Asked once · last asked Apr 10 · Concept · Mid-level
What are test-first development, TDD, and ATDD, and when would you use each?
Asked once · last asked May 21 · Concept · Mid-level
What does BDD stand for, what tool is it associated with, and when and why would you use this approach?
Asked once · last asked May 28 · Concept · Mid-level
Other ways it was asked
- “What does BDD stand for, what tool is it associated with, and when would you use it? What are its benefits?”
How does your testing approach differ across frontend, middleware, and backend applications?
Asked once · last asked Jun 26 · Concept · Mid-level
What type of testing examines a product from the outside without knowledge of its internal design?
Asked once · last asked Jul 16 · Concept · Junior
Why might a team prioritize smoke and sanity testing over other types of testing for an application?
Asked once · last asked Jul 16 · Scenario · Mid-level
Test planning and QA process interview questions
Explore requirements, acceptance criteria, test plans and strategies, QA responsibilities, teamwork, and setting up testing from scratch. 70 questions.
How do you approach test planning?
Asked in 2 of 245 interviews · last asked May 5 · Concept · Mid-level
Other ways it was asked
- “What do you include in test planning?”
What is the role of a QA in the requirement analysis phase?
Asked once · last asked Oct 1 · Concept · Junior
Other ways it was asked
- “What kind of documentation does a QA prepare during the requirement analysis phase?”
How do you manage the QA process from requirements analysis through test automation and sign-off?
Asked once · last asked Jan 27 · Scenario · Mid-level
How would you analyze and test a new build delivered every two or three weeks during a sprint?
Asked once · last asked Mar 17 · Scenario · Mid-level
In a perfect team, what should QA’s function be as part of the development team, what areas of expertise should QA have, and what should their day-to-day work look like?
Asked once · last asked Mar 19 · Concept
How would you integrate QA into a team's workflow from feature definition through release, including the key steps and when and how QA should get involved?
Asked once · last asked Apr 1 · Concept · Mid-level
Other ways it was asked
- “Can you walk us through how QA works in your team, from feature definition through release, including the key steps and when and how you get involved?”
Tell me about a time you had to test with incomplete requirements or documentation. How did you handle it?
Asked once · last asked Apr 20 · Behavioral · Mid-level
How would you learn Salesforce, coordinate with an architect, and take over another tester’s responsibilities while defining an automation strategy, estimating effort, prioritizing test cases, and accelerating test preparation?
Asked once · last asked Apr 20 · Scenario · Senior
Other ways it was asked
- “How would you ramp up on Salesforce and plan an automation testing approach, effort estimates, and priority test cases while taking over some of another tester's responsibilities? How would you coordinate with an architect and accelerate test preparation?”
How would you gather and work through requirements for a software testing project, and what deliverables would you provide to the client?
Asked once · last asked May 5 · Behavioral · Mid-level
Other ways it was asked
- “How did you gather and work through requirements for a software testing project, and what deliverables did you provide to the client?”
How do you test an application end to end, from gathering requirements and preparing test cases through execution and communicating results?
Asked once · last asked May 5 · Behavioral · Mid-level
What practices do you use to maintain quality on a large-scale project?
Asked once · last asked May 26 · Scenario · Senior
What do you need to develop tests for a hardware device, rather than just execute them?
Asked once · last asked Jul 16 · Scenario · Mid-level
Test case design and exploratory testing interview questions
Work through test cases, boundary values, equivalence partitioning, exploratory testing, and choosing tests by risk. 49 questions.
What are test design techniques?
Asked in 3 of 245 interviews · last asked Oct 24 · Concept · Junior
Other ways it was asked
- “Which test design techniques have you applied in practice?”
- “What test design techniques do you know?”
Write five test cases for a function that returns the second-largest element of an integer array.
Asked once · last asked Jun 26 · Scenario · Junior
Other ways it was asked
- “How would you execute test cases for a function that returns the second-largest element of an integer array?”
How do you decide what not to test when time is limited?
Asked once · last asked Feb 9 · Scenario · Mid-level
When time is limited and automation is difficult, what testing would you prioritize?
Asked once · last asked Feb 9 · Scenario · Mid-level
What is your usual workflow for creating test cases, including what information you receive and what you deliver?
Asked once · last asked Feb 9 · Scenario · Mid-level
What is the difference between a test plan, a test scenario, and a test case, and when would you use each?
Asked once · last asked Mar 16 · Concept · Junior
Given the many combinations of user roles, locales, currencies, time zones, feature flags, and configuration options, how would you prioritize testing when it’s impossible to cover every combination?
Asked once · last asked Apr 1 · Scenario · Senior
Would you use internal analytics, such as Mixpanel or Google Analytics, to help decide which configurations to test?
Asked once · last asked Apr 1 · Scenario · Senior
How would you break down the test cases to cover potential edge cases and give users clear guidance when data is missing or malformed?
Asked once · last asked Apr 1 · Scenario · Senior
What is a test oracle used for?
Asked once · last asked Apr 10 · Concept · Mid-level
Can you list some black-box testing techniques?
Asked once · last asked Apr 30 · Concept · Junior
For an age field that accepts values from 18 to 45, what is the optimized set of boundary-value-analysis test cases?
Asked once · last asked Apr 30 · Scenario · Junior
Bug reporting and defect management interview questions
Review how you report, reproduce, investigate, prioritize, and escalate bugs, then verify fixes and examine root causes. 68 questions.
How do you distinguish product bugs from expected behavior, and what evidence do you gather before escalating?
Asked in 2 of 245 interviews · last asked Aug 29 · Scenario · Mid-level
Other ways it was asked
- “A customer reports unexpected behavior in a software application and believes they have found a bug. What evidence would you gather before treating it as a product defect or escalating it to the product team?”
- “When handling a customer issue, how do you distinguish a policy constraint from a product bug, and what evidence do you capture before escalating?”
How do you prioritize defects and testing activities?
Asked in 2 of 245 interviews · last asked Oct 17 · Scenario · Mid-level
Other ways it was asked
- “How do you prioritize software defects?”
How are severity levels used to classify software defects?
Asked in 2 of 245 interviews · last asked Oct 17 · Concept · Junior
Other ways it was asked
- “How many severity levels are used to classify defects?”
How would you investigate why a LoRa join issue was not caught during pre-release testing?
Asked once · last asked Sep 3 · Scenario · Senior
Other ways it was asked
- “How would you investigate why a LoRa join issue was not caught during early development?”
How would you investigate, document, and attempt to reproduce an intermittent bug that is difficult to reproduce?
Asked once · last asked Apr 1 · Scenario · Senior
Other ways it was asked
- “If a bug occurs only occasionally and is difficult to reproduce, what would you do? Would you log it and try to reproduce it, and what would your approach be?”
What is the difference between Fixed Version and Affected Version in Jira?
Asked once · last asked Apr 10 · Tooling · Mid-level
A client emails you more than 100 bugs during project testing, each with reasonably complete descriptions. How would you handle the situation?
Asked once · last asked Apr 13 · Scenario · Senior
A login button takes users to an unexpected landing page. How would you determine whether the issue is in the front end or back end, and how would you handle it?
Asked once · last asked Apr 30 · Scenario · Mid-level
How would you identify a recurring defect pattern using ServiceNow and address its underlying cause?
Asked once · last asked May 25 · Behavioral · Mid-level
Other ways it was asked
- “Tell me about a time you identified a recurring defect pattern in ServiceNow and fixed it.”
How would you investigate recurring defects when the available data is incomplete?
Asked once · last asked May 25 · Scenario · Mid-level
When you're confronted with a potential bug that could impact user experience, what factors do you weigh before deciding on the best course of action?
Asked once · last asked Jun 8 · Scenario · Mid-level
What is the difference between a bug and an incident?
Asked once · last asked Jun 17 · Concept · Junior
Manual testing scenarios interview questions
Apply testing ideas to web, mobile, games, and hardware, including usability, compatibility, performance, security, accessibility, and localization. 53 questions.
How would you test an application's performance and a web page's accessibility?
Asked in 2 of 245 interviews · last asked Apr 16 · Scenario · Mid-level
Other ways it was asked
- “How would you test an application for WCAG accessibility?”
How do you perform compatibility testing, including checks across browsers?
Asked once · last asked Jul 16 · Scenario · Mid-level
Other ways it was asked
- “What aspects of browser compatibility would you test?”
- “Which browsers would you include in a browser compatibility test?”
- “How do you perform compatibility testing?”
Could you discuss how you handle quality verification when implementing a fraud detection system?
Asked once · last asked Feb 1 · Scenario · Mid-level
When testing a web application, what would you validate first, which browser and device would you start with, and what tools would you use for nonfunctional testing?
Asked once · last asked Feb 9 · Scenario · Mid-level
If I share a web app with you, how would you test it, what methods would you use, and how would you approach the testing process?
Asked once · last asked Mar 17 · Scenario · Mid-level
Once you receive application source files, how do you validate them, and what do you include on your validation checklist?
Asked once · last asked Mar 26 · Tooling · Mid-level
Besides the version, registry entries, and services, what else would you validate when testing an application package?
Asked once · last asked Mar 26 · Tooling · Mid-level
What file-level edge cases and security risks would you test for uploads?
Asked once · last asked Apr 1 · Scenario · Mid-level
Other ways it was asked
- “What could go wrong at the file level—for example, if someone uploads an image, a PDF, another unsupported file type, or a blank file?”
- “What file-level edge cases and security considerations would you test to ensure the system handles invalid or malicious files safely and provides meaningful errors?”
How would you test an end-to-end flight-booking flow, from the user's journey through booking confirmation?
Asked once · last asked Apr 1 · Scenario
Other ways it was asked
- “Which checkpoints would you test in an end-to-end flight-booking flow?”
What are the possible edge cases in an order-placement flow?
Asked once · last asked Apr 10 · Scenario · Junior
How would you test an end-to-end flow from a web portal through to an app?
Asked once · last asked Apr 13 · Scenario · Mid-level
How would you check the package source and verify the source files?
Asked once · last asked Apr 21 · Tooling · Mid-level
Backend and data testing interview questions
These questions cover APIs, databases, data pipelines, integrations, migrations, reporting accuracy, test data, permissions, and systems where work finishes later. 57 questions.
How would you create test data for a financial system with complex business requirements?
Asked once · last asked Jun 17 · Scenario · Mid-level
Other ways it was asked
- “What approaches do you use to create test data for complex financial business requirements?”
What approaches do you use to test backend systems, including APIs and Kafka?
Asked once · last asked Jan 27 · Tooling · Mid-level
How do you distinguish functional tests from data-quality tests in a data pipeline?
Asked once · last asked Mar 3 · Concept · Mid-level
How would you verify that analytical values displayed on a dashboard are correct?
Asked once · last asked Apr 1 · Scenario · Mid-level
If the database provides last week’s and this week’s sales values through an API, but the percentage change is calculated on the front end, how would you define your testing strategy?
Asked once · last asked Apr 1 · Scenario · Senior
How would you test a feature that imports store performance data from uploaded CSV files into a database, covering expected behavior, happy paths, edge cases, errors, reliability, and security?
Asked once · last asked Apr 1 · Scenario · Senior
Other ways it was asked
- “How would you test a feature that imports store performance data from uploaded CSV files into the database, covering the happy path, edge cases, and errors? How would you ensure it works correctly, reliably, and securely, and what should the application’s behavior be?”
How would you plan tests for a Salesforce feature to verify its behavior across different roles, including external users and multiple internal user groups?
Asked once · last asked Apr 10 · Scenario · Senior
How would you prevent a test that creates 500 records for performance or limit testing from leaving those records in the environment?
Asked once · last asked Apr 10 · Scenario · Mid-level
How would you test Salesforce field-level permissions when denied access triggers an error that blocks the remaining test path, but the feature is a high-priority client deployment?
Asked once · last asked Apr 13 · Scenario · Senior
How would you test a system that uses eventual consistency?
Asked once · last asked Apr 17 · Scenario · Senior
How would you test a system that uses polling?
Asked once · last asked Apr 17 · Scenario · Mid-level
In an early sprint, should a tester validate a data model's fields and allowed values, or focus on business values and end-to-end process behavior?
Asked once · last asked Apr 20 · Scenario · Mid-level
Test metrics and release readiness interview questions
Topics include quality measures, test reports, user acceptance testing, release sign-off, production checks, incident response, and process improvements. 40 questions.
How do you decide whether to block a release or ship with known issues under pressure?
Asked in 3 of 245 interviews · last asked Oct 15 · Scenario · Senior
Other ways it was asked
- “What would you do if a release did not meet the required quality level but leadership pressured you to launch it quickly?”
- “Would you release an assessed software deliverable as-is if you had already identified issues that needed fixing?”
- “How do you decide whether to block the release versus allow a conditional release with a known issue logged?”
What would you include in a test results report?
Asked in 2 of 245 interviews · last asked Oct 5 · Scenario · Mid-level
Other ways it was asked
- “After a full day of testing, what specific fields would you include in your final report?”
- “After a full day of testing, what fields would you include in your final report so another engineer could reproduce your runs and verify your conclusions?”
- “How would you structure a report summarizing test results?”
What does test coverage tell you, and why doesn't high coverage guarantee all relevant behavior is tested?
Asked in 2 of 245 interviews · last asked Aug 25 · Concept · Mid-level
Other ways it was asked
- “What is code coverage, and why is 100% coverage not always necessary?”
- “Does high test coverage guarantee that all relevant behavior has been tested?”
How do you measure the quality of your testing process?
Asked once · last asked Jul 27 · Scenario · Senior
Other ways it was asked
- “Which metrics do you use to measure the quality of your testing process?”
How would you calculate a 25% improvement in detecting critical defects?
Asked once · last asked Sep 23 · Scenario · Mid-level
Other ways it was asked
- “What evidence would you use to verify that the detection of critical defects improved by 25%?”
Tell me about a time a bug reached production before it was detected. What happened, and what did you learn?
Asked once · last asked Feb 9 · Behavioral
What quality-assurance process or checklist would you use to determine whether a website is ready for release?
Asked once · last asked Mar 20 · Mid-level
Other ways it was asked
- “How do you know when website development is ready? Do you use a quality-assurance process or checklist?”
When preparing a release, do you select specific tests or use a separate smoke test suite to quickly check the application?
Asked once · last asked Apr 16 · Scenario · Mid-level
What would you include in a release-readiness checklist to make sure everything is ready?
Asked once · last asked Apr 17 · Scenario · Mid-level
If a production migration fails and the database goes down, what should the team do, and what is your role as QA?
Asked once · last asked Apr 17 · Scenario · Senior
A critical defect affecting core functionality is found two days before release. How would you assess and handle it?
Asked once · last asked May 5 · Scenario · Senior
What governance processes do you use? Do you conduct code reviews and quality checks, and what are your quality gates?
Asked once · last asked May 5 · Scenario · Senior
Test automation and CI/CD interview questions
Consider automation choices, frameworks, coverage, CI/CD stages, environments, test stability, maintenance, infrastructure costs, and results. 64 questions.
How do you keep automated tests reliable and useful when features, experiments, or feature flags change frequently?
Asked in 2 of 245 interviews · last asked Sep 24 · Scenario · Senior
Other ways it was asked
- “How would you use test automation to keep baseline tests reliable when experiments or feature-flag changes alter the application?”
- “How do you handle situations where automated tests might not provide clear feedback because features are changing often?”
How would you structure a test automation framework, and what changes are needed when transitioning it to AI-based testing?
Asked once · last asked Jul 30 · Design · Senior
Other ways it was asked
- “How would you structure a test automation framework, including its folder structure, and what changes are needed when transitioning it to AI-based testing?”
What are the key components of an automation framework?
Asked once · last asked Sep 11 · Concept · Mid-level
How would you define success metrics for a test automation project?
Asked once · last asked Sep 22 · Scenario · Mid-level
Other ways it was asked
- “How would you define the success of an automation project?”
What business outcome does faster regression testing create?
Asked once · last asked Sep 22 · Scenario · Mid-level
Other ways it was asked
- “What business outcome does faster regression testing translate to?”
How would you design a reliable, high-signal testing framework for a system affected by timing, concurrency, nondeterminism, or external dependencies?
Asked once · last asked Oct 22 · Scenario · Senior
When should you perform a system refresh for a QA environment?
Asked once · last asked Mar 9 · Concept · Mid-level
How do you manage end-to-end testing when an application consists of many services that must be started or kept running?
Asked once · last asked Mar 19 · Scenario · Senior
How do you integrate testing into a CI/CD process, which tools do you use, and how does the process work?
Asked once · last asked Apr 10 · Tooling · Mid-level
How would you approach designing an automated testing strategy, and what factors would you consider?
Asked once · last asked Apr 16 · Behavioral · Senior
Other ways it was asked
- “What was your role in designing an automated testing strategy, how did you approach it, and what did you consider?”
Which metrics are most important for evaluating a test automation suite, and which would you track?
Asked once · last asked Apr 16 · Concept · Mid-level
Other ways it was asked
- “Which metrics are most important for evaluating a test automation suite, and which do you track?”
How would you automate a large workflow involving filling out a form and retrieving information from an email? Would you write one large test or split it into smaller tests?
Asked once · last asked Apr 16 · Scenario · Senior
AI testing interview questions
Explore AI-assisted QA, chatbot and agent testing, varying outputs, safety limits, privacy, evaluation data, quality criteria, and feedback from production. 31 questions.
How would you test an LLM output when the acceptance criteria and expected behavior are known?
Asked once · last asked Jul 30 · Scenario · Mid-level
How would you use an LLM to turn Jira requirements into test cases, and how would you choose between a local model and an online model?
Asked once · last asked Apr 23 · Tooling · Mid-level
What would you include in a data science QA tracker to monitor the quality of outputs?
Asked once · last asked Jun 15 · Scenario · Mid-level
How would you build a test suite for a chatbot that answers questions about a company's product?
Asked once · last asked Jul 16 · Scenario · Mid-level
How will you test that a multi-tenant AI CRM never leaks contact data between agency clients?
Asked once · last asked Jul 16 · Scenario · Senior
How would you build a QA dashboard for tracking AI product quality over time?
Asked once · last asked Jul 16 · Design · Senior
What is a feedback loop in an AI product, and how can production feedback be used to improve test cases?
Asked once · last asked Jul 16 · Concept · Mid-level
How would you reduce production defects as a sole tester, and where could AI help?
Asked once · last asked Jul 16 · Scenario · Senior
What constraints should you account for when testing an AI agent?
Asked once · last asked Jul 30 · Scenario · Senior
How would you test an AI chatbot using TestNG and TestRail?
Asked once · last asked Jul 30 · Tooling · Mid-level
How would you use AI coding tools and manual QA during a software migration?
Asked once · last asked Jul 31 · Scenario · Senior
What should the software testing life cycle for agentic AI systems look like, especially in regulated insurance environments?
Asked once · last asked Aug 19 · Scenario · Senior
Show 18 more
What do you see as the key differences between testing an AI-enabled application versus a traditional application that isn't leveraging AI?
Asked once · last asked Sep 10 · Concept · Senior
How can AI be integrated into software testing or validation?
Asked once · last asked Sep 10 · Scenario · Mid-level
How would you validate a real estate chatbot before and after launch?
Asked once · last asked Sep 21 · Behavioral · Mid-level
Other ways it was asked
- “How did you validate a real estate chatbot before and after launch?”
What is your process for using AI to create test reports or summaries?
Asked once · last asked Sep 23 · Tooling · Mid-level
How do you measure the time saved by using AI for test reporting, and how do you verify its results?
Asked once · last asked Sep 23 · Scenario · Mid-level
How would you structure the test matrix across agents, versions, settings, and seeds to make comparisons fair and reproducible?
Asked once · last asked Oct 5 · Scenario · Senior
If the same prompt produces different failures across five runs, how would you document those failures and assess the agent's reliability?
Asked once · last asked Oct 5 · Scenario · Senior
How would you use Zephyr to estimate the effort required to automate tests with AI?
Asked once · last asked Oct 8 · Tooling · Senior
What concrete failures would you look for when using LLMs to generate test ideas?
Asked once · last asked Oct 9 · Behavioral · Senior
Other ways it was asked
- “When you tried using LLMs to generate test ideas, what concrete failures did you see most?”
How would you design the CI gate to distinguish an invalid LLM-generated test sequence from a genuine game bug, and how would you classify and triage failures?
Asked once · last asked Oct 9 · Design · Senior
Would you use a fixed test suite or create new tests each time to check whether an AI agent's guardrails trigger correctly?
Asked once · last asked Oct 13 · Scenario · Senior
How would you identify gaps in an AI-generated quality control plan for a financial trading platform and account for real-time market volatility's impact on trade settlement accuracy?
Asked once · last asked Oct 14 · Scenario · Senior
How would you test an AI chatbot and build an evaluation dataset for it?
Asked once · last asked Oct 22 · Scenario · Senior
What are the three most common failure points in a chatbot that answers product questions?
Asked once · last asked Jul 16 · Concept · Mid-level
How would you test an AI chatbot, and what tools could you use?
Asked once · last asked Jul 30 · Tooling · Mid-level
Should test-case creation be included in the technical specification for an AI agent?
Asked once · last asked Aug 7 · Concept · Mid-level
What does exploratory testing of AI inference workloads on Kubernetes involve?
Asked once · last asked Sep 24 · Tooling · Mid-level
What reasons might lead a client to test AI use cases themselves?
Asked once · last asked Oct 22 · Scenario · Mid-level
Related interview questions
- QA Engineer interview questions
- Software Engineer interview questions
- AI Trainer interview questions
- AI Engineer interview questions
- Data Engineer interview questions
- IT Support and Help Desk interview questions
- Automation Testing interview questions
- API Testing interview questions
- Agile and Scrum interview questions
- Salesforce interview questions
How this list is made
Every question here was asked by a real interviewer in a real job interview that a candidate ran MeetAssist in. After the call, the interviewer's questions are pulled from the transcript. Practice sessions, tests, exams and anything that was not a job interview are dropped.
Questions are rewritten so they make sense on their own: names of people, employers and clients are removed, and speech-to-text mistakes are fixed. Small talk, logistics and questions about one candidate's own résumé are left out. Rephrasings of the same question are merged, and the count is the number of different interviews it came up in.
The interviews come from candidates who use MeetAssist, so they lean towards software, data and AI roles: the shares describe these interviews, not every Manual Testing interview. Answers to the most asked questions are written and checked by an editor; a "common mistake" is shown only when reviews of real answers in these interviews show it, with the count.
245 interviews, 143 candidates, Jan 2026 to Oct 2026. Updated every month with new interviews.
Or add the Chrome extension