So if I want to hire MMA fighters for a programming job (or give them bonus points, at least), I can do so. If someone doesn't want to hire me because I'm a former academic or because I stickfight, they also can.
[1] You can also get into trouble if systematic hiring criteria have a "disparate impact" on a protected class. I.e., if you hire based on an intelligence test, and a non-asian minority group or sexual majority group statistically does less well on the test, you can also be sued.
You'd be implicitly selecting against gender, which is illegal.
There are girls active in MMA but it's not like it's 50/50.
And woe to you if you do not hire a female programmer that thinks she's more qualified for the job you posted than the guy you ended up hiring, especially if at first glance they're both equally qualified and the rest of your team is guys.
But it isn't the non-job relatedness of MMA that's the problem, it's the fact that the criteria harms a politically favored group.
You'd have to make sure that your pre-selection has a perfect representative split over all the minorities that could come after you in order to be able to get away with it if you made it public what your criteria were.
Good luck doing that, personally I believe that such trying to outsmart the system is something that will come back to haunt you.
Just take raganwalds post here, if someone felt they were passed over for an interview it would immediately be actionable, that is, it wouldn't be thrown out of court and so it could cost a pile of money even if in the end it turned out to be without merit. That blog posting, now seen by a few thousand people and cached in any number of places would suddenly be admissible evidence, and it would take a pretty good lawyer to negate the effect of that one silly document.
Ontario is particularly weird in that respect, I've got first hand knowledge of a pretty strange employer/employee lawsuit there that dragged on for years through appeals (in that case for wrongful termination but no less bizarre).
Best to not give cause in a climate like that.
Also, I rarely talk about specific criteria that I am currently using to filter people. This is because some people treat getting interviews as a game, and employ "SEO" to get interviews:
http://weblog.raganwald.com/2008/03/games-people-play.html
The least broken heuristics are the ones nobody knows you're using, IMO.
Where did I go wrong?
I never suggested that my practices are some sort of universal heuristic for every organization to use, nor did I suggest that other means of finding people were incorrect, or that other typs of people would not perform adequately or even better than the people I get to know.
I wouldn't call the post academic at all, but I would say that discussion about lawsuits is academic. FWIW, I try to avoid discrimination because it conflicts with my values, not because of the possibility of legal trouble. I'm a member of a visible minority myself, so I'm keenly interested in avoiding bias even if it is by accident.
As an employer, the bonus is that usually salary is based on /paid/ experience... so even though the two people in the example above have a /huge/ difference in actual time spent programming, as an employer, their starting wage is going to be pretty similar.
So, twice as much experience, for the same money? hell yes I'll choose the hobbyist. and as far as I can tell, there is no law against that. (though, I'm on pretty shaky ground if I require extra work after I hire you. See the semi-annual Electronic Arts lawsuits.)
That was the exact question the OP posted, the title is 'No, I Wouldn't Hire a Programmer That Has No Interest in Programming Outside of Business Hours', and framed like that it is illegal.
The way you frame it it is legal, relevant work experience, whether gathered inside or outside of work time before the employment commences is a good thing to pick up on that passion.
But given two applicants, one that has 20 years of experience during work time and none that he cares to report about during the interview outside of work time and one that has 10, 5 years working in his spare time and 5 years during employment which one would you pick ?
The latter has 'passion' according to the OP, the former is a clockwatcher.
The one that has completed projects on his own. If neither one of them could demonstrate such a thing, the one that seemed more intelligent.
Also, the difference between 10 years and 20 years of experience, I think, is less than the difference between, say, 5 years and 10 years... I think the wage curve would imply most people agree with me here. In the case of someone with 2.5 years of personal experience and 2.5 years of professional experience, vs. 5 years of professional experience, if all else were equal (which is to say, either neither has completed a project they can show me, or they both have, and they seem about as smart, and they are willing to work for the same wage) it's pretty much a toss-up in my mind. If the guy with 5 years work seems more professional, I might go with him, just 'cause I lack professionalism, and it can be really useful sometimes.
But, the thing is, it's usually not equal. the guy with 2.5 years paid experience and 2.5 years hobby experience, in my experience, is likely to work for only slightly more than someone with only 2.5 years of professional experience.
So, given the choice between hiring the person with 5 years paid experience at market rate for a person with 5 years paid experience, and the person with 2.5 years paid experience and 2.5 years hobby experience at the market rate for someone with 2.5 years of experience, I'll easily take the latter. (at least in my experience, pay goes up /fast/ in the early parts of your career.)
Why? I really don't believe that's true, at least in the US. This says nothing about requiring that they program outside of business hours. As long as they aren't putting any sort of demands on their non-work time, I don't see the problem in using someone's passion as a factor in hiring. There's only a problem if they place some demands on non-work time or fire you for it.
> [...] which one would you pick ?
Depends on the job. If constant learning of new tech is integral to the job, I might go for less experience. (Again, this doesn't imply not paying them for their time.)
I completely agree but I think the argument is that, all things being equal, someone that will do things related to their job in their free time will be better at the job and more likely to get better and better.
I can certainly see why someone would want to use it as a hiring factor but, like you said, once employed, it's none of their business.
The law is in my opinion totally just and I'm saying that as a former employer.