Why are you interested in QA / testing?

Interviewers ask this to gauge whether you've actually thought about the work or are just looking for any tech job. The answer doesn't need to be dramatic — it needs to be honest and specific.

Pick a real reason and own it. Common authentic motivations:

• Curiosity about how systems fail — you find it interesting that production is full of edge cases nobody anticipated.
• User advocacy — you care about the customer experience and testing is where that lives in the dev cycle.
• Systems thinking — you like seeing the whole picture: code, infra, data, behaviour.
• Bridging roles — you enjoy working across product, dev, and design.

Anchor it with a moment. A short story about when QA "clicked" for you carries far more weight than abstract reasons.

A sample answer (Past–Present-style): "I started in [support / development / a related field], and I noticed I was drawn to the moments when something broke in an unexpected way — not just fixing it, but understanding how it had slipped through. The first time I wrote an automated test that caught a regression a week later, I realised QA was where I wanted to spend my time: it sits at the intersection of code, product, and user experience, and the work compounds. Every test you write protects future engineers from the same bug. That's the part I find genuinely satisfying."

Avoid:

• "I like breaking things." — Cliché, and slightly worrying. QA isn't about adversarial breaking; it's about preventing user pain.
• "It's a good entry point into tech." — Honest but one-dimensional. Show you've thought beyond it being a foot in the door.
• "I have an eye for detail." — Generic. Anyone can claim it; ground it in something concrete.