---
title: "How to verify if a candidate cheated in SkillCheck"
canonical: "https://help.skillpanel.com/space/TSG/2894004277/How%20to%20verify%20if%20a%20candidate%20cheated%20in%20SkillCheck"
format: markdown
---
SkillCheck includes multiple security and verification tools that help you confirm whether the right person took the test and if the results are trustworthy.

## When to use this

- You suspect a candidate may have received external help.
- The test score seems unusually high compared to prior performance.
- You need to confirm test authenticity before proceeding to interviews.
- Compliance or audit reviews require verification evidence.

## Quick start

1. Open a candidate’s test report.
2. Check **IP address**, **Similarity score**, and any **Session recording** if enabled.
3. Review **Static camera input** or **CodePair** footage for identity confirmation.
4. Note any irregularities and flag results if they require follow-up.

## **Security and verification features**

### Candidate IP address

Shows the approximate location where the test was taken.  
If the IP location does not match the candidate’s expected region, follow up directly to clarify. This simple check often exposes impersonation or proxy use.

> Why this matters: quick location validation can surface dishonest behavior early and prevent false positives in later stages.

![How_do_I_know_if_someone_cheated_1.png](media://49bf83c8-e58e-430b-a140-0c62a104bc07)

 

## Similarity score

An automated check comparing a candidate’s submission to other solutions for the same task across the entire SkillCheck platform.  
A high similarity score suggests code reuse or potential collaboration.

**Important:** Similarity does not always mean cheating. Common algorithms for simple tasks often look alike because there are few logical variations.

> Why this matters: global comparison detects copied logic patterns that manual reviewers might miss.

![How_do_I_know_if_someone_cheated_2.png](media://32a8795d-4d4c-4135-b560-14e5bd86c268)

### Session recording

If enabled, you can replay the entire test session. This includes typing activity, mouse clicks, and navigation history.  
Session playback helps confirm that the candidate solved the task independently and without suspicious pauses or tab switching.

> Why this matters: watching the flow of thought shows genuine problem-solving, not rehearsed pasting.

### Static camera input

You can require candidates to capture photos of themselves at selected points during the test.  
Use multiple checkpoints if identity verification is critical.

> Why this matters: image capture verifies the same person started, continued, and completed the test.

---

### CodePair (live proctoring)

CodePair lets you watch a candidate take the test live with video enabled. You can interact, ask questions, and even collaborate briefly on code if guidance is part of the process.

> Why this matters: live participation confirms identity and provides immediate context if a test seems inconsistent later.

### Social listening and content protection

SkillCheck monitors public sources to ensure tasks from our test library are not leaked or shared online.  
You can verify this yourself, searching for SkillCheck answers will return none.

> Why this matters: protected content keeps your assessments fair across all candidates.

## Use SkillCheck to go faster and safer

- **Automated proctoring tools** → detect suspicious patterns →  fewer manual checks.
- **Similarity scoring + playback** → confident authenticity decisions → lower false flags.
- **CodePair sessions** → real-time validation → builds trust with top candidates.

## Example

A recruiter sees a candidate complete a Python task unusually fast. The **IP address** shows another country, and the **Similarity score** is 95%. They replay the **Session recording** and confirm repeated copy-paste patterns. The result is flagged, preventing a risky hire.

## Pitfalls & tradeoffs

- Don’t assume a high similarity always means cheating, so verify context first.
- Overusing camera checkpoints can increase candidate friction. Use them only for high-stakes roles.
- CodePair requires scheduling and bandwidth; plan accordingly.