How many interviewers know the answer for a question he asks?

Question

Hi,

Before voting to close please take a look at the details.

In many interviews the interviewers asks questions that has no relevance with the role that an applicant is applied for. I am speaking about technical questions only.

For example.

The position is for a .net developer who has experience in .Net framework 2.0 and the interviewer keeps asking questions related to 3.0 and 3.5. Is this in any way helpful to the company or is the interviewer trying to show off his knowledge in these areas?

My question is how many of interviewers know the answer of a question he asks? Is it necessary for him to know the answers since most of the interviewers won't allow candidates to ask the interviewer to explain the answer.

Answer 1

I suppose that knowing the right answer and the explanation of that is critical for the interviewer. The interviewer will make a decision that will fully or partially influence whether the interviewee will be hired. This decision can't be made without the interviewer knowing what the interviewee is answering him.

Plus th interviewer who knows what he's asking about can choose further questions depending on what and how well the interviewee can answer. This allows for more thorough evaluation than just a test where the interviewee is given a set of question and has to sit for an hour and provide answers.

Answer 2

Though it's possible that the interviewer is just trying to show off their knowledge, it's also possible that there are other reasons:

• While the position is .NET 2.0 right now, they're looking to the future and want to know what they have to work with
• They want to see how you respond under pressure - ie something you weren't prepared for
• Want to know if you're not afraid to admit you don't know, or if you'll try to BS your way out of the question

Those are all legitimate points, and I'd be interested in how my candidates responded. Especially #3 - I'd be much happier with somebody who could admit they didn't know, as opposed to somebody who just blindly accepts an assignment without having any idea WTF they're doing.

Answer 3

I make it a point to try to be an absolute expert on the interview questions I use. That means not only knowing the answer to my question inside and out, but also knowing as many tangents and related topics as possible. I've been proven wrong once or twice as an interview candidate went off in an unexpected direction, or raised an angle I wasn't prepared for. But after such an interview, I try to learn whatever new aspect to the question I missed before I use the question again.

I know not all interviewers approach their questions this same way, and I look dimly on both an interviewer and their company if I know something about an interview question that they don't. After all, they picked the topic and had time to prepare, and I come in fresh and unprepared.

I'm going to interview two candidates tomorrow, and have my questions ready to go. We'll see how they do! :)

Answer 4

Essentially, the interviewer MUST know the answer to the questions they are asking. If they don't they are wasting everybody's time.

On the point of getting .NET 3.5 questions for a .NET 2.0 role. Perhaps they are currently using .NET 2.0 but will be upgrading shortly.

Also, feel perfectly free to ask questions back to the interviewer. It is a two way process. They are evaluating you, and you are evaluating them.

Answer 5

Of course an interviewer should know the answers to the questions they are asking.

Also, asking about a newer version of a framework lets the interviewer see if you are proactive in learning about the latest developments or are just happy with what you know. I think this is a good way to tell if someone is really interested in what they do or if it's just a job to pay the bills.