4 ms·
I feel this is somewhat industry dependent, so take this with a grain of salt (finance answer). They cultivate a friendly banter type atmosphere. As to the act
by Havoc 9y ago
I feel this is somewhat industry dependent, so take this with a grain of salt (finance answer).
They cultivate a friendly banter type atmosphere. As to the actual test part:
The ones that have asked questions that require a judgemental answer.
Bad interviewers try to ask difficult or complex questions. (Stupid monkey puzzles / google style "trick" questions")
The good ones assume you're technically competent and throw you questions where the question is crystal clear but the scenario is ambiguous & open to interpretation & vague. I don't need people that can do monkey puzzles I need people that can respond dynamically in the face of uncertainty.
e.g. How would you go about detecting fraud in a scenario like XYZ.
That has a million possible answers...but depending on which route you chose it'll become painfully obvious to the interviewer whether you know what you're talking about. It doesn't even have to be the right one...the language and logic alone will betray you if you don't know what you're talking about.
- mratzloff 9y agoI agree completely, and it applies equally to software engineering. It's how I interview. Now, if it becomes clear that there are gaps in their knowledge, I will spend some time on those areas so I (or the relevant hiring manager) can make a decision regarding if the trade-offs are something I (or they) can live with. For engineers, that can sometimes mean an algorithm problem--but something they haven't likely seen before. The key here being that I don't want to see someone regurgitate a solution, but to understand how they think. If they can't solve a problem fully but can come up with a list of 10 extremely pertinent questions I intentionally failed to mention, that is good information to have.