| I find the move to take home tests extremely unfair. Anyone with dependents will typically need to block out most of a day of a weekend, or risk doing it in intervals through their week. Got a decent CV? Good luck trying to juggle applying for more than 2 interesting opportunities at once. We mostly hire full stack web devs. IMO It's impossible to really test the abilities of each candidate across the changing landscape of front end, back end, DB & devops tech within an interview process that doesn't use a vast amount of time for everyone. Instead, we don't whiteboard or code at all in our process at the moment, and try and get it all done in a face to face hour or two by: * Taking their experience at face value. Examples: If they have been coding for a couple of years, don't waste everyone's time with fizzbuzz. Assume they will be able to adapt to our source control system, if they have been using a different one. * Insisting on real world examples when asking competency questions. * Asking generic questions about code, such as "What is clean code?", "what should you take into account for password security for a web app?", and looking for their ability to communicate as much as their actual answer. * Looking for areas of strength and weakness to compare across candidates, rather than trying to catch them out. * Scoring highly for enthusiasm, flexibility and a willingness to learn over pure technical knowledge. I appreciate this approach wouldn't work for all organisations but we've done really well out of it. |
No fancy algorithms. No obscure data structures. Just simple loops and conditionals in any language.
It has been the most effective (and most depressing tool) I’ve seen in eliminating the myriad of fakers and unqualified people.