Merc said:
How many people who live within a half hour of Merrillville, Indiana can claim any experience at all with the SBT Accounting system, let alone have a year's experience with their manufacturing-specific add-ons?
I'll bet money on this answer:
one
Some — not all — of those weirdo ultra-specific requirements are undoubtedly there as a way to ensure that the "right" person gets the job.
Most organisations of any size have a formal equal-opportunity policy. They are required to interview and hire on a strict is-this-person-the-best-person-for-the-job basis, and, more importantly, to be able to
demonstrate that this is what they did in any particular case. If there are questions after the event, they can
prove that everything was above board and honest. No back-room deals, no favouritism, everything for the good of the organisation.
Why should there be questions? I'll give you three scenarios.
* Harry gets hired. Mary thinks she should have got the job. Mary's scumbag lawyer sues.
* Harry gets hired. Harry happens to be the purchasing manager's son-in-law. A very senior manager wonders if his staff are feeding at the trough instead of hiring the very best candidates available.
* Harry gets hired. Harry turns out to be stealing stuff from the company, big-time. "No no" says the personel manager, "it wasn't just a gut-feeling judgement call I made, we decided what qualifications we needed and wrote them down (here is the list) and (as you can see) none of the other candidates were qualified. It wasn't
my fault!"
Doubtless you will be able to think of others.
Here is how it works. They want to give the job to Jason. (Doesn't matter why: maybe because Jason is somebody's brother, maybe because he has done contract work for them and they already know he's very good, could be a million reasons.) But you can't just give someone a job these days, you have to go through all the paperwork bullshit. So there is a problem. How do you follow formal proceedure (as all organisations have to do these days) and
also give the job to the person you actually want? (All organisations do this too, they just never admit to it.)
Simple: you sit down and decide that you need a programmer. Hmmm ... you need him/her to be experienced. OK, 5 years of programming. (It just so happens that Jason has been programming for 5 years and 8 months.) Hey, we don't want some out-of-towner that won't stick around. OK, put down lives within ... oh ... a half hour of here? (Jason lives 20 minutes away.) Hey, we need someone who knows the SBT Accounting system, right? Sure thing, and we better put down about knowing the add-ons too.
Before you know it, you have a perfectly logical and rational set of key requirements, and
only one person fits them.
Welcome to the real world, Jason.