Whiteboard exercises, homework, and pair programming are ridiculous ways to test a candidate.
Code samples tell me more about an engineer than absurd and contrived and time pressured tests that have no relationship to how real engineers solve problems.
Those are tricky though. What if someone doesn't have readily shareable code? I'd argue that if you really deconstruct how you would be evaluating a persons' code, you can probably get the same information by thoughtful questions.
2 comments
[ 3.1 ms ] story [ 16.2 ms ] threadCode samples tell me more about an engineer than absurd and contrived and time pressured tests that have no relationship to how real engineers solve problems.