---
title: How Clevid Works
url: https://clevid.com/docs/getting-started/architecture
description: How Clevid combines a dedicated desktop workspace, isolated coding environments, and human-reviewed video evidence.
category: getting-started
categoryLabel: Get started
subcategoryLabel: Overview
updatedAt: May 2026
order: 2
---

Clevid is built around a simple promise: **strong integrity during the assessment, zero background footprint once the candidate submits**.

<Note>
Unlike intrusive proctoring tools that install permanent system services, the Clevid Desktop Client runs as a regular desktop application only while the test is open and closes completely when the exam ends.
</Note>

## End-to-end platform overview

```mermaid title="How candidate sessions and reviewer evidence flow through Clevid"
flowchart TB
  subgraph Client["Clevid Desktop Client (Candidate Workspace)"]
    W["Focused Exam Window &\nScreen Overlay Guard"]
    H["Display, Camera & Mic\nPreflight Check"]
    M["Resilient Video &\nAnswer Sync"]
  end

  subgraph ControlPlane["Clevid Assessment Platform (HR Console)"]
    T["Session Timer &\nIntegrity Timeline"]
    S["Automated Grading &\nCoding Evaluation"]
    O["Recruiter Review Queue &\nCandidate Scorecards"]
  end

  W -->|Timeline Events| T
  H -->|Readiness Check| S
  M -->|Recorded Clips| O
```

## Core platform pillars

### 1. A dedicated desktop workspace instead of a browser tab

Standard browser tests can only see what happens inside a single browser tab—meaning floating AI assistants, second monitors, and background screen shares go unnoticed. Clevid's desktop app protects the whole workspace:

- **Floating Overlay Protection**: Detects transparent AI assistants and pop-up overlays that attempt to sit above the test window.
- **Single-Display Verification**: Checks connected monitors before the test begins and pauses the session if an extra screen is plugged in mid-test.
- **Clipboard & Focus Guard**: Keeps the assessment in focus and logs any time the candidate switches away from the exam window.

### 2. Built-in coding & test evaluation

When a candidate runs or submits code, Clevid evaluates their solution against your sample and hidden test cases in a clean, isolated environment:

| Language | Environment | Typical Use Case |
| --- | --- | --- |
| **Python** | `Python 3.12` | Data science, scripting, and backend algorithms |
| **JavaScript / TypeScript** | `Node.js 22 LTS` | Full-stack and web engineering challenges |
| **Java** | `OpenJDK 21 LTS` | Enterprise backend and campus placement drives |
| **C++** | `C++20` | Systems, performance, and competitive programming |
| **Go** | `Go 1.23` | Cloud infrastructure and distributed services |
| **Rust** | `Rust (Stable)` | Systems engineering and safety-critical roles |

<Warning>
External internet access is disabled inside coding runs so solutions are evaluated purely on the candidate's logic and the test cases you provide.
</Warning>

### 3. Resilient recording on unstable connections

Candidate answers and video clips are saved in small chunks as the test progresses. If a candidate's Wi-Fi drops briefly during a campus drive, their progress is buffered locally and finishes uploading automatically when the connection returns.