HackerRank for work uses a comprehensive and swift plagiarism detection methodology intended to identify candidate submissions with the likelihood of plagiarism by determining if codes are similar and incorporating specific behavioral signals. We optimize for candidate experience and reduce false alarms so that we do not penalize any innocent candidate(s) while ensuring all submissions are original and authentic.
HackerRank for work provides detailed Test Reports which help you view your Candidates' performance in a Test. The Test Reports are generated after the Candidates' have submitted a Test. Below is a walk-through of how a recruiter can use our plagiarism detection process while analyzing candidates based on their test reports.
Prerequisites
- It would help if you had a HackerRank for Work account.
- You must have at least one test attempted by Candidates and their submissions pending for further evaluation.
Steps
- Navigate to the Tests page and select the required Test.
- Click the Candidates tab, and select a Candidate entry pending evaluation.
- The Candidates Test Summary page will display the Suspicious Activity tile, including indications of plagiarism.
Click the View option in the Suspicious Activity tile or Click View report for a particular question. - The Attempt Activity Tab will show if the candidate has submitted code that has flagged as plagiarized, as shown below.
-
Our plagiarism detection tool also shows matches with other candidates across HackerRank for Work who might have submitted the same or similar code to the said question in any test. We match for a similar code with:
- All candidates were attempting any test across any company on the entirety of the HackerRank for Work platform.
-
The code matching happens in the following fashion:
- If a matched candidate is from the same test as the current one, you will be able to see the code match percentage, the date of the same/similar code submission, and the candidate's email.
- If a matched candidate is from a different test, but you have access to the test, you will still be able to see the code match percentage, date of identical/similar code submission, name of the test, and the candidate email.
- Note: If a matched candidate is from a different test that you do not have access to, you will still be able to see the code match percentage date of duplicate/similar code submission but not the test name or candidate email.
- If a matched candidate is from the same test as the current one, you will be able to see the code match percentage, the date of the same/similar code submission, and the candidate's email.
- Code Match Percentage and View Output Diff: The 'Match Percentage' shows you how much match there is between the current candidate's code and matching codes. To the far right of the match, the percentage is the option to 'view diff,' clicking displaying matching codes with highlighted differences. Based on this possible, partial, or no match scenario, we recommend the match percentage. Based on the result, the recruiter can take a call as to how to proceed with the candidature.
Plagiarism Detection at HackerRank for Work detects candidates who have the same structure of code and logic used but could have changed variable names looping constructs in addition to specific behavioral signals and flags for plagiarism. Read more about plagiarism detection and how we go about it here.