Why do you want to be a tester?
BehavioralJunior
In shortTell a short, true story about what drew you to testing, say what you enjoy about the work itself (investigating, thinking like a user, making things reliable), and show what you've already done about it.
Model answer
A strong answer has three parts:
- A true moment or pattern that drew you to testing.
- What you enjoy about the work itself: investigating, narrowing a vague problem down to exact steps, thinking like the user, helping the team ship with confidence.
- What you’ve done about it: a course, a practice project, bugs filed in an open-source project, a beta program.
Example answer:
In retail I was always the one who noticed when the till prices didn’t match the shelf labels, and I’d track down why: a wrong product code, an old promotion. When I learned that testing is basically that for software, I took a course and tested a practice food delivery app end to end. The part I enjoy most is turning “something’s wrong with checkout” into exact steps a developer can fix, and knowing that real people won’t hit that problem.
What to avoid
| Answer | Why it hurts |
|---|---|
| “QA is easier than programming.” | Suggests you don’t respect or understand the role. |
| “I want to move to development in a year.” | Fine to grow, but leading with leaving is a red flag. |
| “I like technology.” | Says nothing about testing. |
It’s perfectly fine to mention you’re curious about automation or other directions later. Frame it as growing within quality, not escaping it.
Learn more: Tell Me About Yourself and Why QA
What they're looking for
That you understand what testers actually do and chose QA on purpose, with real motivation and evidence that you've acted on it, not that you see it as an easy way into IT.
Common mistakes
- Saying QA is an easy way into IT or a stepping stone to development.
- Generic answers like "I like computers" or "I'm detail-oriented".
- Describing testing as only "finding bugs", without the user or the team.