For the first question, Aline Lerner, leeny on HN and founder of interviewing.io, wrote an excellent blog post on this very topic: http://blog.alinelerner.com/

For the first question, Aline Lerner, leeny on HN and founder of interviewing.io, wrote an excellent blog post on this very topic: http://blog.alinelerner.com/how-to-interview-your-interviewers/ http://blog.alinelerner.com/how-to-interview-your-interviewe... Regarding bad fits, I could go on about this all day long, but the two obvious ones I'll offer are this: 1) Assuming you're applying for a software engineering position, if they only ever ask you programming-related questions and don't try to gauge things like professionalism, hobbies, communication skills, how you deal under stress, etc, then they're missing the point. (Being able to program is the MINIMUM requirement for the job, after all.) 2) If the interview feels like an interrogation and not a conversation, that's bad. If they spend the entire interview asking questions and then give only enough time for 1-2 questions of your own, they wasted a lot of your time. Interviews go both ways: it's an opportunity for you to learn about them just as much as it's an opportunity for them to learn about you. You should spend half your time asking your own questions, imo. These aren't deal-breakers, of course, but they're red flags. Enough red flags and you won't be a good fit. Anyway, good luck.