For the past year, I’ve spent an inordinate amount of my time at work trying to hire new people. It just takes forever. And good results (like, actually hiring someone) are hard to come by. I think mostly this is because, for this job, we need people whose skills lie at a unique intersection. Not only must they be good presenters and comfortable working with people of all different types and temperaments, but they also have to possess deep technical knowledge and confidence. Unfortunately for me, of the handful of people out there who do both really well, they pretty much all have good jobs already.
Anyway, I’ve probably interviewed an average of about three candidates a week for the last six months, some overseas (for international roles in our satellite offices) and some here in North America. Along the way, I’ve gotten very good at quickly figuring out whether someone is viable, and I’ve also been exposed to all manner of silliness and deceptive tactics people use when trying to get their respective feet in the door. I’ve also ceased being surprised when people do amazing things like, uh, not being there to answer the phone at the scheduled time. (Talk about unprofessional!)
Today’s experience was extra funny, however, so I thought I’d use it as an excuse to write this exposition about one of my Least Favorite Job Activities.
This afternoon I had an interview with a candidate from London. He had already been vetted and approved in the non-technical dimensions through interviews with some of our employees in the UK. However, since our London office doesn’t currently have another person in this role, that means they also don’t have someone who can do the technical evaluation any justice. Lately, that’s been falling to me, which of course means in each case that one of us always gets to enjoy a phone call at an obnoxious hour.
Anyway, after a few botched attempts with cell phones and long distance provider issues earlier this month, we finally got it set up for real this week, and the applicant is set to call me right after lunch my time. I learn a few hours beforehand that he had a job snafu that was going to interfere with his schedule a bit, but that he would attempt to make the call from his cell phone. It turns out that that worked out fine, and, when he introduced himself, he apologized for needing “to switch phone lines in about 15 minutes when I reach the house.” No problem, I thought.
After some brief introductions, I launch immediately into the first, fairly straightforward technical question. I’ve given him a simple programming problem description and asked him to talk me through how he would write code to solve the problem. I get my first warning flag immediately when he starts out by saying, “Well, you see, you have to understand where I’m coming from. I don’t write computer code every day. I can work with ‘adapters’ and ‘interfaces’ when necessary, and I can look stuff up online or learn it from a book as needed.”
The minute an interviewee starts making excuses for not being able to write college freshman-level code — and especially if they go down the obfuscatory path of talking about higher-order abstractions like adapters and interfaces and methodologies — it’s incredibly likely that he or she will not pass the interview. Moreover, I especially don’t like it when candidates for a sales position cannot directly say, “I don’t know the answer to that.” I think even non-technical people aren’t dummies. It’s patronizing and risky to be evasive when you’re asked about something you just don’t know or you don’t understand. Double buzz for this dude, right out of the gate.
About fifteen minutes later, we’re still muddying our way through this basic problem. I’ve given up on him already, so I’ve switched modes and am generously giving out the steps that lead to the answer so that, well, at least we have something to talk about. (And maybe he learns something to boot.) As I’m waxing philosophic about some part of the problem or other, though, I get the impression that he has arrived at his destination and that he needs to accomplish the phone switch-e-roo that he warned me about earlier. I shut up for a minute to give him a chance to speak, and sure enough,
“Err, yeah, I’ve made it to my in-laws. I need to drop my daughter off inside, and then I will try to call you back. I’m not sure if I’m going to be able to call you back, but I will try.”
Only twenty minutes have passed in our scheduled hour, and for some reason I pretend that I’d enjoy filling out the whole hour, “Great, we’ll pick back up with this in just a minute then!”
“Um, yeah, I’m not sure… do you have more availability later in the day?” (Keep in mind it is already nearly 9pm his time.)
“No, I’m afraid not. I do have the next thirty minutes that we’d scheduled.”
“Well, okay, um, yeah, I’m not really certain if I’m going to be able to get to another line. I might just need to contact the recruiter and let him know.”
Let him know what, pray tell?, I think. “Okay, well, I understand. Do the best you can, and thanks for your time.”
I guess it’s a good strategy for you future interviewee-ers out there: preface your call with the warning that you “need to switch phones” halfway through, and then use that as a way to bail on the call if you think you got in over your head! I thought it was hilarious. I immediately started writing my summary email to my colleagues in London, and I went ahead and hit Send right away after adding that I was willing to wager 100:1 that he wasn’t going to be “finding another line.” So much for that interview!