Skip to main content

Hiring: Scheduling Interviews

Interviewing candidates is never easy. There's a lot at stake. Many notable managers and companies will bloviate about their hiring processes; often in self aggrandizement but occasionally to share tidbits of wisdom.

A successful hiring process requires that a lot of pieces be firmly in place. Corporate messaging. Job descriptions. Salary ranges. Benefits packages. Application process. Referral programs. The list goes on...

One very important yet often overlooked item is scheduling, and that is the focus of this post.

While interviewing a candidate recently, I was doing my routine pre-interview preparation and reviewed with whom and when the candidate had already spoken. To my confused dismay, I learned that the candidate had spoken to 5 people already on three separate days. I was to be the 6th interviewer (on day #4), and there was still one more interviewer scheduled for later that week. That's 5 distinct interview periods!!!



After conducting the interview, I immediately reached out to our head of HR and voiced my concerns. Fortunately, he was very receptive and our conversation was productive.

I realize that it can be difficult sometimes to coordinate schedules of multiple interviewers. This can be compounded when there are micro-managers involved who insist on interviewing every candidate even though they are 2-3 levels removed (tip: if this is you, then it means you don't trust your managers, which is a big problem both for you and your managers).

Respect the candidate's time

It is entirely reasonable to have a multi-stage interview process. However, those stages should be few (no more than 3) and be explained to the candidate at the start of the process. Just because the candidate applied for your position doesn't mean they are some kind of desperate hack who is at your scheduling mercy. A candidate deserves respect, and that respect carries through respect for their time and energy. The candidate likely has to take time away from work, family, or other obligations to meet with you.

Be efficient

Don't drag out the process longer than it needs to be. Determine go/no-go breakpoints and follow-up quickly. If a candidate is a no-go, flag that quickly so that you and your team (and the candidate) can move on. If the candidate is a go, get the secondary/final round together ASAP so that you can maintain momentum and not lose the candidate to another company. The longer you drag out the process, the more likely the candidate will find another job or lose interest in your company.

Have a structure

Different roles call for different interview processes. If you're hiring for an SVP of sales at a Fortune 500 company, that process is likely to be different than if you're hiring for a junior developer at a company with 60 employees. Regardless, you should have a process in place for most positions that hiring managers follow. For example:

  • Interview 1: Phone Screen with HR/Recruiter
  • Interview 2 (within the following week of Interview 1): Phone/video interviews with hiring manager & 1-2 other team members
  • Interview 3: (within the following week of Interview 2): In-person final round with remaining interviewers

In less than 3 weeks, you've reached a decision. If you're a startup, this may be even more compressed. Either way, you don't want to drag it out. Also, you want to set expectations with the candidate about the process; this speaks volumes to their perception of you as an organization (remember: the interview goes both ways!).

Be courteous

If you decide not to move forward with a candidate, tell them. Many companies and hiring managers neglect this and just assume that no response is a fair response. Wrong. As a hiring manager or in-house recruiter, you represent your organization. What kind of message does that send to a candidate when you don't even bother to follow-up? Perhaps you don't care about such things. Well there are companies and people that do; they have voices, and those voices matter.

Take it seriously

Do I really need to say this? A quality hire is worth so much more than your schedule for the week. If you're hiring to fill a position, the hiring for that role has to be prioritized by both you and your team of interviewers. If the interviewers aren't willing or able to make time for the interview, then they shouldn't be part of the process. If you aren't willing to orchestrate a timely and efficient process for hiring, then perhaps you should ask yourself: "Do I really need to fill this role?"

After all, if you don't take the process seriously, why should a candidate take you or your organization seriously?


Comments

Popular posts from this blog

Improving Win Rates

Still here at the Gartner Local Briefing. In a session with Richard Fouts about customer win rates. Sharing Win/Loss Data Sales teams tend to advertise their wins, yet contain their losses. Why is this so? Q:  How many global IT companies conduct win/loss on an enterprise scale? Less than 5%? About 10%? About 20%? A: Less than 5% Why? CEOs and Sales people say "I know why we win/lose".  Some politics are touchy; people don't want you to expose what they did well/not (especially in competitive environments).  "I clicked the won/loss checkbox in Salesforce.com" One company evaluated their win/loss data. They looked at 140 wins, and 55 losses. Looking at this data, they noticed a correlation between the wins and the fact that they beat their competition to market with compelling announcements in over a third of the scenarios. An IT services firm attempted to sell a more sophisticated solution. Upon evaluation of the win/loss data, they fo

Luck Is Not The Answer

As the 2011 season of the National Football League approaches, so does the rabid anticipation of its parasitic counterpart; fantasy football. Anyone who knows me knows that I love football (not fĂștbol); particularly the NFL . I grew up a dedicated Patriots fan and have since become more of a fan of the game itself rather than just a New England loyalist. I tend to keep up with NFL news throughout the year, and regularly download the Rich Eisen Podcast for listening during my morning commute. Rich's guest on the most recent episode was Michael Fabiano, the resident fantasy football expert at NFL.com. At one point during the podcast, Rich and Mike were exchanging viewpoints on what constitutes being an expert and how no matter how much of an expert you are, you need to be lucky to win a fantasy league. A similar sentiment was expressed during a 2010 podcast by one of the guests (I forget whom); that it's all luck and you can't really predict anything. I take exception t

Product Parenthood

It has been a long time since I've been able to sit down and write a lucid blog post.  This one will not be one of them. I've come to realize that my full-time job as a Product Manager, my other full-time job as a husband, and my newest (and most demanding) full-time job as a parent (to a delightful son) consume roughly 100% of my time; leaving precious few moments in the day in which to gather and synthesize my thoughts.  Thus, I've been using Twitter more often and blogging less. " Blogging less?  What?  You only have 3 prior entries! " I used to blog quite a bit under a different moniker.  However, as a parent, I have come to the realization that composing longer, thoughtful essays are a luxury that I generally cannot afford. With that, I've added my Twitter feed to the left, and will make an effort to write "larger-than-micro" blogs here on at least a weekly basis, if not more frequently. And now it's back to full-time job #1, follo