My husband is a manager and hires Network Engineers. He looks at the resumes, but more importantly, during the interview process, he starts to ask direct, specific questions geared to what they claim their experience and knowledge to be.
He's had folks start to sweat profusely, or try to cover their answers by giving long rambling answers. I think that probably 3 out of 10 applicants actually have known what they claimed to know.
Guys like him are why it's not cost effective to lie on a resume. I've had too many brutal technical interviews to even think about it.
Yeah, but those other 7 of 10 are the same people who go on the Internet and complain how tough the job market is because everything has been outsourced to India and "American employers won't give American workers a chance".
I've always thought that "won't give American workers a chance" translates to "won't believe the lies on my resume". ;)
I've done interviews where this has happened. Fortunately, I didn't have the authority to hire because I genuinely felt sorry for some of them.
Now, if you really want to have the interview from hell, apply at Microsoft.
This is a method that is absolutely verboten in my organization. Every candidate has to be asked the same questions that were approved in advance by HR. While we are not hiring Network Engineers, it seems any effective process would be able to identify those that are qualified for the position as early as possible in the process.
The way we do it, a candidate may make it past the interview committee and not have the specifics of the resume investigated until references are checked.
Good. Anybody trying to get a position in IT by claiming knowledge they don't have are in the wrong profession.
To be honest I've been the guy on both sides of the desk (that hiring manager and the guy looking to be hired) and after you have accumulated a very broad range of products long rambling answers become the norm .... after 25 years working with all this crap I just can't explain some time it's like explaining how to ride a bike...and all the acronym be become a jumble...
Newbie and test out kiddies can talk the textbook all day and still have not clue on how it works let alone troubleshoot across multiples heterogeneous platform, protocols and layer's and include all the additional variables (environmental, human, etc.)in the mix
Your husband would have caught Gore when he said he invented the internet? I'd bet on it...
Doing much the same, I've actually had a candidate stop in the middle of an interview and say, "I just don't think this position is for me."
I have been to job interviews where I am asked about doing work that is not on my resume. I stumbled and then am shown the door. I get a little upset later because I wonder why they are asking questions that is not cover on the resume. Next time, I will just ask politely that since that is not on my resume why am I being asked about it.