\t\t\t\tI got another bad hire a couple of days ago. One thing I noticed is that even though I spent 2 hours carefully interviewing him, it only took me 5 minutes of working with him before I started seeing red flags and warning signs. Among other things it took him 5 hours to compile, download, and run the game, when I’ve had others in the past do it in 30 minutes. That’s raw experience right there.<\/p>\n
I’m going to try a new interviewing technique, which is to give a real programming task that<\/p>\n
1. Interfaces with a larger system, so you have to work with someone else’s code
\n2. Has multiple solutions, some of which are better than others
\n3. Takes enough time to require real though and design, but not so much that it would take someone competent longer than an hour, and designed such that a great person could do it in minutes.<\/p>\n