One of the hardest things for me to do in a technical interview is watch someone paint themselves into a corner or commit an obvious mistake without saying anything or giving any indication on an exercise.
It’s also yet another way for bias to sneak into the process: I’m more likely to find myself gently correcting/coaching a candidate I’m already predisposed to favor.
-
-
Instead of asking silly algorithm type questions have the candidate explain an algorithm they have implemented. Dig deep to get at their thinking, evaluate that instead of knowledge of tricks. My approach anyway YMMV
-
One of the (several) things we ask people to do is sit down and code simple examples in a browser environment. This is real and to my criterion: ethical. But a side effect of this is that code structure becomes important and the "working"-ness of the code is important.
-
It's very important for the standardization of interview processes, then, to NOT interfere until the end. My practice is to help them resolve the code either in the last 5m of the interview, or when they ask, with the later being a positive sign.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.