5 ms·
I've tried this in the past when hiring for a startup in two different ways: one with having the entire interview based around simply discussing past projects a
by robbrit 11y ago
I've tried this in the past when hiring for a startup in two different ways: one with having the entire interview based around simply discussing past projects and gauging the level of interest; the other combining this type of discussion with a coding problems or two.
The result: the correlation between passion and competence is not 1.
Initially I wanted to give them the benefit of the doubt and hire primarily on talk alone, however I found that some people are passionate and interested yet can't code very well. After having to fire folks because of it, I decided to actually make them write code during the interview. Sure enough, I discovered a few candidates who could talk the talk, but when faced with an actual problem* couldn't actually solve it.
* When I give interview problems I like to actually give problems that I have faced in my job.
- spitfire 11y agoSo you found work sample tests were an effective predictor? This matches industrial research.
- brightball 11y agoAnd admittedly, that's true. I suppose I shouldn't have let that come off as a purist "only ask this" situation. You need some technical problem that they can solve based on the skills you need and the skills you can judge. For those types of problems, I tend to focus on watching HOW they get to a solution and why rather than pure syntax. I shouldn't have represented my original comment as the only thing necessary. Getting a mainframe guy to geek out on me for an Android position is probably not going to be all that beneficial.
- eikenberry 11y agoBeing able to talk about past projects is not passion, it is simple professionalism. How can you work in a field for long without being able to talk intelligently about it. I also don't find testing for actual coding skills to be a problem as most candidates don't make it to the interview if they don't have some sort of portfolio of code samples.
- robbrit 11y agoA portfolio of code samples is not always available. Juniors often don't have code samples; neither do people who have only really worked on proprietary projects. I don't like to discount potential good developers just because they spend their free time doing things other than coding.
- deedubaya 11y ago> spend their free time doing things other than coding This is a valid point. A good work/life balance is critical. But to counter it, don't you want to look at candidates who _want_ to get hired, so they've spent a little extra time writing something for potential employers to look at? A developer who gives up at "I don't have code samples" isn't someone I would want to hire.
- robbrit 11y agoIf they didn't want to get hired, they wouldn't have applied for the job. Assuming that "I don't have code samples" is equivalent to "I don't care" is a silly assumption, and one that I've found is completely false in reality. Some of the developers I've hired have years of experience but no code samples, and after hiring them I discovered I had made the right choice. They just have other priorities on the side (children are often a big one).
- eikenberry 11y agoCode is art and artists have portfolios. Not having at least a minimal portfolio shows a lack of professionalism. Would you hire a graphic artist, a writer, a painter, etc. without previewing their work first.