Should campus recruiting and intern hiring use AI interview proctoring?
TL;DR: Yes for identity and integrity basics, but keep it light. Campus hires happen at high volume with tight per-candidate cost, so the goal is catching proxy test-takers and AI-assisted technical screens in large first-round batches, not building an adversarial process for a 21-year-old's first professional interview.
The claim
Campus and intern pipelines are often the highest-volume, lowest-scrutiny stage of hiring — hundreds or thousands of first-round technical screens run in a short window, exactly the conditions where AI-assisted cheating scales cheapest for candidates and where a single human can't review every session.
The evidence
CodeSignal's data shows technical assessment cheating rates doubled from 16% to 35% year-over-year, and campus hiring pipelines lean heavily on exactly this kind of high-volume automated technical screen. Karat's research found 80% of candidates use LLMs during banned live coding tests — a behavior that skews younger given how normalized AI tool use already is among students.
Comparison: campus hiring vs experienced-hire proctoring needs
| Factor | Campus/intern hiring | Experienced-hire proctoring |
|---|---|---|
| Volume | Very high | Lower |
| Per-candidate proctoring cost tolerance | Low | Higher |
| Primary risk | AI-assisted coding screens, proxy test-takers | Identity fraud, deepfakes, coaching |
| Appropriate intensity | Light identity check + tab/screen monitoring | Full trust report, continuous verification |
Step-by-step: right-sizing proctoring for campus hiring
- Apply lightweight identity verification (ID + selfie) at the first technical screen, not every touchpoint.
- Enable browser lockdown and tab-switch detection for any timed coding assessment, since that's where AI-assisted cheating concentrates.
- Reserve deeper trust reports and continuous verification for final-round and offer-stage interviews, not every screen.
- Communicate the "why" clearly to student candidates — framing it as fairness to all applicants, not distrust of any individual, tends to land well with this audience.
FAQ
Is this overkill for unpaid or low-stakes intern roles? It's proportional — a light identity and browser-lockdown check adds minimal friction and cost even at high volume, while catching the AI-assisted cheating that's now common in early-career technical screens.
Do students push back on proctoring more than experienced candidates? Some do initially, but clear disclosure and framing around fairness (every applicant gets the same check) generally resolves the concern.
Should this apply to non-technical internships too? Yes, at a lighter level — identity verification alone is worth applying broadly; heavier monitoring makes more sense for timed technical assessments specifically.
By Pinal Dave Last updated: 2026-08-03