Solid anti-cheating measures

To ensure that all CodinGame test results are an accurate, trustworthy representation of candidates’ skills, we take cheating and plagiarism very seriously.

Prevent

We’ve built strong preventive measures into our platform.

  • Our Random Blocks feature automatically generates randomized groups of questions based on your test settings (role, domain, difficulty, etc.). This means that no two tests are the same, and makes it much harder for candidates to look for and/or leak solutions online.
  • Candidates cannot copy and paste question statements without us knowing. You can choose to deactivate copy and paste within the candidate IDE too, but we don’t recommend it.
  • We continually update and refresh our content, so as to limit the risk of leaks.

Detect

We continually and automatically monitor candidate activity within our platform. We also empower you to identify any suspicious behavior.

  • Our Code Playback feature provides insight into how your candidate built their algorithm, when they left the environment, when they copied and pasted, etc. If you pick up on any malpractice, you have the power to flag and reject the candidate.
  • We regularly crawl the internet to detect question and/or solution leaks.
  • Our system will pick up on any abnormal candidate performance (e.g. difficult questions completed in a fraction of the usual time).
  • Our plagiarism detection engine will recognize if a candidate submits the exact code previously submitted by another candidate and trigger a notification.
  • We track candidates’ approximate geolocation so as to spot any unusual behavior (e.g. logins from different locations or devices during the test).

Respond

We don’t jump to conclusions. However, in the unfortunate event of cheating, we react fast.

  • We take necessary action to remove leaked content from the internet.
  • We refresh any compromised content.
  • We keep you informed throughout the process.

Frequently asked questions

We believe that online proctoring is both inefficient and counterproductive. These monitoring measures are proven to introduce bias, provide for negative candidate experience and hinder test performance. What’s more, if a developer were so inclined, they would be incredibly easy to dupe.

We believe that this type of ID verification is unnecessary and counterproductive.
We would never recommend starting a candidate/recruiter relationship with a demonstration of mistrust. We very, very rarely come across cases of identity fraud. This is likely because candidates are well aware that at some point in the recruitment process, they will need to show their face and interact with recruiters or future colleagues.

We can’t publicly share the ins and outs of our plagiarism detection technology, for obvious reasons. However, we can send you more information on how this works, if you’re interested and willing to sign an NDA. Simply get in touch: [email protected]

Simply put, we record candidate activity during a coding exercise. You can watch how your candidate built their algorithm, when they left the environment, when and what they pasted from external sources, and what happened when they ran their code. You can explore a demo version of our Code Playback by clicking here.

Ready to start testing developers' skills?

*No credit card required