Do you have any questions for us?
BehavioralJunior
In shortAlways say yes and ask two or three genuine questions about the work, the team and the next steps, for example how testers and developers work together, what a great first three months look like, and how releases are tested.
Model answer
Always have two or three questions ready, and adapt them to who you’re talking to. The answers also help you decide if you want the job.
About the work
- What does a typical week look like for a tester here?
- How do testers and developers work together? When does QA first see a feature?
- Is testing mostly manual, automated or both? Is there a path toward automation for someone interested?
- How are releases tested, and who decides whether something ships?
About the team and growth
- How many testers are on the team, and who would I learn from?
- What would a great first three months look like in this role?
- What’s the biggest quality challenge the team has right now?
About the process
- What are the next steps, and when can I expect to hear back?
Match the question to the person
| Interviewer | Good topics |
|---|---|
| Recruiter | Process, timeline, team structure, salary range |
| Tester or QA lead | Test process, tools, releases, learning |
| Developer or product owner | Collaboration, how bugs are handled, what they value in a tester |
| Manager | Expectations, growth, how success is measured |
Benefits and vacation are fair questions, best asked with the recruiter or at the offer stage.
Learn more: How QA Hiring Works
What they're looking for
Real interest in the role and in how quality works in the team, plus the judgment to ask about things that matter for doing the job well.
Common mistakes
- Saying "No, I think you covered everything."
- Asking something the job ad or website already answers.
- Leading with vacation days or perks in the first technical interview.