- 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
November 07, 2006 | Comments: (0)
Handling interview challenges
Dear Bob ...
I had a phone interview with an HR screener a few months ago. She said: it's been a while since you've worked for a large company - I don't think you can do that any more. She went on to say that the five staff members have been working for large companies for the past five years. I'm not the kind to raise my voice, but I DID ask: What is it that you think I'm lacking when it comes to working for a large company?
She got 'REAL' defensive at that point: "I don't have to explain myself to you..." Well, needless to say I don't think I backtracked very well out of that one!
No to be fair to these employers, all I have is several years of experience (I leave off the military stuff so I don't see TOO experienced (
How do you think I should have handled the comment?
- HR-challenged
Dear Challenged ...
You describe an interview situation that comes up over and over again - the interviewer assuming a disqualifier. I don't know why they do this. I think an inference about it is reasonable: They wouldn't be talking with you if they really thought the issue was a deal-breaker, so they must be raising it to see how you'll respond.
So here's how you respond. In general, do your best to anticipate what they're likely to be. Most ad libs are rehearsed, after all - they aren't spontaneous acts of brilliance. If you are caught off-guard, memorize this phrase: "I get that a lot. I don't really think it's an issue, though. Here's why:" That gets you going in the right direction without putting either of you on the defensive.
So: "I get that a lot. I don't really think it's an issue, though. Here's why: I don't put my years in the military on my resume, because it would add a lot of length without adding a lot of value. As I think you know, the military is a pretty big organization, and I did pretty well there. I also worked in a couple of big companies before starting to work in smaller ones, and what I discovered is that most big companies act just like a collection of small ones. Either way it's about managing the right relationships, and that's something I've focused on throughout my career."
If that explanation doesn't fit your experience, figure out another one that does. Whatever it is, also remember the first rule of handling disqualifying questions: Answer them as briefly as possible, and then redirect the conversation to a qualifying subject. So here, you might finish by asking a question of your own that points things in the right direction. For example: "Not all big organizations are the same, and I'm guessing you had something specific in mind about your company when you raised the point. What, in particular, do you see as the biggest organizational challenges associated with this position?"
And in case you didn't recognize the phrase, "organizational challenges" is a nice euphemism for "political landmines."
- Bob
Posted by Bob Lewis on November 7, 2006 04:38 AM
RATE THIS ARTICLE:
-

- COMMENTS
This is the sort of interviewing technique that has bothered me for quite some time. It's all a matter of attitude. By the time someone reaches the interview stage, the elimination screening should have been done. At that point, when I'm interviewing someone my philosophy is to look for reasons to hire him (or her). My experience is that people don't need to be tricked into eliminating themselves; they do a good enough job of that without any help!
Posted by: Dave at November 8, 2006 01:34 PMExcellent advice in response to a pre-conceived disqualifer. As a "worker bee" who participates in group interviews of potential teammates, I've always held military experience in high regard. This is especially true in judging whether a person will be able to be effective in a giant corporate machine and its associated culture of adherence to policy, procedure, and understanding chain of command. An HR screener might appreciate military experience even MORE than an MBA. (I mean, how many HR screeners hold MBA's?)
Posted by: Stan at November 8, 2006 02:38 PMI think its somewhat sad that the art of interviewing has devolved so low.
Rather than being able to demonstrate a body of work, prove you can get along well with others, and illustrate how you can add value to the organization, more focus is placed upon "who can answer the trick questions." It's almost like the HR gurus were inspired by Monty Python's Holy Grail where the knights were asked their favorite color before crossing the bridge.
There's a phrase "you are what you measure." Meaning, if you place a lot of emphasis on measuring efficiency, odds are that the company has grown to be highly efficient. So if your HR decision making is based on answering trick questions, then most likely you hired the best trick question answerer, and less likely the best candidate for the job.
Well then. How many perfectly qualified people get stopped at the HR level before the hiring manager ever talks to them? I know this has been covered over and over but the function of HR is to provide a different viewpoint of the candidate. They should not be the gatekeeper for technical positions.
Back in the day when I was a hiring manager all the resumes came to me. Unfiltered, unsorted, unvetted. I went through them and found the ones I felt were best suited. Then the team went through and voted for their top candidates. At that point I informed HR of who was getting interviewed.
The face-to-face interviews were myself, then the team, then HR. After all the interviews we all sat in a big circle and chose a candidate.
Did this take time? Yes. But what it got us was someone everyone agreed upon at the beginning.
Where was I going with this? Hiring should be a team endeavor if the person is going to be working with a team. Since the burden is going to fall on these people if the new hire doesn't work out they deserve the respect of having a say in who is going to be joining their team.
Posted by: Marie at November 13, 2006 07:35 AMSeveral years ago my employer (a state government agency) shifted to a concept called 'Competency Based Interviewing'. It's strength is that it requires to interviewer to, up front, decide what is key to know and to frame 3 to 5 basic questions around them. The interviewee is then asked to "tell a story" about how their past work experience covers the question asked. The advantage with this concept is it focuses the interviewee on describing how she/he fits the job and keeps the interview on a postive note rather than on a "what can I use to reject this person" approach.
Posted by: Glenn at November 16, 2006 07:39 AM|
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

- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization

- Is your smaller organization ready for High Availability?
- Is system maintenance doing more harm than good?
- Virtual Test Lab Automation: Manage development infrastructure





