Maybe I'm the only one here, but I actually like technical interviews. Granted, I've done a handful of terrible interviews (either because of the questions or b

Maybe I'm the only one here, but I actually like technical interviews. Granted, I've done a handful of terrible interviews (either because of the questions or because the interviewers weren't prepared), but I think good tech interviews are very productive. I've been on both sides of the table: from the interviewee's side, a good interview allows you to show off your strengths and show the team how you work; from the employer's side, it's important to get inside the candidate's head and see exactly how they work and how the solve problems. Now, a good interview isn't one where you ask question about the technical details of a language or a framework or how HTTP works or anything like that. Sure, good technical knowledge is necessary for most positions, especially senior ones, but information is really easy to pick up as you go, whereas real talent is not. Good interviews ask more broad, open-ended questions. "If you wanted to build X, how would you build it?" "If your app was really slow, where would you look to fix it?" "What do you think about framework/language/tool X in relation to tool Y?" Etc, etc. These kinds of questions let you really get into the candidate's head and figure out if he's a good fit, while still allowing him room to go in a different direction and play to his own strengths.