The law is in my opinion totally just and I'm saying that as a former employer.
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.
First there are several jobs which require an ongoing education requirement (outside of work) in order to maintain the correct licensing for their fields. My mom's a nurse, my wife's a lawyer, both have ongoing education requirements. To take your bookkeeper examples, CPA's at least have Professional Education Requirements.
I consider programming outside the office part of a programmer's ongoing education. We may not need to be licensed but we do need to continue to keep up with technologies both in and outside our direct field of work. I'd be hesitant to hire anyone who doesn't keep up with what is going on in the environment around them. In my particular case the vast majority of technologies that I use now in my work I started working on outside of my direct work projects. Thats the nature of our industry.
And there's nothing illegal, in the US at least, about asking about activities outside of work and using that as a basis of hiring.
Just as a cab driver would be expected to have a valid driving license.
That's nothing to do with 'passion' outside of the job though, where a nurse would only be hired (or fired if she/he didn't) practice nursing in their free time, it's everything to do with the company being liable if they employed people that were not in the possession of a valid license to perform their jobs.
But I am allowed to ask questions that do not directly or indirectly adress illegal discrimination, and asking about profession-related activities is usually on-side.
That being said, it is perfectly legal for anyone to file a lawsuit suggesting that perfectly legal questions are being used to indirectly create illegal discriminatory practices. So if I never ask about religion but I only hire from my network which "happens to be" my church or my weekly Richard Dawkins Appreciation Society club...
What little I know about HR suggests that hiring out of a professional network that is agnostic about discriminatory matters is legal. HOWEVER, programming networks are on shaky ground. Not because of religion, but things like Ruby Conferences seem to under-represent certain protected classes of people like women.
Another example: If I put out a call for applicants on my own blog and that's the only source of applicants, am I discriminating against people who speak English competently for professional purposes but only read Hindi or Mandarin programming blogs? In ontario, that could be construed as illegal.
I can't give anyone legal advice, but if your network gives the appearance of discriminating against qualified candidates in protected classes, I suggest that it's good business sense to expand your network. It's a win-win: You'll get qualified people that other employers are ignoring, and your legal costs will go way down.
So... Good point about the title. And even though I am NOT saying that in an interview I refuse to hire someone who does not blog or go to conferences or tweet or whatever, my filtering mechanism could be breaking the law if it accidentally discriminates in a legal sense.
The problems really only start when you get larger though.
If you were to go over roughly 20 employees and you put out calls for applicants. Ontario is pretty bad in this respect actually (I still have an Ontario corporation, I probably ought to shut it down) I remember all the cautioning from our corporate lawyer there regarding interview questions. For instance 'how old are you?' is an illegal question, but 'are you over 18?' is ok.
Under 20 employees and when using non-public ways of reaching potential hires the situation changes a bit, but someone could still have a case if they felt that they should have gotten a job and you refused them for some imaginary reason. Being an employer in a litigious climate is pretty tricky.
Not necessarily, if you account for time wasted on pointless interviews. Some networks/channels are simply better, and a better network causes you to waste less time interviewing fools. My company has been hiring, and I've found that the candidates who contact me through HN are of a higher quality than those we've found via recruiters.
If you recruit from a lower quality pool, you need to spend more time filtering out the chaff. Maybe it's necessary to avoid lawsuits, but it's not necessarily a win-win.
It's a lot like driving: good drivers are fanatic about it. They are always itching to go for a drive and push their cars. If you wanted to hire a star driver, would you want want to hire someone passionate or someone who learned it on the job and gets by?
If you want your programmers to continue to be educated for the work that they do and for new technologies applicable to that work then you can provide them with courses during work time. If they do such stuff in their spare time it's great but that can never be a discriminating factor during the hiring process in anything but the most unofficial manner.
Anyway, you don't have to believe me, passion is great but you can't mandate it of an employee.
If you are looking for a co-founder that's a different story, but people that are employees do not fall in the same category.
1. The chances of discovering a potential employee are much higher if they are passionate about their field. Passionate people make a lot of noise. The OP acknowledges this.
2. I never said you should always higher passionate people. For example, some passionate people are unlikely to get things finished (they're more likely to be excellent at starting projects).
I agree with you about this being a rubbish (and potentially illegal) HR policy.
Companies in US are not allowed to discriminate based upon things like commute time, family situation at home, age, etc. - none of which factors into how well they can do the job once they are at work and on "company time" - and the argument that what someone does on their personal time falls into this category of judging someone based on factors beyond "Can the applicant perform this job?" is pretty easy to make.
So it's fine to look for passion - but people hiring and doing interviewing should be very cautious about what they say (and especially what they tell applicants) about how they are going to judge your level of passion, unless they want to open themselves up to potential discrimination suits (or so my possibly overly cautious corporate HR department would have us believe).
The difference is subtle, but the title suggests that it is the one whereas actually it is the other.
Think about it, if you actually did what the title says then you'd be open to legal action almost immediately.
Imagine an employer that would not hire a bookkeeper because they're not busy with bookkeeping in their free time.
I understand what the author is trying to say but the title is not really appropriate, the author has filtered out such applicants before the interview phase, so he does not hire them as a consequence of that.