My Painful Experience Interviewing Software Developers
I’ve been on both sides of the interview, and it’s terrible, no matter how you slice it. The worst part is that it wasn’t even any interviewee’s fault. The process is that bad.
I read “The True Pain Of Hiring A Developer” by Dr Stuart Woolley (one of my favorite writers), which inspired me to write about my experience interviewing software developers at my last company.
Let me tell you what, it sucked so much ass.
My main gripe was the confusing scoring system, structure, and sheer volume of candidates. You weren’t finding good developers in this process. Based on that, it was just finding out who could interview the best at rating. You can’t hire everyone, but you can damn well interview them all for the fun of it.
It’s not a new concept in tech because it’s tough to interview candidates for. My solution has been to hire people at an hourly rate after a simple competency interview to see how they perform.
However, this isn’t about solutions but whining.
Interviewing Pain
The problem with running interviews at a larger company is using a standard rubric that can be applied to each candidate and digestible by others. In theory, it’s a pretty foolproof idea: check for these things, whether the…
