Hiring Testers, Part 1: How about a cup of MOCHA?

A cup of MOCHA

A cup of mocha.

Caffè Mocha or café mocha, is an American invention and a variant of a caffe latte, inspired by the Turin coffee beverage Bicerin. http://coffee.wikia.com/wiki/Cafe_mocha

This is the first post of several in a series of post on my experiences in hiring software testers.

Interview or Interrogate

A friend of mine recently reminded me of how different job interviews can be, when he told me about his latest experience. He was upset over the interrogation he had gone through for an hour with out being able to actually ask any of the questions he had prepared for the interview.

I was quite upset myself since I see a job interview as a conversation and I had difficulties in relating to the interrogation style. The interview serves as a discussion where my aim is to gather as much information as possible about the candidate. However I can see that there might be some type of information that you would get from an interrogation.

Perhaps the interrogator was interested in how the candidate reacts under pressure. Maybe the person was looking for very specific answers, correct answers since the questions where very much related to technical knowledge.

I believe most people are already under pressure when in an interview. I think there is enough stress in the situation. Unless you are looking for someone who will handle extreme situations I don’t see the purpose of using the interrogation as a style of interviewing. I prefer to create a relaxed environment and open up for a conversation when I interview people.

My experience comes from many years of interviewing in the role as a test leader and test manager. I’ve researched the field of interviewing in tech and I am very influenced by Johanna Rothman. I highly recommend her book Hiring Geeks That Fit.

I see interview as an art, where you need to follow the flow but also influence it. Asking questions is an art. Based on Johanna Rothman’s suggestions on how to ask questions I have created a heuristic to help me ask the “right” questions in an interview.

A cup of MOC(H)A

A cup of mocha describes my style of interviewing. It’s like having a chat over a cup of coffee ( or tea if you prefer). Mocha reminds me of the type of questions to ask during the interview and how to ask them, and to keep the right blend.

Meta questions
A meta question is a question about questions. I use it very rarely but something I might ask in the end of the interview is: “What question have I forgotten to ask you?”
The reason I ask this question is to find out if there is something the person thinks is important. It might help me to find new areas to discover.

Open questions
Open ended questions are the one’s I use the most. They are questions that reveal information on behavior. Questions might start with why, what, how? I mostly open up the discussion with a : “Tell me about a situation where…”  I listen, observe and follow up with open ended questions.

Closed questions
Closed questions are some what binary. They often lead to very short answers when asked. I frequently use closed questions in the first scanning interview. If there are specific requirements needed for the role I will start with these questions. They describe facts.
It might be questions like: “Do you have any experience in Python?”
I also use closed questions to find out where to explore further. Questions such as: “Have you ever been in a situation where you had to…” If the person have experience from this particular situation I would probably continue with an open question.

Hypothetical questions
I rarely use hypothetical questions (which is why I have put the H in parenthesis) They are not suitable as behavioral questions and often lead to the candidate answering what you think they want you to hear. However I use hypothetical questions sometimes as part of auditions (see below). But in those cases I am more interested in the thought process than the answer.

Auditions
I highly recommend auditions especially when it comes to testers and developers. How else can you tell how some one actually performs? The audition consist of different assignments that I give to the candidates. One of them is to watch them test a product.  This is something I believe most people feel stressed over. So putting the candidate under the pressure that an interrogation causes is completely unnecessary. It is important for me to try to make it as relaxing as possible.
The audition might also contain a simulation where the tester is given a context and special assignment to solve.

My blend of MOCHA contains a high amount of open questions and auditions.  How does yours taste?