Earlier quoted context omitted.
Is there a better way of making sure someone can actually code? It’s easy to take credit for past projects when it’s unclear how much help you had or what part you played. Isn’t the best way to judge a candidate asking them to create/produce something for you?
IMHO a better way would be: - A non-trivial take-home exercise and give them a week or two to complete. This should have higher weight on the decision instead of the "Google doc coding" as most likely that's the type of code they'll be shipping to production. - Use the onsite interviews to improve upon the exercise and/or to get into the nitty gritty details, and also to make sure this is the type of person people wo…
If you'll end up having to do a face to face analysis to make sure someone didn't cheat on a big take home assignment like that, why not just skip to the face to face analysis?