You join a team with almost no automated tests and frequent production bugs. How would you build a test strategy over your first few months?

What the interviewer is looking for

• This question tests test design & strategy. Thinks in risks, edge cases and boundaries, balances unit, integration and end-to-end tests, and explains why.
• Strong answers: Analyses where bugs come from, protects the highest-risk flows first, adds tests to the pipeline, involves developers, and measures escaped defects.
• Likely follow-up: How would you show leadership that the effort is paying off?

Another way it may be asked: Imagine a team that tests everything by hand and keeps shipping bugs. Where would you start, and how would you grow it?

A structure to follow: Frame, structure, analyse, recommend

1. Step 1

   Frame

   Restate the goal and ask what success is and what the constraints are.

2. Step 2

   Structure

   Split the problem into a few separate parts you can check one by one, and say what you will look at first and why.

3. Step 3

   Analyse

   Reason with the information you have, state your assumptions out loud, and say what data would change your mind.

4. Step 4

   Recommend

   Give a clear recommendation, the main risk, and the first step you would take.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Listing ideas without choosing between them.
• Hiding assumptions instead of stating them.
• Finishing without a recommendation.

How to practise it

Answer in four spoken parts, one per step, then check you ended on a recommendation.

Related questions

• If I asked you to test a login page, what kinds of cases would you think about beyond just a correct username and password?
• How do you decide which tests belong at the unit, integration and end-to-end levels for a new feature?
• You find a bug that only happens sometimes. What goes into a bug report so a developer can actually fix it?
• How would you test a REST API endpoint that creates a new customer record? What would you check?
• What makes end-to-end browser tests brittle, and how do you write them with tools like Playwright or Cypress so they stay reliable?

Browse all questions