Automate what is repetitive, stable, and objectively verifiable, where the cost of the check recurs: regression paths, critical journeys, data driven permutations, and API contracts. Keep manual and exploratory testing for usability, visual judgment, one off validations, and anything still changing weekly, where the automation would be rewritten before it ever paid back its cost.
Why interviewers ask this
Automate everything is a red flag answer, because it signals someone who has never maintained a suite through a redesign. Interviewers want a cost benefit argument: how often the test runs, how stable the area is, and what maintenance will cost. Defending exploratory testing as a distinct activity that finds a different class of defect, rather than as leftovers, marks an experienced tester.
How to structure your answer
- Frame it as return on investment over the test's lifetime.
- Name the strong automation candidates.
- Name what stays manual and why.
- Warn against automating an unstable area too early.
- Defend exploratory testing as finding a different class of defect.
Example answer
I treat it as return on investment across the life of the test, not a philosophical position. The good candidates are checks that will run hundreds of times, in areas that are stable, with an unambiguous pass or fail: regression around core journeys, permutation heavy cases like tax rules across ten regions, and API contracts. Those pay back quickly and a human doing them is a waste of a human. What stays manual is anything requiring judgment. Does this layout look broken, is this error message actually understandable, does this flow make sense to someone seeing it for the first time. An automated test will happily confirm a button exists while it sits hidden behind a modal. I also hold off automating an area still changing weekly, because I would rewrite the tests three times before they caught anything, so I cover it exploratorily until the design settles. And I defend exploratory testing as its own discipline rather than as what is left over. Automation checks things we already knew to ask about. Exploratory testing is how we find the questions nobody thought of, and the serious defects come from there far more often.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How would you measure whether your automation is actually paying off?
- What would you do with a test that fails only because the UI was restyled?
- How do you structure an exploratory testing session so it is not just clicking around?
Related qa engineer questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions