Resumes and Interviews – Making the Cut

Yesterday, I posted about crazy things I've seen in resume cover letters. This time around, I thought I'd share how I actually review the resumes and candidates themselves. If you are looking for a job, maybe there will be some wisdom in here for you. If you're hiring someone, maybe this we can compare notes. I'm always looking for ways to improve my interviewing skills, as well as be able to uncover that real gem of a resume.

Stage 1 - The first cut

The first thing I do when trying to find the ideal candidate is to quickly review the cover letter. I then take a short scan of the most recent experience to see how it matches up to the job we're advertising. I basically grade the resumes at that point with an A, ?, or No. I always write down the reasons for a No rating, some of which were listed here. If I get a ton of resumes, and many of those end up in the A or ? piles, I'll do a second or third pass to thin them down to a reasonable number.

Stage 2 - The second cut (the in depth review)

I then go back to the A and ? resumes, and review them in detail. I spend a lot of time looking at the candidate's experience, weighing it against the job description. It's important to me that I find someone who can do the job we have, but won't be bored because they are overqualified. To do this, I need to get a really good look at the work experience. This means that I'd like to see the following for each job listed in the work experience section of the resume:

  • Company name.
  • Position(s) held.
  • A brief, but pointed, summary of job duties.
  • The period of time candidate was there (Month/Year to Month/Year)

Next, I go through it looking at:

  • The length of time spent in each position.
  • The duties in each position.
  • Can I see where the listed skills are in line with those positions? (i.e. Does the resume support the skills they claim to have?)
  • The amount of time unaccounted for between positions (I make notes to ask about this if I get a "Relevant Experience" resume.)
  • Were the job duties progressing or flat?
  • Is their education progressing or flat?

This last point can be interesting. This time around I specifically requested a 3rd or 4th year accounting student. I actually got an application from someone who had taken one accounting course and, as it appeared from the resume, quit. She then pursued a certificate in golf course irrigation design, complete with AutoCAD certification. While admirable, it hardly gives the impression of someone who truly has their goals set on getting their accounting designation.

As I go through the second cut phase, it is not at all unusual to have resumes move from A to ? or vice versa, but mostly you just end up moving resumes to the No pile. My ultimate goal is to get down to between 6 and 8 resumes that I'm interested in. The real question comes down to what you do if you eliminate them all, or leave only one. I'd suggest that far too many people just soldier on and interview someone but, in my experience, this is rarely the best route. You should re-evaluate the position, re-craft the ad, and re-advertise the position. Hiring out of desperation rarely leads to a good hire.

Stage 3 - Phone Interview

I always do this... even if I KNOW that I'm going to interview the person, I phone and tell them that I'm conducting a short phone interview. I ask a few questions about their resume that I'd like to know, and see how they handle it. I cannot overstate how important it is to represent this a part of the interview process. There are times when it becomes very obvious after 30 seconds on the phone that you don't want this person, no matter how good their resume is. If you've already offered them an interview, you can't gracefully back out of it, which means you're going to be wasting time on an interview for everyone. The intention is always to offer an interview when you dial, but it gives you a graceful exit if the phone call turns you off.

Stage 4 - The Real Interview

By the time the candidate gets this far, their paper looks good. So then we need to interview them. I think it's helpful to remember why we interview, as well as review how we should interview:

Why we interview

The interview serves three main purposes, IMO:

The first thing the interview does is that it helps fill in the gaps that aren't obvious in the resume. I'll ask direct questions targeted at these points. "Why were you only there 3 months", "What did you do here?", "Why was there a 2 year gap in your work history?". Sometimes candidates will be hazy about these kind of questions, sometimes they will tell you way more than you could ever want to know. You need to be careful about not asking a question that is in violation of labour standards regulations, or that could lead you into a discrimination suit if you decide not to hire the person.

The second thing the interview provides is a way to verify the paper. I've seen estimates that as many as 80% of people either lie about or substantially embellish their skills on their resume. This is your last chance to see if the candidate seems to demonstrate the skills they say they have. I've made candidates complete bookkeeping tests, and asked for pointed examples of the most complicated work they've done. As I mentioned yesterday, anyone who tells me that they are an expert in a software program gets grilled. I will never ask anyone to grade themselves out of 10 in a software program any more, as inexperienced users overgrade themselves, and experts tend to downplay themselves. For this reason, the rating is useless... but if they volunteer... I'm particularly hard on those who claim to be Excel experts, maybe because I know a little about the program myself. My typical line of questioning goes like this:

  • "What is the most complicated formula you've ever built in Excel?"
    • 90% of the time, this is enough to expose their level.
  • "Have you ever used a VLookup formula?"
    • If they answer Yes to this, they get asked EXACTLY what it did. I'll also substitute other formulas depending on the answer to the previous question.
  • "What do the letters VBA mean to you?"
    • Of all the candidates I've ever interviewed, only one candidate ever had an answer to this question, and he then told me that he didn't need it. Despite this, he still rated himself a 10/10 with Excel. I have a bit of a challenge with that.

Understand that this has nothing to do with showcasing my superiority. Far from it. The idea is to get to the bottom of what they do know. If they claim to be experts in Word, I'll go after them about Styles, bookmarks and VBA. And if they claim to be experts in Internet Explorer I'll probably just laugh. (Every high school student seems to be an expert in surfing the internet these days.)

The final major point that I'm trying to nail down in the interview, which is VERY difficult to determine, is their personality. I need to know that the person is going to fit with my existing team members. This is very much a "feel" type thing, so I can't really say much more about it, except that it is of critical importance.

How to Interview

This part is, to me, the most interesting of the process. I've seen some really bad interviews, and been interviewed by a few people who seriously needed some training in that regard. Of all the interviews I've ever had, only my current boss knew how to interview properly.

I've been told several times by candidates that I've given the toughest interview that they've ever had. They are always careful to point out afterwards that it wasn't unfair, just tough. I really made them think, and they felt like I'd really gotten into them to get stuff out. It's actually kind of flattering to hear, as I've seen first hand how useless some interviews can be. Now I'm not saying that I'm perfect, and I'm certainly not saying that I've only hired good people because of it. Far from it. The odds are dead set against you when trying to hire a new person, so the best you can do is use the tools at hand to mitigate the risk here.

So what's the secret? Open ended and behavioral questioning. That, and having two people to conduct the interview.

Before I start, I tell each candidate a few things:

  • I will be asking them a series of questions. (Hopefully this isn't a shock!)
  • I will be taking notes. This allows me to review their responses later to ensure I don't forget anything.
  • When answering questions, wherever possible, I would like specific examples of where they have done things in the past, not generalizations.

If you look carefully at the Excel questions above, you'll see that questions 1 & 3 are open ended questions. And while question 2 is not, (it allows a yes/no answer,) it will be immediately followed up with an open ended question.

The reason for this is that you have this person in the interview to hear THEM talk. Hearing them say Yes or No all the time doesn't give you a true look into the person at all. I'm looking for more than just if they know what a Vlookup formula is when I ask them this question. I want to get an insight to their creativity. I also want to find out if they "used it" or "built it".

The next part is behavioral questioning... I've been taught, and thoroughly believe, that the best indicator of future performance is past performance. This means that I need to know how someone reacted to certain situations in the past to see how they do in the future. Most of my questions, therefore, start with "Tell me about a time when you..."

"Tell me about a time when you dealt with a particularly difficult customer."

The trick to this is to keep focusing the candidate on times when they did this. It is very common to get a "Well, I would do this" type response. This doesn't help me, as they are trying to tell me what I want to hear. I'll usually counter with a question along the lines of "Surely in your retail job you must have had one really challenging customer that sticks out in your memory?" Usually this is enough to get the candidate talking. If they still can't get it right after a couple of prompts, I note that they lack attention to detail.

"Tell me about a time when you went over and above the call of duty".

People love this question, as it gives them the ability to toot their own horn. It's funny that I rarely have any issue getting people to give me a real world example here. 😉 They're definitely not so fond of this next question though...

"Tell me about a time when you didn't put in all the effort you should have".

People are human. They have good days, and they have bad days. And no one is above it. I have had candidates tell me that they've never given a sub-standard effort. (Yeah, right.) If I'm feeling particularly benevolent, I'll even give them an example of when I might not have. (Worked a lot of OT the previous night, really should have got a report out, but just didn't feel up to it.) Something to get them talking. You would honestly not believe the stuff that has come out of this question. I've discovered many (very serious) reasons to avoid hiring someone from this very question. It is amazing what people will tell you. Another good one:

"Tell me about a time where you intentionally violated a corporate procedure, and why".

How's this for you... a guy squirreled money out of the chequing account into a savings account. The reason was that the boss liked to spend like crazy, and would frequently overdraw the account, meaning that they ran into problems with bounced payroll cheques. He made certain that the money was there to pay the employees. Benevolent, yes. Deceitful, yes. I'll leave it up to you if that should be a deal breaker on the hire. The point is that you would not ever learn this without asking the hard questions.

I'm not saying that you should have a counter question for each you ask, but one or two, particularly where you know you're going to get the glowing answers, can be quite helpful. It's partly these kind of questions that really garners the respect of the interviewee, as well. No one ever asks those questions, in my experience.

What else to look for

I give every candidate a chance to ask questions at the end. I always appreciate it when they take the time to do so, as it shows that they are curious about our place. I do, however, watch for questions that show an obvious lack of preparation on the part of the candidate. Asking us what we do, for example, is not cool. On the other hand, if they tell us they've seen x, y and z on our website, and are looking for clarification, that's great.

It's amazing to me how many candidates don't ask any questions, though, even when given the chance. I've always been of the opinion that the interview is a two way street. As much as the company is interviewing the candidate, the opposite should also be true. How else will the candidate know that they actually WANT to work there? We spend a lot of time at work, so it is important that we be both happy and challenged in whatever job we take.

Interview Closing

I always close the interview with the following:

"Thank you for your time. We have a few more candidates to interview, and will be making our decision once those interviews are complete. If you are the successful candidate, we'll be in touch."

It doesn't matter if they are the last candidate or the first. It gives you the time to sit back, reflect and a chance to talk about the candidate with your co-interviewer. Remember how I said I always interview with another person? The two biggest reasons for this (IMO) are:

  • If there is every a discrimination case, you have a person in the interview to back you up on what was said;
  • You get a second set of eyes and ears to help evaluate the candidate.

The last point is the bigger one to me, but the first could prove to be important at some point. (I hope not, but prepare for it just in case.)

Oh, and by the way... regarding the "more candidates to interview"... no one I've interviewed has ever minded that I've called them before they got home to offer them the job. 😉

Things NOT to say on your resume cover letter

Over the past couple of weeks, I've been collecting resumes for a Senior Accountant at Fairwinds. This person is going to handle a bunch of the accounting work that I used to do in my previous position, allowing me to free up some time to focus on higher level accounting tasks, supporting and directing the IT, and strategic planning and measure development. I'm really looking forward to getting someone on staff to help out, as I've done nothing but wrack up extra hours since September when I was promoted. There are a variety of reasons why we haven't brought someone on staff over the past few months, which I can't discuss, but we're now at the point were I have to get this done.

As is always the case when receiving resumes, I've picked up some doosies. This time around, I actually ended up with very few under-qualified candidates, (unusual that,) and about a half dozen who look like they actually might fit the bill.

