Let me start with a side note: this post could either way be titled “The Question I Will Ask during Interview.”
It all started when I asked my better half one question we often use during interviews with developers. Actually it may sound a bit weird to ask a surveyor a question taken from an interview with a programmer. It may sound even weirder that my wife’s answer would easily put her in a better half of answers I get for the question. Without sweating.
The question is simple: imagine you have programming language which has addition, subtraction and multiplication of integers already implemented. Your goal is to propose an algorithm for division operation.
Disclaimer: I am well aware I’ve just published one of my standard questions from interviews.
Other disclaimer: no, I don’t do that because I have an evil plan not to ask the question any more.
Another disclaimer: I do know that some, not so many actually, candidates I interview happen to google this blog, or even read it from time to time.
One last disclaimer: I am not dumb. Or so I believe.
What’s going on then? What I want to share with you today is that many questions you’re going to hear during an interview with me are just excuses to dig deeper. In this very case the question could sound more like “show me the way you think” but it would be sort of hard to answer the question stated this way.
But there’s more. Not only do I look at your reasoning and the way you tackle issues but also you give me some insight when you give up. In other words, I don’t look for an answer although there probably is one, which is sort of optimal. I try to observe how you act when solving not-so-complex issues. Something you’re going to do pretty damn often if you accept the job.
This is a pattern I follow when recruiting. I could probably safely publish the whole list of my standard questions and I would still learn what I want about interviewees.
Of course that doesn’t mean we don’t check technical expertise. We do. Well, “we” is sort of abuse here. My colleagues do. So while my wife would probably shine during the “soft” part of an interview, blank stares she would give during technical part would scare away our recruiters in just a few minutes.
The interesting part is: if you don’t have decent answers during the first part your technical excellence doesn’t make any difference. We just don’t want to work with people who find it hard to think.
And by the way: yes, this is an experiment. I’m waiting for the moment when an interviewee tells me that they’ve read an interesting post recently so the next question isn’t a surprise. At all.
Anyone wants to bet when it’s going to happen?