Understanding the candidate report, plagiarism, and cheating issues

How to analyze a candidate report.

 

Breakdown

We combine several factors into a final plagiarism score in a candidate report. Our system monitors the following events:

  • Copy/pasting in the editor
  • Reference searches
  • Tab leaving

Copy/pasting

Our system monitors the editor page where a candidate is writing code to make sure they do not copy/paste from any other source. If they do, we flag it in our system and let the candidate know they should not be copy/pasting into our editor. 

We show you all the pieces of code the candidate copied, and it looks something like this:

Screen Shot 2020-04-15 at 8.48.24 PM

Reference searches

Our editor allows candidates to search Google for programming help as they are solving a challenge. You can then see what they looked up and what links they clicked on for help. This is a great feature for recruiters and engineering managers because it allows them to see the thought process behind what the candidate was trying to do. Here is an example of how it'll look in the report:

Screen Shot 2020-04-15 at 8.59.28 PM

Tab leaving

We monitor the editor page to let you know how many times and when a candidate left the page. Because we allows candidates to perform searches directly on the page, there shouldn't be a reason they leave the page too many times.