2 ms·
How do you verify no cheating with work samples? > Create a project based coding assessment that directly reflects the work the developer would be expected to
by TulliusCicero 7y ago
How do you verify no cheating with work samples?
> Create a project based coding assessment that directly reflects the work the developer would be expected to deliver if hired, making sure to provide some open-ended flexibility that allows candidates to showcase their strengths. This might require the developer to digest an existing code base, gather requirements, communicate to your team a push request they’d like to make, or provide a detailed description of code that they’ve submitted before merging into production. These activities move your assessment process beyond the code, revealing insights into what a candidate would actually be like to work with.
That sounds like it'd take more than 3 hours, unless it's based on a very small project.
- twblalock 7y ago> How do you verify no cheating with work samples? You can't really, and that's the main reason most of the teams I know avoid them, or supplement them with onsite whiteboarding.
- TulliusCicero 7y agoYeah, I know some teams say that they discuss the project after, which would work if the candidate couldn't code at all. But if they're just a mediocre programmer who's been coached, it may be harder to detect, especially if they have a talent for BS'ing.