|
|
|
|
|
by untog
4435 days ago
|
|
I would be more specific - Death to Interview By Whiteboard. I haven't had many, but every whiteboard interview I've had has been miserable. At best I've just about managed to convey what I mean, at worst I don't even understand the question. One particularly memorable exercise had the interviewer write out HTML on the board and ask me to write out the CSS to turn it into a dropdown menu. I didn't even know where to start, because I couldn't construct a mental model of what was going on where. Because outside of the white board interview I never have to. A much better technical interview that I do not with death upon is one that put me in front a computer which was rigged up to a projector that the interviewer could see. We talked through my solution to an exercise as I constructed it, and I was free to switch between the browser and editor as I wanted. You know, like I might in a normal, actual working day. An even even better interview was one that left me in a room for 45 minutes with a task. After that time I sat down with the interviewer and talked through what I did. |
|
In my experience, being bad in either one of these interview types is not correlative to being bad at being a developer.