It’s not often that I get to interview potential new tester colleagues so I asked for input from the test community on Twitter to help me out.
This is the thread if you want to skip this post, but I’ll also make a more readable list here.
Any brilliant no-brainer questions when interviewing for a potential new tester colleague?
— Maaike Brinkhof (@Maaikees) August 1, 2018
My favorite suggestion was made by Joep Schuurkes
A question I like to ask everyone:
Imagine you’ve just come home from work. You feel great and are full of energy. It was an awesome day. What happened during that day?
Phrasing matters: I want them to remember that feeling before answering.
Inverse question is also a good one.
— Joep Schuurkes (@j19sch) August 2, 2018
This is not only a great question to ask someone else, but also to ask yourself! If I had to answer it would probably be when I have found some hard-to-find bugs with exploratory testing (I like the detective work in testing) and when I have paired or mobbed with my team for programming or testing purposes. In general, when people are working together with empathy and understanding for one another it makes me happy.
Huib Schoots suggested asking the candidate how they learn.
How do you learn?
— Huib Schoots (@huibschoots) August 1, 2018
I ended up using this question during the interview and it was insightful. Something interesting did happen on a personal level. I had answered the question for myself beforehand and when the candidate answered something in a completely different direction I had a hard time not steering them in my direction.
Another great question came from Benny Cornelissen:
Regardless of what kind of role (dev, test, infra) I’m interviewing for I always try to figure out what their personal goals are. Some people just want to work with cool tech, other people want to be on stage, or want to mentor others.
— Benny Cornelissen (@whieee) August 1, 2018
This is also a good question to ask yourself as well. I like it a lot more than the cliché question “where do you see yourself in 5 years?”, because when I hear that one, all I want to do is yell “how the f do I know!?”. Thinking about personal goals without the arbitrary 5 year thing feels much better.
Lanette Creamer suggested asking about the best tester they’ve worked with.
Describe the best tester you’ve ever worked with. What made them great? If they say it is themselves, beware. The reasons can be eye opening.
— Lanette Creamer (@lanettecream) August 1, 2018
There’s a little trap in there too because when they nominate themselves for this honour it can reveal arrogance and that warrants some follow-up questions.
Next, 2 questions that reveal a lot about the candidate you’re interviewing:
Not sure if it fits a “no-brainer” description, but I like to ask “what is testing” or “why do we test”. First time I asked I was told it’s “a bit obvious” to ask such question to a Sr QA. Yet, we adopted it.Ever since then I enjoy tons of no-brainer answers that it might trigger
— Mr. Viktor Slavchev (@TheTestingTroll) August 1, 2018
These are very dangerous questions that I think many testers struggle with. There are some red flags if a person says “checking if the software works according to spec” or “writing automated tests to see if the software is correct” and nothing more.
Of course, we also have to ask about quality, like Marit van Dijk suggests.
What is software quality to you?
— Marit van Dijk (@MaritvanDijk77) August 1, 2018
This question is almost always guaranteed to lead to an interesting conversation.
More suggested questions and topics:
- what do you like about working in testing? (Magnus Pettersson)
- what is the latest blog post or book you’ve read about software development or testing, and what did you learn from it? (Karol Szewczak)
- What do you do when you have nothing to test? (Toine Schoenmaekers).
- How do you handle developers when they say “it’s not a bug”? (Sanchita)
- When was the last time you helped someone on your team? (Rüdiger Schnirring)
- What is the most interesting defect you’ve uncovered? (Paul Grossman)
- You have a bug on the build and the developer says “works on my machine”. What do you do? (Jose Pita)
- Why do you want to work for our company? (Fred Steenbergen)
- Could you draw your ideal pipeline? (Finbarr Brady)
I hope this helps you out a bit! It certainly helped me very much, thank you to everyone who answered. Cheers