How do you get developers to own quality and write tests themselves, instead of treating testing as your job alone?

What the interviewer is looking for

• This question tests collaboration with developers. Works as a partner to developers, shares testing skills, and promotes shared ownership of quality.
• What to bring out: Makes testing easy with tools and examples, pairs with developers, involves testing early in design, shares bug data, and gets leadership support.
• Expect a follow-up like: Tell me how you handled a developer who strongly resisted this.

Another way it may be asked: Developers on your team say testing is the tester's job. How would you change that?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the collaboration with developers you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

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

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

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?
• 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?
• Your nightly test suite fails randomly about one run in five. How do you track down and deal with the flaky tests?

Browse all questions