Ever since, whenever I've interviewed someone, I ask them to demonstrate their strengths to me first.
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.
Nice. That agrees with some of the other comments here. For example, about asking about past work or projects that they are proud of or that demonstrate their skills.
Another hard issue is what to do, as an interviewer, if things start to go downhill to the point where the candidate becomes flustered and you can tell they're not at their best.
A quick googling sessions confirms this, inopinatus studied maths in Edinburgh according to his Linkedin.
> I would take 'read' as a pretentious term.
I'm confused...
The disposition of my pinky, however, shall remain a mystery.