3 ms·
Reasoning behind why whiteboard interviews suck is based that doesn't model real job skills. Maybe our org is an outlier but but we heavily rely on whiteboard
by adrr 9y ago
Reasoning behind why whiteboard interviews suck is based that doesn't model real job skills. Maybe our org is an outlier but but we heavily rely on whiteboards to plan out architecture(ERDs,flow), problem solving, training/knowledge sharing. Our trello cards sometimes contains images of whiteboarded diagrams. Being able to explain and whiteboard your stuff is a very important skill at organization.
- jay-anderson 9y agoSketching out ideas and preliminary diagrams is very different from programming on a whiteboard. If a whiteboard interview were talking at a higher level about the problems at hand then I don't think it'd be such a problem. However, that doesn't seem to be the case. In whiteboard interviews you're asked to write detailed code on a board.
- rimliu 9y agoHow many images in your trello contain C code for reversing string?
- neeleshs 9y agoYep, whiteboard programming - not good . Whiteboard interviews is too generic a name to use for that.
- ng12 9y agoI'm fairly convinced much of the hate comes from people who interview at firms who do WBI incorrectly. The question I give is tailored for the following points: You can pick up unfamiliar code/data structures easily You can understand a given problem space without too much explaining You can code the "easy stuff" without thinking about it too much You can distill and discuss the difficult parts of an algorithm All of which are traits I consider key for someone I'll be working with.