In my previous post, I described a simple interview question and the various approaches different types of programmers take. These weren’t mistakes per se, but they revealed biases and were good indicators of potential future problems, or holes in a programmer’s mental map. Like the candidate who sees everything in terms of recursion (or avoids […]
Over the past three years, I’ve easily done over a thousand technical interviews, each of which involved having the candidate write code on a whiteboard, either in person or online. There are lots of people who will try to convince you that this is a bad approach – that you should focus on what candidates […]
An introduction, with some quick comments on interviewing.