How To Interview–A Quick Guide

This post was originally going to be called “Interview Dos and Don’ts” but I didn’t want it to get confused with interviewing on DOS, or to start a grammar war on the use of Do’s or Dos.

I had the chance to interview a couple of candidates for a senior developer position today. Each one of the interviewees had greater than 12 years experience in developing for SQL Server. Each one of the interviewees had different styles in the interview process.

Rather than focus on specific questions and answers in this post I actually want to look at how each candidate handled themselves in general and in response to questions. All the interviews here were performed by our DBA team of three people.

 

Candidate 1

The first interviewee had a great deal of experience and was already seated when we walked in the room. Rather than stand and greet everyone the candidate stayed in his chair and just reached out his hand. Not a good start.

I figure that everyone has a quick 30 second “this is what I can do” spiel, and so that was the first thing asked. In that situation I would expect someone to give a very brief overview of their knowledge and experience. For some unknown reason this person decided to give a life biography in a rather condescending manner.

Technical questions followed. Each one of those was met with the kind of attitude that indicated “I’m better than you”. Many of the answers were wrong. When asking for clarification on answers we were frequently met with a wave of the hand and “I don’t really know”.

At one point a question was asked and the follow up used some obvious logic to disprove the original answer. At this point I would expect the candidate to change one of the answers. They didn’t. A new and third answer appeared that completely (apparently) disproved the logic. Pretty stunning.

After what was an all too long period of interviewing this person, we let them go and moved on to the next person.

 

Candidate 2

Our second victim interviewee immediately stood and greeted us when we walked in. He had a nervous smile on his face as he shook hands and introduced himself.

The elevator pitch went ok and there was none of the obnoxious behavior the first candidate. Then we started in on the tech questions and things started going a little sour.

I can understand folks getting a little nervous when interviewing but this candidate seemed to go to pieces. Questions were frequently answered with “I know this, but I can’t remember” and a panicked look. With this person being so obviously flustered we tried to get them back on track by throwing over a couple of softball questions. At this point I think we’d lost the candidate entirely and brain panic took over.

At the end of the interview he almost seemed on the verge of tears and it seemed to us that he started trying to play the emotional angle to try and have us feel sorry for him in an effort to have us walk away with a good impression.

We’re DBAs, empathy is bred out of us so this didn’t work.

 

Candidate 3

The final candidate greeted us with a warm friendly smile as he stood, shook everyone’s hand and introduced himself. He repeated back out names to be sure that he had heard them correctly and settled into his seat.

The elevator pitch was spot on. We got a very quick overview of his skills and what he’d been working on recently.

When we started in on the technical questions he gave obvious consideration of what we were asking, looked for clarifying points for some things and provided concise answers. By no means was he able to answer each and every question, however when he did not know he was quick to admit as such, provide what he felt would be the answer and a pointer to where he would look for a definitive answer.

This prompted a question around community involvement in which he mentioned that he liked to attend events like SQLSaturday and read blogs. When asked about favorite blogs he was able to provide a few and name the sessions and speakers from the most recent local SQLSat event. This was a huge plus as this candidate obviously enjoys working with SQL Server enough to spend time and effort outside to increase his knowledge outside of regular work activities.

When a couple of questions were answered incorrectly and we questioned the responses we were met with a genuine interest in getting the correct information and were able to build conversation around those items.

We were sad when time was up and we had a great time sitting and interviewing this person.

 

So which one would you choose?

If you were an interviewer, technical responses aside, which one of these candidates would be at the top of your list?

Captain Obnoxious?
Nervously Tearful?
Quietly Comfortable?

I know which one was at the top of ours.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s