Month: November 2009

On Interviewing

I have to admit that I find the process of interviewing prospective candidates for a job to be an odd mix of exciting and nerve-wracking. While I absolutely love getting to know people and thinking of the possibilities for them within my organization, I find I often worry about making candidates comfortable and not breaking any of the intricate set of HR laws surrounding interviews. Overall, though, I really enjoy it.

Interviewing geeks has its own challenges, as many of them come in to the interview extremely nervous and shy. Since I can hold a meaningful conversation with a coffee table, I usually talked to them until they would eventually stutter out a few replies from which I could get a decent read. If you’re not as ridiculously extroverted as I am, however, you may find interviewing geeks challenging.

If you’re interviewing geeks, you have to first define your goals. They should be in these general buckets:

  • Technical ability. Can they execute the geeky part of the job?
  • Personality requirements. Can they execute the non-geeky part of the job?
  • Team fit. Will they have credibility on both geeky and non-geeky levels with their fellow geeks and the company as a whole?

Once you’ve defined what belongs in those buckets, figure out how to get to them.

  • Technical ability: What kinds of situational or technical questions do you need to ask? Should you give a written or computerized test? Make sure that the questions are appropriate to the level of the position for which the candidate is interviewing.
  • Personality requirements: I love behavioral interviewing for this. Propose a situation to them and ask how they’ve handled similar situations in the past or would handle this situation in the future. Ask them to tell a story about the last time they got angry or made a mistake.
  • Team fit: You may be able to determine team fit from their answers to the above, but sometimes geeks don’t give much away in their personality even while telling behavioral stories. In that case, it’s time to schmooze. Ask how their weekend went or what they do for fun, and volunteer your own weekend stories and your hobbies. This piece has the most two-way conversation of the entire interview, and those of us who tend towards the quantitative often forget the value of this “useless” chatter.

I haven’t always been perfect in my interviewing (note to self: write blog post on terminations), but as I started defining my goals (“buckets”) and figured out how to get to them, I was able to much better identify good geeks.

On Skepticism

At the ILTA ’09 conference in August, I attended a couple of sessions by Jason Dorsey, the Gen Y guy. At the second of his sessions, he mentioned a service online that helped people find couches to crash on. Then he said, “You Gen Xers in the room are looking this up right now to see if I’m telling the truth.” I quickly dropped my Blackberry and pretended that I hadn’t been doing exactly that, much to the amusement of the Boomer sitting next to me.

Gen X leaders aren’t as common as we should be. At the point in our careers when the previous generation should start retiring to let us take over, they’re not. Their 401Ks have been decimated, and they just don’t feel old yet (hi, dad!). I was very fortunate to be able to move into leadership early in my career.

As a Gen X leader, I found that leading and managing other Gen Xers was incredibly easy. Here are my tips for managing Gen Xers:

  • Maintain honesty and credibility
  • Address their skepticism
  • Be yourself

Luckily, this leadership style works well for geeks, too, since their intelligence and natural skepticism means that many of them have Gen X attitudes even if they’re older or younger than that generation.

I have to wonder whether anyone has studied Gen X attitudes (skepticism) and juxtaposed that with geek attitudes (also skepticism). I also have to wonder if that means that Gen X geeks are incredibly difficult for non-Gen X non-geeks to manage…

Vendor Story: Message from beyond the grave

I meant to post this Friday, since it would have been more appropriate for Halloween, but I’m a bit late with it.

I had been IT Director of a Boston law firm for about 4 years, which was plenty long enough to have learned to stop answering my phone. For those of you who might not know, anyone with any sort of decision-making responsibilities in IT could easily spend 10 hours/day just fielding cold calls. As such, if we don’t recognize the number (or if we don’t have an assistant to field the calls), we don’t pick up.

While I didn’t answer my phone, that didn’t mean I didn’t get my voice mail. One day, I got this message:

Hi, Jenn! This is (vendor) from (company). I was just talking to (partner), and he told me that you should definitely get back to me, since your firm is very interested in (service we needed like holes in our heads).

Not such an unusual message, right?

Here’s the problem: that partner he had “just been talking to” had passed away nine months before. To add insult to injury, said partner had been out for nine months before that battling cancer.

I didn’t call the vendor back, but I was sorely tempted to ask him how that partner was doing and what medium he used to talk to him. I mean, wouldn’t that partner’s widow want to know…?