That said, I was on an interview/selection committee last month and another this month. They are public sector positions, so they are points based and the candidates with a CCNA, Network+, recent Microsoft MCwhatever score higher.
There's a reason that the public sector and the east coast are so far behind, technically speaking. (No offense intended) The mentality is entirely wrong for the job. I recall a guy I interviewed a few years back (but less than ten!). He had a degree in IT or something similar who had no idea what I was talking about when I mentioned CIDR. I started re-wording, because I figure he'd know the concept by a different term, when he-I-swear-to-god said: "What? There's nothing smaller than a class C!"
I was floored. I still am.
Anyway, someone with a CCNA will know better, yes, but they may honestly be terrible at applying it, or actually understanding the concepts. Someone who's spent a few years working in the field will most likely know a whole lot more, but a good interview is really the only tool that will demonstrate the candidate's
actual knowledge and suitability for the job. I've sent many people home after about ten minutes of technical interview, and have weeded out innumerable candidates via phone screen. Seen lots of great resumes with nothing between the ears, and a lot of skinny resumes with amazing critical-thinking skills and the right mindset and attitude for the job.
My ideal candidate resume:
- has no degree, or has a degree in something that I think is really cool.
- has a work history that shows a history of active interest in the field in the form of personal projects, or contributions to open-source projects,
- has, ideally, a dynamic career in internet operations, but isn't required,
- has a keen interest in the job... loves what she does. Loves tech.
- has knowledge of technologies we use, or stuff that's fundamentally similar,
- has worked for companies I know. (This one is just a bonus, because I often know people who worked there at the same time who I can ask about person X)
My ideal candidate, when interviewed:
- Is sharp;
- Shows an intellectual curiosity about things they don't understand, or things they're revealed to not understand;
- Is capable of following a chain of logic and arriving at conclusions;
- When asked technical questions on what they claim to be their strongest knowledge domain, shows no fundamental weaknesses or flaws in understanding;
- Is capable of defending their correct answers, and
- Acknowledges that their wrong answers are actually wrong, when I show them how;
- Displays creativity, ingenuity, and, again, intellectual curiosity;
- Is interested in the problems that we want to solve, and
- Doesn't ever try to BS me!
Then I'll dig into the technical and infrastructural skills that define the role, to determine if they're a fit for the role... and then I'll let them interview me / us, so they can figure out if they'd enjoy the job.
I've had a really, really good record of hiring in tech. I've made entirely one real mistake in recommending a candidate, but we really needed a network guy, and he was a CCIE, with a PhD in biophysics. He didn't show any real sharpness, but I figured he had to be pretty sharp, given his background, and ascribed the problem to a language barrier.
He wasn't sharp.
-Fox