15 / 52 · 25 Interview Preparation & Career · Culture Fit and Values← prev⊞ allnext →☰ Read as one page
2.8Evaluating Whether the Company Is Right for You
The interview is a two-way evaluation. Watch for these signals:
Green Flags
- QA is involved in sprint planning and design discussions
- The team talks about quality as everyone's responsibility, not just QA's
- There is investment in test infrastructure and tooling
- Developers speak respectfully about the QA team and process
- There is a clear career path for QA engineers
- The team measures quality with metrics beyond just "bugs found"
- They can articulate their testing strategy and why they chose it
Red Flags
| Red Flag | What It Signals | Question to Confirm |
|---|---|---|
| "QA tests after development is done" | Gatekeeper model, no shift-left | "At what point in the sprint does QA get involved?" |
| "We don't have time for test automation" | Short-term thinking, growing tech debt | "What is your automation strategy for the next year?" |
| No QA in sprint planning | QA is an afterthought | "Who attends sprint planning?" |
| "The developer who wrote it tests it" | No independent quality perspective | "How do you get a fresh perspective on testing?" |
| High QA turnover (check LinkedIn) | Systemic culture or workload issues | "How long has the longest-tenured QA engineer been here?" |
| Vague answers about quality challenges | Either they do not know or they are hiding problems | "What is the hardest testing problem you are solving right now?" |
| "We need someone to just run test cases" | The role is manual execution, not engineering | "What percentage of the role is manual testing vs automation vs strategy?" |
| No mention of CI/CD or test automation in the job listing | Immature testing practice | "Walk me through what happens from code commit to production." |