3 ms·
Take 4 pages worth of interesting/diverse parts of real production code (Non-IP sensitive) and do a 'code review' where the candidate is the reviewer. For more
by DoingIsLearning 6y ago
Take 4 pages worth of interesting/diverse parts of real production code (Non-IP sensitive) and do a 'code review' where the candidate is the reviewer.
For more junior candidates add blantant defects or bad design into the sample code.
I have experienced this both as a candidate and as an interviewer. As a candidate, I found this a lot less adversarial and less stressful. As an interviewer, IMHO this gives a lot of insight into how a candidate thinks, without being a huge time sink, like 4 hour whiteboard tests or take-home assignments.
- collyw 6y agoI like this idea on principle, but I don't find it easy to jump into new codebases and see what is going on. Its usually after working with it for a couple of weeks that you see what is good and bad. Maybe something like this but given to the candidate to look over in their spare time. One of the best interviewing experiences that I had was when I was asked to bring in my laptop with some of my code to discuss. I had a side project that I was working on at the time so that was not a problem. I showed the interviewer, he asked questions, asked me to add a simple feature, I did. No algorithimc nonsense (which is basically about as reliable as a coin toss as to whether I will get the answer on the spot). No hours of my spare time wasted on take home challenges. It felt like less pressure than usual as it was code that I knew.