I agree with all of these, but I'm glad you brought up points 7 and 9. As a job applicant, you don't always know how bad things are or will be until after you

I agree with all of these, but I'm glad you brought up points 7 and 9. As a job applicant, you don't always know how bad things are or will be until after you start working there. Sometimes, the job starts out OK, but things get progressively worse over time. Am I supposed to voluntarily endure a crappy situation that has no end in sight, so that my next employer doesn't think I'll leave too fast? You should be able to explain that kind of thing in an interview without it being considered a mark against you. As for #9, too many places ask these types of questions when the job you're applying for amounts to cranking out CRUD web apps. I think it's just cargo-cult behavior from old Microsoft interview techniques. If the job will require the unorthodox, creative thinking the employer is trying to test for by that question, a better way to do that would be to see if I have any actual projects, apps, open-source code that I actually wrote that demonstrates this ability.