2 ms·
In different interviews, candidate might be asked the same literal question but be expected to produce very different responses. The interviwer will ususally pr
by ClumsyPilot 5y ago
In different interviews, candidate might be asked the same literal question but be expected to produce very different responses. The interviwer will ususally provide no context for the situation or state what he is looking for.
Interviews are not a simulation of reality, so you don't have context like you would in a real situation. Like in dungeons and dragon, what moves are allowed? What are the rules of engagement?
The people you will select are often those that read non-verbal clues or guessed what you are looking for. Thats why there is so much culture bias in interviews.
- throwaway2037 5y agoThat is a good point. I would be very upfront and provide a one pager before the interview explaining sample questions and what we are looking for. Also, each time I interview a software engineer, I give a 30 second "speech" that is roughly: "For today's technical interview, we are not interested in what you do NOT know. We are interested in what you do know and how deeply you know it. Some interviewers are trying to trick you or show they are smart or show that you are wrong. That is not us. If we discuss a topic that you don't know about or have no experience, just tell us. No problem -- we will move to a different topic."
- civilized 5y agoI haaaaate it when interviewers ask vague questions and then fault you for taking it in a direction they didn't want. So many interviewers act as if they expect to hire someone who has already worked at their company for five years and knows the codewords of the local cult.