How to Use Behavioral Interview Questions in a Technical Interview


During a job interview, digging into a candidate’s technical depth is just as important as determining cultural fit.
Recently I was looking over the shoulder of a CTO of a small, fast-paced Silicon Valley firm. He had asked me to help him polish the job responsibilities he had for a senior technical hire he wanted to make.
The responsibilities looked like this:
Once he had decided on these responsibilities, I asked him what type of questions he would ask to determine if a person could accomplish these responsibilities. To my surprise, one by one he went down the list and turned each one of them into a behavioral interview question.
To do what my CTO friend was able to do, one must first understand the structure of the behavioral interview question. It starts with knowing how to design a request for information in such a way that the candidate has to look into their past experience for the answer.
To create a question out of any job responsibility, add an introduction to a situation related to that responsibility.
1) The beginning or introduction
This is most often a phrase like:
2) The situation
By combining these two elements, my CTO friend was quickly able to construct the following questions:
When I asked my friend how effective he felt his questions were, he said they usually get him most of the information he is looking for. However, with a candidate who is not particularly talkative, he might have to dig for more information.
He does this by asking about the problems that they were facing, the actions that they took, and the results that they achieved. Otherwise known as the PAR technique.
After each question, he said he listens carefully for each of these three components in their answers and asks for more information about the ones he does not hear.
He uses these examples to complete his interview evaluation form.
Use the responsibilities section of the job description as a foundation for your behavioral interview questions. This can turn in any bone-dry technical interview into a useful conversation.
Simply combine an introduction with a technical responsibility and you will likely have a behavioral question.
image from fastasista/freedigitalphotos.net