I disagree. Don't get me wrong, I want someone that can transform requirements into test scripts but I what I really want is someone that can THINK. Someone that can test what's not in the requirements document. To quote Anne-Marie Charrett, I want to hire someone that says, "Don't hire me if you want perfect software. Don't hire me if you're looking for a tester to only "check" if things look ok."
For my interviews, I developed a standard list of questions to ask. Each question was carefully thought out and has a specific purpose for being asked. Here's my list:
- How did you get into software testing?
- What do you like about testing?
- What are your frustrations with testing and how do you deal with them?
- For example: How do you deal with being the resident naysayer?
- For example: How do you deal with defects that just never seem to get fixed?
- What comes to mind when you hear the term ‘Quality Assurance’?
- Compare and contrast automated and manual testing.
- Compare and contrast scripted and exploratory testing.
- How confident are you in your ability to deliver defect free software?
- What essential information should be included in defect report?
- How do you determine if something is working correctly when you have no documentation?
- What’s your experience with Agile?
- How do you sharpen your testing skills?