Just posted a new article on my blog: What if your interview coding challenge would be completely different? This is a (very) shortened version to get other developer's opinion on this.
Instead of the boring FizzBuzz, the annoying whiteboard, the mental dry-runs of code from a paper page, and all the other coding challenges we all so love to hate - what if we had something like this instead?
A coding challenge that is comprised of a few small parts, each designed to give the interviewer insight of a different aspect of the capabilities of the candidate.
These mini challenges should be as close as possible to your development team member’s day-to-day job, and combined, should take no longer than what you would normally expect the coding challenge part of the interview:
- Reading a small codebase
- Simple debugging
- Actual problem solving
- Finding and fixing logical problems in a codebase
- Simple code design
- Handle specification changes
So, what say you?