How to Detect AI Cheating in a Data Analyst SQL and Excel Test

A data analyst SQL and Excel test shows AI-cheating signals when a complex nested query or an advanced Excel formula appears fully formed with no iterative draft-and-error cycle, and the candidate can't explain a specific clause or function when asked — a sign the query or formula came from a browser AI tab or an in-app Copilot rather than live authorship.

Threat Model, Tells, and Evidence to Capture

Threat ModelObservable TellEvidence to Capture
AI-generated SQL query pasted wholesale into the editorCorrect, complex subquery or CTE appears on the first attempt with no syntax-error iteration typical of live SQL writingKeystroke-vs-paste ratio; query-editor edit history
Excel Copilot or AI chat generating formulasFormula bar shows a full formula appearing via paste rather than incremental typingFormula edit-history timeline; clipboard paste-volume telemetry
Screen-share to a remote helper solving the problem liveCandidate's mouse/cursor pauses match a pattern of reading instructions rather than working independentlyScreen recording of the authoring process; tab and window-focus log
Function or clause used is beyond the candidate's stated experience levelAdvanced window functions, CTEs, or array formulas appear despite a resume showing only basic SQL/Excel useCross-reference of resume-stated skill level against test artifact complexity

Interviewer Script

  • Mid-test, ask the candidate to modify their own query live — add a new filter, join an additional table, or change an aggregation. A genuine author does this quickly and explains the change as they go; a copier stalls or produces another suspiciously clean paste.
  • "Why did you use a window function here instead of a self-join?" A real author has a reason; a pasted answer usually gets a generic or evasive response.
  • For Excel, ask the candidate to break their own formula on purpose (introduce a circular reference or an off-by-one range) and then fix it live.
  • If the test is proctored asynchronously, route any session with a low keystroke-to-output ratio to a short live follow-up before scoring it.

FAQs

Is it fair to flag advanced SQL as suspicious — some analysts really are that skilled? Skill level alone isn't the flag. The tell is the pattern — a complete, correct query appearing instantly with no iteration — combined with the inability to explain or modify it live afterward.

What if the test allows an open-book or "use any resource" policy? Even in open-book tests, the goal is usually to verify the candidate can apply what they look up. The live-modification script above still separates genuine research-and-apply behavior from a fully AI-generated answer.

How does this compare to a Financial Analyst Excel test? The underlying signals — paste ratio, formula edit history, live-modification ability — are the same, but financial modeling formulas (DCF, amortization schedules) have different "too advanced for the stated level" thresholds than typical analyst reporting formulas.

Can browser extensions inject answers directly into a web-based SQL editor? Yes, which is why an extension inventory scan alongside keystroke telemetry is important — a paste-ratio check alone can miss extension-based injection that mimics typing.

How often does this kind of cheating show up across technical assessments generally? CodeSignal reported cheating attempts on its assessments roughly doubling year over year, and SQL/Excel skills tests share the same unsupervised, browser-based structure that makes coding tests a high-risk format.

Related Guides

Get the Evidence Before You Extend an Offer

SQL and Excel skills tests run entirely inside a browser or desktop app, and that's exactly where paste events, formula-edit history, and tab-switching leave their trail. Neuroxa Browser Proctoring captures all of it automatically, so your team gets an authorship-confidence score instead of just a final answer key match.