|
|
|
|
|
by inopinatus
4742 days ago
|
|
I've interviewed at Google. Years, years ago. I didn't get the job. Similarly, no brainteasers, but something worse: they made me write syntactically correct code on a whiteboard. I have never written code without using a keyboard; turns out, I just didn't have the neural pathways for anything else. My brain kinda seized up. I specifically recall failing to recognise the fibonacci sequence (especially horrifying given that I read mathematics at Edinburgh). Things went downhill from there. Ever since, whenever I've interviewed someone, I ask them to demonstrate their strengths to me first. |
|
Interestingly, I believe Google are slowly moving over all their coding interviews from whiteboards to Chromebooks - this is what I was told by my Google recruiter when I last interviewed with them, anyway.
The whiteboard can be a bit polarising...I love whiteboarding code, but I suspect many people detest it with a passion (I used to teach CS, so it's something I picked up on the job). I do think it is rather unfair to have candidates whiteboard and demand syntactically correct code, especially when under pressure. There's room for flexibility.