Here’s How to Interview Better- Hey Are You Listening?


A number of listening pitfalls will trip you up in your job interview. Don’t fall in these listening pitfalls:

  • Being so intent on what you have to say that you listen mainly to find an opening to make your point. You may be thinking that you have a very important point you want the interviewer to know, and if you don’t say it now, the opportunity will be lost. In reality, you won’t lose the opportunity, and this pitfall often results in an interruption[md]never a good thing during an interview.,
  •  Formulating and focusing on your answers quickly, based on what the speaker is saying. Candidates often are so concerned about giving the “right” answer that they get nervous and stop listening. They also have the misconception that they have to answer a question immediately after it is asked. It is perfectly acceptable to say, “Let me think about that,” and then take 30 to 40 seconds to formulate an answer. A thoughtful, considered answer is better than a quick, confused, or off-target response.
  • Focusing on your own personal beliefs about what you’re hearing. Your personal beliefs form a filter that may distort the interviewer’s meaning. It is important to be aware of how your beliefs distort what you hear and adjust for the distortion. You can do this by becoming consciously aware of your beliefs. For example, the interviewer might be talking about the importance of offshoring certain functions in their department. Perhaps you are opposed to sending jobs overseas. Your opposition may impact how you listen to the interviewer’s message. However, if you say to yourself, “This is an area of disagreement for me. I need to stay in active listening,” you will be able to focus on the message and not your internal resistance and judgment.
  • Evaluating and making judgments about the speaker or the message. While the interviewer is busy making subjective judgment about you, you are busy making subjective judgments about her. Judgments can distort how you hear things- both positively and negatively. If you have a positive impression of the interviewer, you might tend to believe what she is saying and not ask clarifying questions. If you judge the interviewer negatively, you might prematurely dismiss what she is saying and not listen fully. Be aware of your judgments, which can be as simple as whether you like or dislike the person, so that you don’t lose the message.
  • Not asking for clarification when you know you don’t understand. Many candidates think that asking for clarification is a signal to the interviewer that they don’t understand and that, as a result, they will appear stupid. A candidate of mine walked out of an interview sweating because the interviewer used an acronym he did not know, and he didn’t ask what it meant. Throughout the interview, the candidate was hoping he wouldn’t be caught; as a result, he was a nervous wreck and performed poorly. It turned out that the acronym was an obscure, little-known term that he couldn’t have known anyway. The interviewer was either impressed the candidate knew or guessed that he was covering up- probably the latter, since there was no job offer.
As it is in all sales situations, listening is the most important activity in a job interview. The more time you spend listening and understanding the job, the better you can match your background, skills and experience to the critical job requirements.
Advertisements

One Response to Here’s How to Interview Better- Hey Are You Listening?

  1. […] Here’s How to Interview Better- Hey Are You Listening? (employmentinterview.wordpress.com) […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: