I interview a fair amount of people (3-5 a week), and most of this is solid advice. However, I'm not sure I agree with the section Getting Prepared for the Que

I interview a fair amount of people (3-5 a week), and most of this is solid advice. However, I'm not sure I agree with the section Getting Prepared for the Questions will Make you Sound “Rehearsed”: Wrong! I generally know when an answer is canned or the question anticipated (I'd estimate I catch it most of the time, but how would I know?), and I quickly switch gears to somehow take the question to the next level or introduce variables that can't have been anticipated by the candidate. In fact, that is a large part about what behavioral interviewing is, it is about digging down to ask follow-ups and determine what a candidate's real contribution to past projects really was. Rehearsing answers to a questions about what the coolest feature of Rails is won't help you, because I am then going to ask you about a time you specifically used it, why it made a difference in your past project to do it and not choose some other solution, what other ways there might be to do it if that feature didn't exist and if your coworkers agreed with the decision, etc. In short, I am going to ask you a lot of follow up questions to determine your actual contribution to something, and if I sense each response was canned I will keep drilling deeper until I find you actually thinking about your answer on the spot.