> Closely related to speaking poorly is sounding disinterested. It's an absolute turn-off to hear somebody who's dead inside and their job is like a prison. It

> Closely related to speaking poorly is sounding disinterested. It's an absolute turn-off to hear somebody who's dead inside and their job is like a prison. It can also be taken as disrespectful. I'm taking the time to interview you, and I expect you to show some modicum of interest in the process. Along those lines... One warning flag to me is interviewees who ask no questions, or who ask pedestrian questions. So much of what programmers do boils down to asking the right question - and then answering it. Why doesn't this loop exit? Who's maintains that piece of code? What authorizations do I need to fix this problem? What if we simply let this bug be? How do I know the right time to optimize code? What are my supervisor's/company's larger goals with this project? Beyond that, it takes research to ask good questions about a company or person a job candidate will be interviewing with. The interviewee who comes prepared with good questions to inject into the conversation is someone who has a plan. An interviewee who asks no good questions looks like someone who needs a lot of direction. That's something to explore in an interview, but there's really not much time. The safer bet is to pass.