3 ms·
Today, I guarantee you that candidates will eventually take that risk to cheat in the online assessment stage in the hopes of getting an offer from the company
by rvz 2y ago
Today, I guarantee you that candidates will eventually take that risk to cheat in the online assessment stage in the hopes of getting an offer from the company and will likely turn into a bad hire.
Not hiring them is better than a bad hire.
If it were me, I would not use Hackerrank, Leetcode, or other online puzzles sites. Instead it would be just a conversation in to just show me your open source contributions in large repositories or you building projects (open / closed) that others are using.
That is it.
For contributions, they must be under public code review or you doing the review and for open source projects they shouldn't be hello world / test projects but useful to others which are used as dependencies in other larger open-source projects.
A basic easy conversation that rids of 95% of cheaters and frauds and those who cannot code.
- OutOfHere 2y agoNot everyone has open source projects to show. Also, for the ones that do, extremely few would be used as dependencies in larger projects, so that requirement is just ridiculous. Also, how do you even know if it's the candidate that has developed the code? You simply don't know if the candidate copy-pasted the code. Secondly, just because someone cheated at an extremely difficult Leetcode problem doesn't in any way mean that they can't code on the job. Jobs hardly require such problems. Instead, ask the candidate to explain specific parts of your code that you show them. It can also be cheated, but it has both a screen and a voice input component, so cheating would take more work.