Ask Slashdot: Why Are Tech Job Requirements So Specific?
First time accepted submitter hurwak-feg writes "I am in the market for a new IT (software development or systems administration) job for the first time and several years and noticed that many postings have very specific requirements (i.e. specific models of hardware, specific software versions). I don't understand this. I like working with people that have experience with technologies that I don't because what they are familiar with might be a better solution for a problem than what I am familiar with. Am I missing something or are employers making it more difficult for themselves and job seekers by rejecting otherwise qualified candidates that don't meet a very specific mold. Is there a good reason for being extremely specific in job requirements that I am just not seeing?"
I'm under the impression that the more specific a tech job requirement is, the more likely it was written to target one person, such as a specific foreign citizen on an H-1B visa. That or the company just wants to be a cheapskate, wanting the new hire to be productive from day two instead of taking two weeks to train him or her.
The problem is, there are a lot of candidates out there now. A LOT. So we get real specific with what we want, because we still end up getting between five to ten applicants that have those things and thirty to forty who have almost all of them. If we were vague, we would receive probably between 100 and 200 applicants per job. And we're in an area that is NOT tech haveny. We're in the middle of the deep south.
I remember a friend from google telling me they receive , on the average year, around 195,000 candidates, 30% of which make it to an interview phase. That number doubles every year and a half. By being way more specific , they are slicing that number in half. Or more. Instead of ALL the google employees having to interview 50000 (which doesn't count second or third or onsites that also occur), they're trying to do far less.
Employers are facing a glut of software engineers/IT/etc. We're just knocking the numbers down to reasonable levels with these extra requirements. It'd probably be in your interest to go ahead and apply if you're close to all.. but rest assured, if you see an advert for a job that contains a lot of requirements, they will probably get 5 - 10 applicants that meet those around here.. and 300 - 400 in a more tech heavy area like the bay area.
This is pretty well documented. In America if you want to hire someone for a tech job on a work Visa by law you have to "prove" there is no American capable of doing the job. The easiest way to do this is to have very, very specific requirements. There are law firms that teach companies how to do this without breaking the law, and the gov't is pretty much complicit in this (thanks to 30 years of non stop attacks on perceived 'Bureaucracies' brought on by people that don't like the DMV). Compounding this you have schools in India and China that exist to rubber stamp people with any qualification needed.
It mostly works because the vast majority of tech workers aren't MIT graduate rock stars but rank and file workers. There's nothing wrong with that, but it means you're easily interchangeable. But us tech workers also have big, big egos, so we're convinced that Unions and lobbying to protect your interests is for losers who just couldn't hack it (and if they lose their jobs and end up a Walmart they blame themselves anyway...).
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
My own job is programming Moodle, an LMS with over a million lines of code. That's roughly equal to an entire Linux distribution.
What are you smoking? Just the linux *kernel* is roughly 12 million lines of code. Firefox is 10 million lines of code. The GNOME desktop framework is 8 million lines of code. The GNU compiler is 6 million lines of code. Chromium is 7 million lines of code.
That's just a smattering of the packages that can be found in a linux distribution...