Naturally, some stick out. And while I'm aware that this is important, some stick out for the wrong reasons. So for anyone who is job hunting, here's some tips based on cover letters that I really did receive:

  • Send your resume in a generally accepted format. (Hint, Microsoft Works is NOT a generally accepted format!) The most common I've seen are Word (.doc), PDF or just in the body of the email.
  • When I email you to say that your resume did not come through in a readable format, don't send it back with the (entire) message "Chow for now". First off, Ciao is not the action of eating. Secondly, when applying for an accounting position, (or any other position, IMO,) this is not acceptable use of language. Try being professional about this. I'd suggest: "I'm sorry the attachment didn't come through, and have attached a new copy for your review. I look forward to discussing it with you in more detail."
  • Don't tell me you have a hot wife. I really don't care.
  • Don't tell me that you have a swimming pool. I really don't care.
  • Don't tell me that you are in perfect physical condition. I really don't care, and I also don't believe you.
  • Don't tell me that you you want to work seven days per week. That's not healthy, and is actually suspicious. When auditing, we actually make sure that people actually take vacation time, as this means that someone else has to cover their job while they are gone. This can show where fraud is taking place, as the perpetrator is not there to continue covering it up.
  • Don't tell me you are a millionaire. I really don't care, and don't believe you. (I also make it a policy to hire people who actually need their job.)
  • Don't send me a cover letter that says your career aspiration is to work for another company. I want to hire someone who wants to be here, not someone who wants to be somewhere else.
  • Know how the online resume tools you use actually work. If you post your resume in a job search engine, give me your CAREER aspirations. It is quite possible that the company you want to work for won't pick up on your resume, and the agency may just email it to me. (Then see above.)
  • Don't tell me that you are a 10 out of 10 in any software application. You're not. And if you're careless enough to say it about Excel, I'll teach you that you're not when you're in the interview. (Nicely, but I will.)
  • Don't send me your resume unless you spell check your cover letter AND resume. If you can't be bothered to do this, I can't be bothered to hire you. (Accounting is about attention to detail... hello?!?)
  • Don't send me your resume from your work email address. If you'll do it to them, you'll do it to me.
  • Gmail, Yahoo, Hotmail and many other carriers offer free email accounts. Get one, and for crying out loud, make it professional! I don't want email from!

I also have a rule of 3 pages for an application.

  • Every resume MUST have a cover letter.
    • This is your only chance to actually tell me anything about yourself, and I like to know how you write.
    • By the same token, however, I'm busy, and don't have time for an essay. You get one page to "hook" me, and make me want to look at your resume.
  • I stop reading after 2 pages of your resume.
    • If your resume is more than two pages long, then start cutting the irrelevant work experience. I really don't care that you painted fences while in high school 15 years ago. If you preface it with "Relevant Experience", I'm happy, and I'll get you to fill in the gaps in the interview.
    • Consider creating a "skills resume" that highlights what you do, rather than where you did it. You need to be careful with this, however, as I'm very keen on knowing the where as well.

I'm curious... what things have you seen on a cover letter or resume that should just not have been there?

Things I want to see in the next Outlook version

Now that we've completed our systems migration, I'm actually using Outlook 2007 on a daily basis. Previously, we used Novell Groupwise at work, and I'm also a huge consumer of gmail for my personal stuff.

I don't mind Outlook 2007 overall, although I've heard some complaints that there are too many steps to get to each thing. Most of it is that people are trying to get used to the new UI, but I'd agree that it could be more efficient in certain areas.

Things I do like about Outlook 2007:

  • It has a softer feel than Groupwise 6.5
  • I can code against the object model (Okay, I'm a geek, but we knew that)
  • The calendar has a neat feature that, when shared, overlays others appointments against your own, so you can see everything that is going on.

Things that I think are sorely lacking

  • In Groupwise you could set up rules to file email once it had been marked read. In Outlook, even in 2007, you cannot do this. We can set up rules to file it when it comes in the door, but not after the email is read. Come on Microsoft! I don't want my email filed until I've had a chance to see it, or I'll miss it. This is WAY overdue!
  • Filing in folder vs labels. Microsoft needs to take a page from gmail and get this into the next version. Filing in folders is soooo 1997! I want to be able to label each email with MULTIPLE labels. None of this filing an email in one folder. I want to be able to tag it with each person's name, and maybe even a project description. As it is, I file based on the original sender, which means I'm pretty much restricted to using the search feature and waiting for it. Gmail is incredibly powerful in this regard, as I don't need to remember the original sender, just one of the participants in the thread, and I can find the entire email conversation. Ultimately, I'd like to combine this with rules, automatically applying rules to label the email when it arrives, (based on sender and/or subject) and having it clear out of my inbox once it's read.

The thing I'm still trying to figure out, that I'm sure is possible...

  • I'm still trying to figure out how to get all my contacts to file, and flow into email, by LAST name. By default, I have to enter the person's first name to get the email prompting to work. This simply isn't the way I work. I know it can be done, but haven't had time to fight it through yet.

I'm sure I'll have more as I go along. As it is, I've started publishing short articles to our staff on how to work with Outlook 2007, which I'm reproducing in the Outlook General Tips section of my website.