3 ms·
It’s pretty hard to have a reliable interview process if you don’t ask all of the candidates to do the same thing. Comparing how a candidate performed compared
by twblalock 7y ago
It’s pretty hard to have a reliable interview process if you don’t ask all of the candidates to do the same thing. Comparing how a candidate performed compared to other candidates on the same set of tasks is an important part of the evaluation.
Consistent processes are also important for avoiding bias. For example, take-home projects are more likely to make sense for young candidates who aren’t raising families and have free time after work. If you have most of your young candidates doing take-home projects and the older candidates doing whiteboarding, you will end up evaluating candidates differently based on age.
- jenscow 7y agoCandidates have different strengths and weaknesses. Sure, I'll ask the base questions but in terms of assessing their coding ability I'll go with whatever they feel the most comfortable with. If they have github, I'll ask them to walk me through a few files, asking their reasons for doing X, why not Y - what does this do? If they prefer take-home, I'll give them something to create/improve. Want to do something now? knock yourself out - with or without me watching. I don't need to sort the candidate into an ordered list, just filter out the "over confident". The questions I want answering is: Can they actually code? Does their skill match their experience? Is their skill level similar to the codebase?