Slashdot Mirror
Hiring Developers By Algorithm
Strudelkugel writes in with a story about how big data is being used to recruit workers. "When the e-mail came out of the blue last summer, offering a shot as a programmer at a San Francisco start-up, Jade Dominguez, 26, was living off credit card debt in a rental in South Pasadena, Calif., while he taught himself programming. He had been an average student in high school and hadn't bothered with college, but someone, somewhere out there in the cloud, thought that he might be brilliant, or at least a diamond in the rough. 'The traditional markers people use for hiring can be wrong, profoundly wrong,' says Vivienne Ming, the chief scientist at Gild since late last year. That someone was Luca Bonmassar. He had discovered Mr. Dominguez by using a technology that raises important questions about how people are recruited and hired, and whether great talent is being overlooked along the way."
Whoosh. I think the whole point is that having a phd isn't the best measure of anything. I've worked with phds and high school dropouts and I've never noticed any difference except that the dropouts are less entitled.
At my old job, we had a pretty revolutionary strategy for picking someone: We talked with them.
I've always done that too. Just get the interviewee to talk about their work, what was interesting about, the problems they encountered, etc. If a person doesn't know their stuff they won't be able to talk about it intelligently. Some people you have to coax out of their shell a bit, but that's it. If a person is reluctant I'll even ask them to pick something out of their resume to talk about instead of me suggesting a topic. I accept that most resumes have some exaggerations in them, so just let them pick something that isn't exaggerated. Also talk to them about the project they're being hired for, see what kind of questions or suggestions they have, etc.
It's purposely a low pressure technique. Some very good technical people don't do well being drilled about nonsense or brainteasers, or clam up if the interviewer starts playing Mr. Tough Guy and tries to trip them up on everything. Remember, you're trying to hire good technical people, not good interviewees. For other type of work this technique might suck.
It amazes me more companies haven't tried of this method.
Too simple and obvious - takes away the mystique of being a great interviewer. Also you've got to know your stuff to use the technique.
So, at my previous job (at a games company) I regularly worked 8.30 till 8 or 9pm. I'd get home at 10, eat, workout a little, then go to bed. I often worked full weekends (crunch time) and there was no way I could ever code outside of work, I was simply too burned out. In fact, I barely had time to do much else other than eat, sleep, and do chores. As such, if someone tried to find any open source work done by me, well, there is none, but that doesn't mean I can't program.
I kind of hate this recent assumption that all open-source programmers with work on github must be programming geniuses.