Top 5 Test strategy Interview Questions
Browse 5 real-world technical and behavioral interview questions about Test strategy. Review scenarios, edge cases, and architectural best practices.
You have seventy minutes for four coding problems. In what order do you attempt them, and when do you stop polishing one?
Spend the first few minutes reading all four problems and their constraints, then solve them easiest first so points are banked early. Give each a time box, submit a working version once it passes your own checks, and take partial credit on hidden tests rather than chase one perfect answer.
How do you decide what to automate and what to leave manual?
Automate what runs often, has a deterministic oracle, sits on a stable interface, and guards an expensive escaped bug. Push each check to the cheapest layer that can still fail meaningfully, treat flakiness as a defect rather than noise, and keep human time for exploratory testing, not scripted regression.
You are reusing a component that has run without incident for years in another product. What does your test strategy have to say about it?
A clean track record is evidence about the old system's operating envelope, not about yours, so the strategy must surface the assumptions the component inherits, test it against the new envelope rather than trusting its history, and state which inherited assumptions are going untested.
What is the test pyramid, and is it still the right model for your system?
Buy most of your confidence from fast isolated tests and little from slow end-to-end ones, because cost and flakiness rise as you climb. It is a claim about where risk lives, so a system whose risk sits in integration - a thin service over a database - correctly has a different shape.
Where do you draw the line between a unit test and an integration test, and how do you keep a few thousand of them under ten minutes?
Draw the line by what the test is allowed to touch - a unit test stays in-process, an integration test crosses a real boundary. Mock collaborators, never the component under test. Use Testcontainers for real dependencies and keep the suite fast by reusing the Spring context and the containers.