Re:The college-for-all model isn't working
by randomdata on Tuesday December 03, 2013 @03:31PM
(#6842968)
I'll admit, I had to look up what a cross join was, despite being quite familiar with the subject once I understood the terminology. I'm sure you apply much more rigour to your hiring process, but at the same time, it is difficult to know who is throwing out great candidates (I'm not suggesting I am one) over silly little things like this. How do we know if people are hard to find because people are actually hard to find, or people doing the hiring are terrible at their job?
Re:The college-for-all model isn't working
by tbrownaw on Tuesday December 03, 2013 @04:09PM
(#6843209)
How do we know if people are hard to find because people are actually hard to find, or people doing the hiring are terrible at their job?
Partly both, but also missing a qualified applicant often costs far less than making a bad hire.
The ratio of decent hires to bad hires needs to be as high as possible. In comparison, the percentage of qualified applicants thrown out almost doesn't matter (unless it gets to something truly absurd like 90%). (Really it does matter, just not compared to making bad hires. Interviews and delays are still expensive, just less so than failing to get new employees up to speed.)
Interviewers that make bad hires are terrible. Interviewers that turn away good hires are merely bad.
Software developers (supposedly) aren't stupid. Applicants for software development positions on the other hand...