User Submitted!
530

Checking Technical Skills

Two Surefire ways to check technical skills of your candidates.

1) Check Technical references (Supervisors). 

The point of a reference is not, as is generally assumed, to find out ifyour candidate is a good guy or gal.  Only an idiot would give references of people who would not put in a good word for them.  Thus the reference check is useful in screening out idiots, but not so much for determining technical availability.

The key for determining skill lies in questions about the reference, not the candidate.  I interview the reference, trying to determine if they are technically apt, helpful, and willing to talk about specific situations that will match up with comments the candidate has made.  Asking if they work well with people is just a round about way of trying to get the reference to make a mistake and admit your candidate is a dud.  The far smarter way of approaching this is asking the reference how they helped the candidate learn, grow, and achieve.

After all, a reference should be a supervisor, and if the supervisor is a brilliant and patient teacher, chances are you've lucked out with a well-taught candidate.  If the supervisor is non-technical, but ran the department, where did the candidate go when they were stuck? 

Finally, if the conversation has gone well, don't forget to ask the reference for referrals, other references for the candidate, and even business or the possibility of the supervisor switching positions (not necessarily in that order).  A good reference check is business development, and as we all know, we're all responsible for business development.

2) The second way to check a technical reference is the "Tell Me" method.  Far too many recruiters like to hear themselves talk, so they don't give the candidate time to tell their story.  The Tell Me Method starts with a brief explanation of the company and the position, followed by the statement, "From the information I have given you, please tell me what you think the position is, how your skills apply, and why your technical expertise will convince your new boss to hire you.

This method is all about listening and giving the candidate the chance to shine.  Organized, disciplined minds respond well to this kind of questioning.  So do conceptual thinkers.  Both of those types of employees are valuable, and tend to ask more questions to clarify the position.  Poor performers, and the chronically discontent can't answer without giving themselves away.  They are looking to please you in order to get the job (deception and inertia are how they maintain their current jobs), so asking them to talk without clear direction will tell you all you need to know.

Picture taken from Dave at Dr. Fun's website.

Mon, 09/26/2005 - 6:06pm

Reference checking and "Tell Me" are enough ways but as a candidate you definetly add value/get noticed when you get CERTIFIED- It shows your commitment to your work/skill...Ofcourse as a recruiter just judging by certifications itself is not a good idea ..well.. but then again I do make exceptions for someone with certification like CCIE(with lab)..

-- from another certified (CIR)(wink)

Mon, 09/26/2005 - 6:26pm

I'll agree that Cisco certifications are well worth it - but how many of the others?

That's another post for another time - but certifications are worthy in my eyes only when the experience backs it up.

Way too many people don't get that, and then are surprised that I'm not willing to double their salary because they passed half of their MCSE exam.

David Douglass
Tue, 09/27/2005 - 3:54am

When you want to check somebody's technical skills don't ask nit-picking questions line "What's the third argument to the XYZ function?". Instead focus on higher level subjects such as "What is quality software?", "How is quality software produced?", and "Give me an example of a mistake that badly damaged a project, and what would have been a better course."

Don't accept trite answers. Drill down for real depth and understanding (or lack thereof).

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <font> <img> <span> <p> <br> <br/>
  • Lines and paragraphs break automatically.
More information about formatting options