4 ms·
Sure, at 400 interviews, you'd get decent. But that's my point! Do you want to hire people who are good at the job, or do you want people who are good at interv
by gkoberger 6y ago
Sure, at 400 interviews, you'd get decent. But that's my point! Do you want to hire people who are good at the job, or do you want people who are good at interviewing?
- josephg 6y agoSure, I want to hire people who are good. But honestly a well designed interview is a pretty good way to find them. You get some false negatives (people who are good, but interviewed poorly because of stress). But I suspect most people I passed on (90%+) were true negatives - they didn’t pass the interview simply because their programming skills aren’t as strong as I’d like to see. And (I hope) most people who struggle with interviews can figure that out with a bit of practice. If it takes you 5 bad interviews before you do a good one (and land the 6th job you apply for), that’s great. Nothing is harmed in the process but your ego, and a bit of time. Every time there’s an article like this on HN there’s people whinging about the interview process. But for most developers, interviews work fine. I stand by my claim that a well designed interview with a balance of content (see my other comments in this thread) is a fair and accurate way to assess a candidate’s programming skills.