Re: It Skills Gap: What We've Got Here Is A Failure To Communicate
I have a lot to say on this topic. First, perhaps views from people on both sides of the interview table are bound to be biased - a hiring manager would never admit he discriminated against someone unfairly, and a job-seeker would rarely admit he didn't get a job due to his own failings. It's a topic we all have a personal stake in - as evidenced by the number and variety of passionate comments here. Dave mentions job descriptions written by non-IT people. I read lists of job requirements that look like cake recipes, yet, when you sit down at the interview table, the person you talk to is more interested in your approach to problem-solving, your adaptability, and your 'soft' (re: people) skills. They'll gladly work around a lack of experience with one type of API/hardware and bring you up to speed. But you often could never get to the interview table because you're off the list without that experience. How backwards!
On top of GAProgrammer's points, the salary issue is two-sided. They can pay more, or prune their requirement of the unnecessary and open the job up to legions of applicants (yes, even programmers) who would be overjoyed to take even less than the wage they're offering. If they've no problem accepting H-1B applicants as a cost-saving measure (not implying anything about H-1B holders), why not these people? I've noticed some employers finally putting 'degree or equivalent experience' in their listings, a nod to the alternative educational or entrepeneurial paths one can take to IT. There's a lack of clarity in bullet-point listings: for "1-5 years" of experience in a specialized subfield (say, "OpenStack" v "Cloud Computing"), is five years of the generic skill better than one year of the specialized one, or not? I think we all know a shakeup is needed here, but we likely won't see one for some time.