Most candidates I rejected passed the technical screening. They knew the tools. They had the certificates. What they did not have was what this framework measures. Over 25+ years of hiring and building QA teams, I used the same five lenses in every interview to answer one question: do I want this person on my team?
None of these five points requires another certification or five more years of experience. They require a shift in how you think about your work — and how you talk about it. Here is the framework, with the red flags that end interviews, the green flags that earn a yes, and how to prepare for each.
Free companion download
The 5-Point QA Hiring Framework (PDF) · 209 KB
1. Curiosity & preparation
What I was looking for: did this person come in with questions, not just answers? The strongest candidates had done their homework — they had explored the product, read the engineering blog, and noticed something specific they wanted to understand better.
- Red flag: no questions, or only questions about salary, benefits and hours.
- Red flag: generic answers that could apply to any company.
- Green flag: "I noticed you recently migrated to the cloud — how did that affect your testing pipeline?"
- Green flag: demonstrates they researched you, not just the role.
How to prepare: find one thing the company has shipped or published recently, and form one genuine question around it. That is it.
2. Business impact thinking
What I was looking for: can this person connect testing to what the business actually cares about? Most testers report bugs. The testers I hired reported risk — what a bug would cost if it shipped, in money, trust or users.
- Red flag: describes bugs only in technical terms (steps to reproduce, expected vs actual).
- Red flag: cannot articulate the real-world impact of a defect, and treats all bugs as equally important.
- Green flag: "This affects ~12% of checkout users — about 3,400 transactions a month at risk."
- Green flag: frames testing around revenue, retention, compliance and reputation.
How to prepare: have one story ready where you connected a testing finding to a business outcome. Use numbers if you have them.
3. Communication
What I was looking for: can this person make risk understandable to anyone in the building? The best testers could walk into a room with developers, product managers and executives and adjust their language for each — without losing the substance. This is becoming more valuable in QA, not less.
- Red flag: overly technical explanations with no ability to simplify.
- Red flag: blames developers or throws colleagues under the bus.
- Green flag: adapts the explanation to who is asking.
- Green flag: describes handling disagreement constructively.
How to prepare: practise explaining your best testing achievement twice — once for a fellow engineer, once for a product manager who does not know what a test case is.
4. Judgement
What I was looking for: do they know what not to test? When time is tight and scope is large, what do you cut, what do you keep, and can you explain why? This is the skill that separates testers I want from testers going through the motions.
- Red flag: "I test everything" — this is not a virtue, it is an absence of judgement.
- Red flag: no framework for prioritising effort, and no example of a real trade-off.
- Green flag: "I asked the product owner: what are the three things that absolutely cannot break?"
- Green flag: describes cutting test cases deliberately, with reasoning.
How to prepare: have a story about a difficult testing trade-off under pressure. What did you cut? What did you protect? Why?
5. Thinking vs checking mindset
What I was looking for: do they think about quality, or just testing? The candidates I hired saw their job as protecting the user experience, not executing test cases. They questioned requirements and noticed when acceptance criteria missed edge cases. This is the hardest thing to measure and the most revealing.
- Red flag: describes testing purely as following scripts or checklists.
- Red flag: sees their role as "finding bugs" rather than "managing quality risk".
- Green flag: "The criteria covered the happy path, but didn’t address a payment gateway timing out mid-transaction."
- Green flag: talks about testing in terms of risk, user impact and systems thinking.
How to prepare: think of one moment where you went beyond what was asked — where you noticed something that was not in the test plan but mattered. That is your story.
Score yourself before the interview
Rate yourself one to five on each point, and note the specific story you would tell for it. A five means you have a compelling, specific example; a one means it is a development area. The candidates who got hired were not always the most technical or experienced — but they walked in demonstrating these five things.
Key takeaways
- Technical skill gets you screened in; these five things get you hired.
- Report risk, not just bugs — connect findings to business impact.
- Show judgement by knowing what not to test, and communicate to any audience.
- Prepare one concrete story for each of the five points.
Frequently asked questions
What do QA hiring managers actually look for?
Beyond tools and certificates, they look for five things: curiosity and preparation, business-impact thinking, clear communication, judgement about what not to test, and a quality-first thinking mindset rather than a checking one. Most candidates who are rejected passed the technical screen — they were missing these.
How do I stand out in a QA interview?
Come prepared with a genuine question about the company, frame your testing stories around business impact (ideally with numbers), explain risk clearly to any audience, show you can prioritise and cut test effort deliberately, and give an example of noticing something that was not in the test plan but mattered.
Do I need more certifications to get hired in QA?
Usually not. None of the five things hiring managers look for require another certification or more years of experience — they require a shift in how you think about and talk about your work. A compelling, specific story for each point does more than an extra badge on your CV.