All 54 questions

  1. How do you decide which tests to automate and which to keep manual?

    Asked in 11 of 145 interviews · last asked Nov 6 · Concept · Senior

    Show answer

    I automate tests that run often, cover important risks, and have clear expected results. I compare the time saved and faster feedback with the cost of building and maintaining them. I keep exploratory, usability, and rarely repeated checks manual when automation adds little value. I retire or rework automated tests when their upkeep outweighs their value.

    • Prioritize repeatable regression checks for critical features.
    • Choose tests with reliable setup, controlled data, and clear pass or fail results.
    • Use manual testing where human judgment matters or requirements change often.
    • Review slow, flaky, or duplicate tests; fix useful coverage rather than simply removing it.

    What the interviewer checks: The interviewer wants to see whether you balance risk, repeatability, human judgment, and maintenance cost.

    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?”
  2. How would you estimate the effort and time needed to automate a set of test scenarios?

    Asked in 3 of 145 interviews · last asked Oct 8 · Scenario · Senior

    Show answer

    I group scenarios by complexity and estimate the work for each group. I automate a small sample to check those estimates, including test data, setup, coding, debugging, and review. I account for reusable framework features, dependencies, and team availability, then give a time range with clear assumptions and a buffer for unknowns.

    • Check which scenarios are suitable for automation before estimating.
    • Include framework changes, test data, environment setup, and CI integration where needed.
    • Use sample results or past work, not one fixed time per scenario.
    • Separate total work hours from calendar time; waiting and parallel work affect delivery.

    What the interviewer checks: The interviewer checks whether you can build a realistic estimate rather than guess from the scenario count.

    Other ways it was asked
    • “How do you estimate the effort required to automate a user story?”
    • “How do you estimate the effort required to automate a given user story?”
    • “How do you estimate automation effort for a user story in an Agile sprint?”
  3. How will you decide which test cases are good candidates for automation?

    Asked in 3 of 145 interviews · last asked Nov 18 · Scenario · Mid-level

    Show answer

    I prioritize tests that run often, cover important features, and have clear expected results. I check whether they can run reliably with available tools, controlled test data, and a stable environment. I compare the time saved and risk covered with the effort to build and maintain them. I keep exploratory and subjective checks manual.

    • Start with high-value smoke and regression tests that run frequently.
    • Check tool support, test data, dependencies, and clear pass or fail results.
    • Balance build and maintenance costs against repeat runs and business risk.
    • Defer rarely used or rapidly changing tests unless their risk justifies automation.

    What the interviewer checks: The interviewer checks whether you can prioritize useful, reliable automation based on risk, feasibility, and return on effort.

    Other ways it was asked
    • “Given 600 manual test cases, how would you choose which ones to automate?”
    • “How do you decide which test cases to automate, considering feasibility and ROI?”
  4. How would you measure the quality of automation compared with manual testing?

    Asked in 2 of 145 interviews · last asked Oct 26 · Scenario · Mid-level

    Show answer

    I would compare automation and manual testing by useful defect detection, risk coverage, speed, and total effort. For automation, I would include setup, maintenance, and time spent checking false failures. Automation is usually better for repeated checks, while manual testing is better for exploration and judging usability.

    • Compare the same scope and risk level, not just test counts.
    • Track missed defects, defect severity, and coverage of important user flows.
    • Measure feedback time and total effort across repeated test runs.
    • Track flaky tests because unreliable results reduce trust and waste time.

    What the interviewer checks: The interviewer wants to see whether you balance speed and cost with reliable results and defect detection.

    Other ways it was asked
    • “How would you compare the efficiency of an automated testing approach with manual testing?”
  5. What is the testing pyramid?

    Asked in 2 of 145 interviews · last asked Oct 8 · Concept · Junior

    Show answer

    The testing pyramid is a guide for balancing automated tests. It typically has many unit tests at the base, fewer integration tests in the middle, and very few end-to-end tests at the top. This balance gives fast feedback while keeping test costs and maintenance lower.

    • Unit tests check small pieces of code in isolation and usually run quickly.
    • Integration tests check whether components work together.
    • End-to-end tests check complete user flows but are usually slower and harder to maintain.
    • The pyramid is a guide, not a fixed ratio of tests.

    What the interviewer checks: The interviewer is checking whether you can balance test coverage, speed, and maintenance across test levels.

    Other ways it was asked
    • “What is the testing pyramid, and what levels does it typically include?”
  6. How would you measure the business impact of increasing test automation coverage by 60%?

    Asked once · last asked Aug 17 · Behavioral · Senior

  7. 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?”
  8. 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

  9. 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?”
  10. 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?”
  11. Which automated testing tools would you implement for UAT?

    Asked once · last asked Apr 18 · Tooling · Mid-level

  12. Can you give me an example of something you automated that helped the product?

    Asked once · last asked May 25 · Behavioral · Mid-level

  13. How would you automate or improve testing processes to increase stability and overall code quality?

    Asked once · last asked May 25 · Behavioral · Mid-level

    Other ways it was asked
    • “How have you automated or improved testing processes to increase stability and overall code quality?”
  14. How would you design a test automation strategy to maximize its value?

    Asked once · last asked Jul 21 · Design · Senior

  15. How do you calculate test automation coverage?

    Asked once · last asked Aug 5 · Concept · Mid-level

  16. How would you build an automation strategy for a large microservices-based application with UI, API, and backend layers?

    Asked once · last asked Aug 17 · Design · Senior

  17. How would you design a test strategy to automate cross-validation testing?

    Asked once · last asked Sep 4 · Scenario · Mid-level

  18. Tell me about a time you took ownership of a test automation framework, set its direction, and mentored the team.

    Asked once · last asked Sep 8 · Behavioral

  19. Tell me about a time you persuaded developers and business stakeholders to invest in test automation, using its impact on critical defects to make the case.

    Asked once · last asked Sep 8 · Behavioral · Senior

  20. How would you develop and organize automated tests for 100 test cases?

    Asked once · last asked Sep 18 · Scenario · Mid-level

  21. What major factors do you consider when evaluating trade-offs in an automation decision?

    Asked once · last asked Sep 22 · Scenario · Mid-level

  22. If you joined a team with no automated tests but already had documented scenarios, how would you approach test automation?

    Asked once · last asked Oct 8 · Scenario · Senior

  23. How do you approach manual testing before automating an application?

    Asked once · last asked Oct 12 · Scenario · Mid-level

  24. What automation tests have you written from scratch, and what was the hardest problem you faced?

    Asked once · last asked Oct 14 · Behavioral · Mid-level

  25. What should a client expect from you when you join a project to audit existing test automation?

    Asked once · last asked Oct 22 · Scenario · Senior

  26. What step-by-step test automation strategy would you use for a trading system when the QA team has limited knowledge of it?

    Asked once · last asked Nov 17 · Scenario · Senior

  27. Who should be responsible for reviewing nightly regression results and classifying failures as product bugs, test bugs, or environment issues?

    Asked once · last asked Oct 26 · Scenario · Senior

  28. When would you build a custom test automation solution instead of using existing tools, and how would you evaluate its advantages?

    Asked once · last asked Oct 26 · Scenario · Senior

  29. What is UI test automation, and which frameworks can be used to implement it?

    Asked once · last asked Oct 27 · Concept · Mid-level

  30. How do you approach regression, automated, and manual testing as a QA professional?

    Asked once · last asked Nov 3 · Scenario · Mid-level

  31. How would you automate a component or module of an application, such as its login functionality?

    Asked once · last asked Nov 6 · Scenario · Mid-level

  32. How do you decide what belongs in a JUnit or integration test versus an end-to-end Playwright test?

    Asked once · last asked Nov 6 · Concept · Senior

  33. Which tool is best from your perspective: Playwright, Testim, or Katalon?

    Asked once · last asked Nov 12 · Mid-level

  34. When would you use record-and-playback testing, and when would you write test scripts manually?

    Asked once · last asked Nov 12 · Concept · Mid-level

  35. How do you manage both manual and automation testing within your sprint process?

    Asked once · last asked Nov 12 · Scenario · Mid-level

  36. How do you identify which areas are suitable for automation testing?

    Asked once · last asked Nov 13 · Concept · Mid-level

  37. How would you calculate the speedup achieved through test automation?

    Asked once · last asked Nov 20 · Concept · Mid-level

  38. What business outcomes can result from time saved through test automation?

    Asked once · last asked Sep 22 · Scenario · Mid-level

    Other ways it was asked
    • “What business outcomes can result from reducing testing hours through automation?”
  39. Where does test automation fit into the QA process?

    Asked once · last asked Jan 27 · Concept · Mid-level

  40. What are the differences between manually performing an integration test and automating it?

    Asked once · last asked Apr 28 · Concept · Junior

  41. How many test cases would you estimate an intern can automate in a day: 10, 15, or 20?

    Asked once · last asked Apr 28 · Scenario

  42. What is a test script?

    Asked once · last asked May 8 · Concept · Junior

  43. How should automated testing and a dedicated QA team fit into a software development workflow?

    Asked once · last asked Jun 25 · Scenario · Mid-level

  44. Which test automation tools do you know?

    Asked once · last asked Jul 27 · Concept · Junior

  45. How do you approach testing and test automation on a project?

    Asked once · last asked Aug 5 · Scenario · Mid-level

  46. Do you know the difference between unit, integration, and end-to-end test cases?

    Asked once · last asked Sep 21 · Concept · Junior

  47. Why is it important to compare an automated test's output with the expected value?

    Asked once · last asked Sep 22 · Concept · Junior

  48. How can test automation improve testing productivity?

    Asked once · last asked Sep 22 · Concept · Junior

  49. Why would cost be a success metric for automation?

    Asked once · last asked Sep 22 · Concept · Junior

  50. What are software testing and test automation?

    Asked once · last asked Oct 22 · Concept · Junior

  51. How do you assess whether a test automation approach is working effectively for a team?

    Asked once · last asked Oct 26 · Scenario · Senior

  52. How would you break down a website or application and begin building its test automation?

    Asked once · last asked Nov 6 · Scenario · Mid-level

  53. What are the benefits of using automated tests?

    Asked once · last asked Nov 13 · Concept · Junior

  54. What types of functionality are suitable for automated testing?

    Asked once · last asked Nov 13 · Concept · Junior

More Automation Testing 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 Automation 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.

145 interviews, 79 candidates, Jan 2026 to Nov 2026. Updated every month with new interviews.