- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
May 06, 2007 | Comments: (0)
Interviewing techniques
Dear Bob ...
What do you think about behavioral interviewing? That's where they ask you to tell a story about the time you led development of a new marketing strategy, instead of asking how you might do it in the future.
I've always though behavioral interviewing rewards people who are good story tellers. Whether the stories are true, or not.
- Recruiting
Dear Recruiting ...
I've used behavioral interviewing. It seems to work pretty well, so long as the interviewer probes a bit. But maybe I'm peculiar. I figure that if an interviewee can make it up well enough, he/she knows how to handle the situation. Besides, there aren't that many people whose story-telling can survive a probe into the details.
I do, however, generally prefer to ask people to "do the job in the interview" (to use Nick Corcodilos' phrase). It isn't all that different when it comes to the actual conversation, except that the situations you ask about are neither hypothetical nor historical - they're what you're actually facing. Either way you have to probe to the details to make sure you aren't getting a story that only looks good in the PowerPoint, as it were.
In fact, it occurs to me that no matter what your interviewing technique, success depends more on your ability to drill into the details. Usually that means you shouldn't be the only interviewer - especially if you're hiring a position where you aren't the expert.
It's a simple principle: If you don't know enough about a subject to know what success looks like firsthand, you're unlikely to be able to recognize which candidate will be most likely to succeed.
- Bob
Powered by ScribeFire.
Posted by Bob Lewis on May 6, 2007 09:31 AM
RATE THIS ARTICLE:
-

- COMMENTS
Sound advice from Dr. Bob.
Among styles, would advise not using the "hostile interview." A few years ago I was on an interview that I could only describe as akin to a police interrogation (at least the TV version, fortunately never had the real thing...).
After being shocked by the experience, I read up on the tactic. Some places use it to see how people react to pressure or uncomfortable situations.
However, my reaction is that this tactic overlooks that that the canidate is also evaluating the company and the people with whom he/she would be working. Needless to say, the hostile interviewer made a poor impression with me. And since there's no way to know if this is the interviewer's normal personality or just a "interview tactic" -- I hedged my bets and later withdrew my name. This likely wasn't the kind of person with whom I'd want to work.
As Dr. Bob mentioned, there's ways to probe answers within behavioral interviewing without resorting to hostile interviewing. And compared to other styles, I think behavioral interviewing can yield the best results. After all, when you're describing a problem or offering a solution at work, isn't it usually in a story-like format?
Posted by: Mike at May 9, 2007 11:43 AMI find it most effective to combine the two: behavioral with "do the job in the interview". Ask the "tell me about a time when.." question, and then communicate a current challenge and ask how the candidate would handle it. This should tell you if the candidate learned anything from the previous experience, and also if he or she is going to be able to solve your problem. Bob's right though - the devil is in the details.
Posted by: Sara at May 9, 2007 12:30 PMAs an HR person for IT, who's used behavioral or competency interviewing for a decade, I concur with your statements about the importance of probing and the difficulty of a story teller standing up to the probing. Many experienced people know what they ought to do in certain situations; but when actually in a situation, for any number of reasons, they don't do that. Even a non-technical person can do pick up on some red flags - such as a person who tells a story with only 'I' (or never says 'I'); or a person who blames things on his boss/colleagues/the customer etc. More often than not, a person gets going on telling a story, and they reveal more than they realize. (And the person who can't tell a story - every bit has to be painfully drawn out - is also telling you a good deal!)
Posted by: Allison at May 9, 2007 06:14 PM|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
ADDITIONAL RESOURCES

- Do you have the power to resolve technical issues with one call?
- Take control of your content- leverage Microsoft SharePoint
- Keeping the E-Mail Flowing

- SGI Adaptive Data Warehouse: Building a High-End Oracle Data Warehouse
- Five Steps to Secure Outsourced Application Development
- Global Shared Memory: Performance and Productivity Breakthroughs





