Re:Coding Interview Cheatsheet
by watwut on Saturday October 14, 2017 @09:24AM
(#15472057)
3. Or who worked a lot for previous employers or took school seriously. GitHub full of contributions is hard if you work 40 hours a week without slacking at work, basically impossible for those who do a lot of overtime. People who spend their out of work time learning (e.g. reading books or other theoretical stuff) are out too.
But really most importantly, it is important for reviewer to be prepared for things like performance anxiety, like shy people who are not good at looking confident, to people cant think out loud (don't hold it against them if they are silent for few minutes for christ sake) and so on and so forth.
But people here throw temper tamtrum over really simple well known questions.
Maybe the companies would to the best if they made their expectations clear and realistic in ad itself. Let people know how interview looks like before hand, let them know what exactly it is you expect and then stick to it.
But really most importantly, it is important for reviewer to be prepared for things like performance anxiety, like shy people who are not good at looking confident, to people cant think out loud (don't hold it against them if they are silent for few minutes for christ sake) and so on and so forth.
But people here throw temper tamtrum over really simple well known questions.
Maybe the companies would to the best if they made their expectations clear and realistic in ad itself. Let people know how interview looks like before hand, let them know what exactly it is you expect and then stick to it.