4 ms·
"Why would I have reason to be abrasive?" Interviews are mostly (~80%) about evaluating the candidate for fit. They almost always have a time limit. The interv
by rahimnathwani 8y ago
"Why would I have reason to be abrasive?"
Interviews are mostly (~80%) about evaluating the candidate for fit. They almost always have a time limit. The interviewers job is sometimes made harder by a candidate who answers a question different from the one asked, or who rambles unnecessarily, or who continues talking after the interviewer is satisfied with the answer to a particular question.
In these situations, the interviewer needs to quickly cut off the candidate and move to a different line of enquiry in order to collect enough useful signal during the allotted time.
This can come across as abrasive to some people, particularly if it happens multiple times during a single interview. And the impression can be compounded if they feel the interviewer cut them off as they were saying something which would have increased their odds of success.
- specialist 8y ago"Interviews are mostly (~80%) about evaluating the candidate for fit." Interviews in our industry are the chaotic mutant hybrid of "Guess what I'm thinking!" and fraternal hazing rituals. I've been interviewed a few times by self-declared bar raisers. Not impressed. One raiser dismissed outright all my work on grammars, saying the tool (ANTLR) did all the work. Awkward pause. Has he never written a parser? Is he making a joke? Oh. He's serious. Unfortunately, I eventually sarcastically replied "Ya, and the compiler writes all my code for me." I'm not a CS researcher. Our pithy jobs are client/server CRUD apps with some glue. Cut a string from here, paste it over there. Do some validation. Make sure the concurrency scales. Not rocket science. Stop treating me like an initiate. I've been doing this longer than most.
- indogooner 8y agoI don't know if you are referring to Amazon bar raisers but most of them are Dev Managers who don't write code on day-to-day basis. And this is a common problem where they don't understand the technical depth of the problem a candidate has worked but still have most weightage in debrief even on technical strengths.