Recruiter/Interviewer

[dialex]

• http://katrinatester.blogspot.co.uk/2017/03/how-do-you-hire-junior-tester.html
• http://blog.eviltester.com/2017/03/how-do-you-interview-testers.html
• https://dojo.ministryoftesting.com/lessons/tips-for-interviewing-junior-software-testers
• http://sethgodin.typepad.com/seths_blog/2018/01/getting-paid-what-you-deserve.html
• https://hbr.org/2017/12/how-to-highlight-your-talents-in-a-job-interview-without-showing-off
• https://azevedorafaela.com/2020/05/29/hiring-and-onboarding-a-qa/

[dialex]

[dialex]

Manual tester:

Draw an architecture on a whiteboard and ask them how they would test it. See which areas they focus on and which they ignore and then question them accordingly

e.g. do they focus on the UI? If so ask them about testing the backend systems the UI talks to. Get them to identify how they would break it up a bit so that they don't test everything through the UI. IMHO there's no hard and fast questions that give you guaranteed answers. It's really a question of trying to work out if they are going to explore a system properly

throw a few curveballs in there as well to make it awkward for them and see how they work around issues. Play the role of an awkward product manager/developer/somebody else who tries to guide thier testing in the wrong direction and see how they deal with that

For me it's mainly about giving them a series of challenges and seeing how they react.

• Are they going to explore the problem in depth and try and find issues?
• How do they deal with adversity?
• How well can they explain what they are doing and why?

I'm not so much interested in what they have done before at this stage (their CV will have told you that if you want to know). I wouldn't want to spend lots of time with them explaining their previous projects. If they have some relevant experience they can bring to the table, that's great, but don't let them turn it into an hour long re-reading of thier CV :wink:

-- Mark Colin