The Three C’s Of Interviewing

A client of mine recently asked me to help fill a junior-level position in their organization. This isn’t uncommon; I regularly help clients interview and select qualified IT Professionals to join their ranks.

Usually I’m usually given a detailed job description with very specific requirements. The manager frequently believes that the requirements for the position are very unique, very specific to the organization.

Sometimes this is true; often it is not.

As a result of this perceived uniqueness of the position, many hiring managers mistakenly settle for the first person that meets their minimum requirements. Sometimes, they even settle for less than their stated minimum.

This is unfortunate. It is a disservice to their organization, to the ill-fitting candidate that’s hired, and to the other candidates who would have been a better fit in the organization. The organization has to suffer through a lackluster performer. The person hired is put into a role where he has little chance for success. And other, potentially really qualified, candidates loose out on a great opportunity.

Past Performance Is No Guarantee Of Future Success

When I interview candidates for a position, I ask questions that help me to gauge their likelihood for success. Predicting success is not easy; it’s a difficult undertaking. But trying is important for the obvious reasons.

Much has been written about interviewing techniques and asking good questions so I won’t go into a lot of details on this subject.

I will say, however, that I like scenario-based questions. These kinds of questions reveal quite a bit about how a person approaches his job.

What are some scenario-based questions?

  • “Tell me about a time when you and the development team didn’t see eye to eye on an issue and how you handled it.”
  • “Describe a time when the budget you were given was far less than needed and how you adapted to the new limitations.”
  • Think back to a time when one of your projects was at risk of missing a deadline. How did you approach the problem and what did you do?

Although these kinds of questions will not guarantee that you’ll find the rose among thorns, they do offer some insight into the candidate’s experience and outlook.

What To Look For When Interviewing A Candidate

As I interview candidates, I’m look for what I call The Three C’s of Interviewing. Before I recommend a candidate for hire, I want to make sure that both the client and I are comfortable in the following three areas.

  • Competency. Does the candidate have a good base onto which to build? No one is likely to meet every single requirement. And even if he did, he’d still have to learn the specifics of this environment. So it’s important that he has a good foundation on which to build, that he can learn quickly, and that he sees opportunities not obstacles.
  • Compatibility. Will the person be a good fit with organization? Can he get along with the others? Perhaps the role requires a significant amount of individual work without the input of others. Can he work alone? Or can he function as a member of a larger team if required?
  • Core Values. Is the person trustworthy? Does he have a good work ethic? Do I believe that he will take ownership of issues? Will he work hard? Is he a go-getter, or does he lack initiative? Can I trust that he can and will do what he says that he’ll do?

These are the qualities that I look for in a candidate. Yes, experience with specific tools and technologies is important. But don’t overlook the the intangibles of the Three C’s.

Question: What do you look for when you interview candidates for an open position in your organization?

Related Posts

About these ads

22 Responses to The Three C’s Of Interviewing

  1. Mike Walsh says:

    Good post, Joe.

    I just included a thought on this in a post I put up for SQL University’s DBA week last week. Then I just saw a comment on Jes Borland’s SQL U blog post that made me think of this (her post: http://blogs.lessthandot.com/index.php/DataMgmt/DBProgramming/MSSQLServer/sql-university-women-in-technology) and my comment there answers your question :-)

    But in a nutshell – For me the 3 C’s are almost always more important depending on what role I am trying to help fill when interviewing. Especially that first C. If there is time to train and work with someone, I’d rather have someone capable of learning who has a solid grasp of common sense and can apply logic to problems but not so much experience in a technology than someone with all the experience in the world who I couldn’t work with or couldn’t apply logic to solve simple problems.

    Great post. Lots too take out of there the next time I help interview a candidate.

    • Joe says:

      Thanks for the link to Jes’ post, Mike. Great words from her there.

      A teachable spirit is critical in my opinion. Without it, learning is tough.

      Thanks!

      Joe

  2. D says:

    I’m on the other side of this equation, having been interviewed twice so far this year, and hoping for more. Both interviews were more technical requirements interviews, and it wasn’t until I was asked if I had questions that issues like training and compatibility came up. Seems as if people out there could learn from you!

    • Joe says:

      Thanks D!

      The same issue tends to raise its head when someone gets promoted. He is promoted for his technical astuteness, but that’s a vastly different set of skills than those required to succeed as a manager. I’ve written about that in a series called “I got promoted, now what?”

  3. John Sansom says:

    Great post Joe.

    I particularly like your take on the employers perspective of their role being unique, special and requiring a very niche type of person. Rarely is this actually the case and it makes for a very interesting point because it’s not one that is given sufficient consideration in the process of recruitment in my opinion.

    The scenario of an employer “settling” for a “good enough” candidate is also disappointingly common I fear. I wonder if this is perhaps as a consequence of employers often needing to source a new employee quickly?

    I’m a believer that employers should maintain close ties to their relevant technology communities so that they already know who they would “love” to have on their team when the time comes. Wishful thinking perhaps?

    • Joe says:

      I actually see this quite a bit, John. Many companies view their roles, processes, etc., as being very unique to them. Many times they are not really that unique at all.

      Your last paragraph is right on. Employers should “build their bench” as some say. Go ahead and identify some folks that you’d like to have on your team when the need arises.

  4. Pingback: Dew Drop – March 8, 2011 | Alvin Ashcraft's Morning Dew

  5. Pingback: Weekly Link Post 185 « Rhonda Tipton's WebLog

  6. Pingback: Interviewing like a Pro: Tips for first time interviewers

  7. This iss my first time go to see at here and i am genuinely impressed to read all at one place.

  8. Pingback: scrapbooking online stores australia

  9. Pingback: girls clothing size conversion charts

  10. Pingback: this article

  11. Pingback: cheap one direction one direction t shirts in dubai

  12. Pingback: jessops promo codes

  13. Pingback: travel plans english to japanese dictionary

  14. Pingback: website link

  15. Pingback: click the up coming webpage

  16. Pingback: Yovonnda

  17. Pingback: mouse click the up coming webpage

  18. Pingback: company website

  19. Pingback: itisd.com

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 36 other followers