--- title: "“Don’t Expect Candidates to Have Everything Memorized”, the Dos and Don’ts of Cheating Prevention With Nathan Sutter | CoderPad" description: "Sure, you want to prevent cheating. But you also want to feel good about your hiring process. So how do you do that?" canonical: "https://coderpad.io/blog/hiring-developers/dos-and-donts-cheating-prevention-nathan-sutter/" last_modified: "2026-04-15 16:19:21" --- [Back to blog](https://coderpad.io/blog/) # “Don’t Expect Candidates to Have Everything Memorized”, the Dos and Don’ts of Cheating Prevention With Nathan Sutter June 3, 2024 5 Minute Read By Nathalie Figuière [Hiring Developers](https://coderpad.io/blog/hiring-developers/) [Interviewing](https://coderpad.io/blog/interviewing/) Sure, you want to prevent cheating. But you also want to feel good about your hiring process. I recently chatted with [Nathan Sutter, VP of Engineering](https://www.linkedin.com/in/nathansutter/), about cheating, interviewing, and candidate experience. We put together a list of dos and don’ts to help you hire developers and prevent cheating in the “best possible way” (i.e in a way that won’t send developers running for the hills OR make you feel like an unfair, out-of-touch paranoiac). > 🔖 Related read: If you want to read more about how to prevent, mitigate and detect cheating within your tech hiring process, [check this out](https://coderpad.io/blog/hiring-developers/18-features-your-tech-assessment-tool-should-have-to-prevent-cheating/). ## The dos of cheating prevention ### Do: be transparent with candidates It can be tempting to keep candidates in the dark. Indeed, some recruiters worry that any information candidates receive will be used to better prepare a cheating offense. We disagree. The more a candidate knows about the hiring process, the better. Aim to clearly communicate what you’re looking to assess and why. We also strongly recommend that you communicate, ahead of time, what tools candidates can or can’t use and why. > “Be as clear and as transparent as possible. Candidates should know what they’re walking into.” For example, if you consider that using ChatGPT during a [live coding interview](https://coderpad.io/platform/coding-interviews/) is fair game—say so! Then, go on to explain that you encourage the use of ChatGPT because you want to provide a realistic interview experience (for example). Candidates will respect you all the more for your transparency. A well-prepared, well-informed candidate is less likely to cheat because: 1. You’ve shown candor and started to build trust and engagement. 2. They’re confident that you’re not trying to “catch them out” or spring any surprises on them. They’re less likely to panic. 3. They’re “onboard” with your evaluation process. They haven’t been made to feel that they’re simply “jumping through hoops”. You’ve shown that you respect their time and value skills above other, less objective, criteria. ### Do: create a realistic interview setting Always strive to simulate your working environment during the interview process. > “Create an environment that is as close to working with this person as possible. Give candidates the tools that you would give them on the job.” Whether it’s tools (as mentioned above), the IDE, or the space to ask questions, it’s important to provide developers with a familiar and realistic interview setting. The more comfortable and confident they feel, the less likely they are to look for external, unauthorized support (asking someone to take the interview in their place, for example). ### Do: align and engage your hiring team Recruitment is not a one-(wo)man show. It takes a team. > “It’s really important that your hiring manager specifically is working very, very closely with talent acquisition, and that you’re on the same page with what cheating is.” It’s important to define what cheating means to your organization. Clearly list expectations and decide what’s allowed and what’s not. All stakeholders should commit to this shared position. For example, here at CoderPad, we don’t consider that using ChatGPT as a supporting tool during a test or interview is cheating. We do, however, consider that asking a friend to take a [pre-employment assessment](https://coderpad.io/platform/technical-screening/) in your place, is cheating. It’s just as important to make sure that anyone involved in the hiring process is fully engaged and, better still, trained in inclusivity, hiring bias and structured interviewing. Why? Because the better the interview experience, the less likely candidates are to want to cheat. > 🔖 Related read: [How Talent Acquisition Can Empower Engineering Hiring Managers to Be Better Interviewers](https://coderpad.io/blog/hiring-developers/how-talent-acquisition-can-empower-engineering-hiring-managers-to-be-better-interviewers/) ## The don’ts of cheating prevention ### Don’t: over-rely on proctoring > “Adding proctoring for all assessments is not something I would recommend. In some geographies, proctoring is a norm, it’s expected; in other geographies, it’s absolutely not.” Proctoring can be both a powerful anti-cheat tool, and a real obstacle for candidates. When deciding whether or not you activate proctoring for your online assessments, take into account elements such as: - Seniority of the role you’re hiring for - The market and culture you’re hiring in - Expected number of applicants for the role - Your available internal resources As a general rule, we recommend that you avoid using proctoring excessively. However, if you do decide to enable proctoring, you should do so for every candidate applying for a given position (per-test, not per-candidate). > 🎬 Related watch: [How to Prevent and Detect Cheating in Your Tech Recruitment Process](https://coderpad.io/events/how-to-prevent-and-detect-cheating-in-your-tech-recruitment-process/) ### Don’t: expect memorization Do not expect candidates to memorize everything; focus on problem-solving skills instead. > “For as long as I’ve been writing code, we’ve had tools to help us remember things. Our toolsets are becoming more complex over time, so don’t expect candidates to have everything memorized. Memorization isn’t a good indicator of how well a potential engineer will solve problems.” ### Don’t: present overly complex problems The harder the questions, the harder it is to cheat. Right? No. Asking candidates to work on overly difficult development tasks will not get you better hiring results. > “If it’s a 45-minute interview, give them a problem they can realistically solve in 45 minutes, not something that would take two or three hours on their own.” Provide clear instructions, and have candidates work on something as close as possible to an on-the-job problem, that can realistically be completed in the allotted time. Expecting candidates to over perform in an interview setting does not set you, or your candidate, up for success. ### Don’t: create an adversarial environment or an overcomplicated process No good will come from throwing an endless amount of steps and obstacles at candidates. You may well drive the cheaters away, but you’ll drive everyone else away too. Instead, focus on enabling candidates to succeed rather than tripping them up. > “Ask yourself, how do I enable somebody to succeed, not catch somebody out.” We absolutely recommend that candidate experience remain your north star. Make it as easy as possible for candidates to navigate your hiring process and, above all, demonstrate their skills. ### Don’t: make rash decisions or accusations Lastly, don’t jump to any conclusions. Any one indicator of unusual or suspicious behavior is not necessarily enough to label a candidate as a cheater. > “For example, some engineers, being introverted, might not feel comfortable being on camera for the first interview. I wouldn’t take this as a red flag indicating cheating. Instead, focus on being engaged and ensuring the candidate can walk you through their solution in real time.” Lead with curiosity, ask questions. There may well be a perfectly reasonable explanation. ## Subscribe for more CoderPad insights ## Trending Articles Previous slide Next slide [Hiring Developers ## Generative AI and the Future of Technical Interviews: Addressing Concerns of Increased Cheating The invention of ChatGPT has raised no shortage of questions. These questions seem mostly to be grounded in fear – anxiety that ChatGPT will replace the need for our jobs, our unique skills, and our need to think. Read the post](https://coderpad.io/blog/hiring-developers/chatgpt-and-the-future-of-technical-interviews-addressing-concerns-of-increased-cheating/) [Hiring Developers ## 18 Features Your Tech Assessment Tool Should Have to Prevent Cheating This article is an overview of “anti-cheat” features that can help you prevent, detect and mitigate cheating attempts within your candidate assessment process. Read the post](https://coderpad.io/blog/hiring-developers/18-features-your-tech-assessment-tool-should-have-to-prevent-cheating/) [Interviewing ## 2 Effective Interview Questions to Ask Your Full-Stack Developer Candidates Choosing the appropriate interview questions for full-stack engineering candidates can be a daunting task. This article presents two premium questions to consider for your upcoming full-stack engineering interviews. Read the post](https://coderpad.io/blog/interviewing/2-effective-interview-questions-to-ask-your-full-stack-developer-candidates/) [Hiring Developers ## How to Hire for AI Fluency Now That It’s a Critical Skill Based on the CoderPad webinar featuring Bayo Ojuri (CoderPad), Bonnie Dilber (Zapier), and Melany Austin (GoDaddy). “AI fluency” has quietly become a line item in nearly every technical job description. The problem: most teams added the requirement long before they had a reliable way to assess it. You can ask a candidate whether they use […] Read the post](https://coderpad.io/blog/hiring-developers/how-to-hire-for-ai-fluency-now-that-its-a-critical-skill/) [Hiring Developers ## Hot Takes on Hiring: “AI Fluency” Is a Myth Our CEO, Amanda Richardson, and our Head of Product, Frank Hauben, can’t agree on anything else. We put Amanda and Frank on camera, handed them five spicy hot takes about AI in hiring, and told them not to sit on the fence. They sat on the fence anyway. Here’s what they actually fought about. Amanda […] Read the post](https://coderpad.io/blog/hiring-developers/hot-takes-on-hiring-ai-fluency-is-a-myth/) [Hiring Developers ## 5 Unfiltered Takes on AI That Engineering Leaders Actually Believe We put a room full of senior engineering leaders together, took away the slides, added beer, and asked them to say the thing they’d never put in a LinkedIn post. No PR-approved talking points, no vendor gloss, just people who ship for a living telling the truth about what AI is doing inside their orgs […] Read the post](https://coderpad.io/blog/hiring-developers/5-unfiltered-takes-on-ai-that-engineering-leaders-actually-believe/) [Hiring Developers ## Your Developer Interview Loop Is a Year Old. Is It Still Finding Your Best Candidates? A YC-backed founder called me last week with some good questions. His 20-person startup hadn’t hired an engineer in over a year. Now they’re opening reqs again, and instead of just dusting off the old loop, he wanted to understand how interviews had changed and if candidates were ready for AI interviews. His process — […] Read the post](https://coderpad.io/blog/hiring-developers/your-developer-interview-loop-is-a-year-old-is-it-still-finding-your-best-candidates/) [Hiring Developers ## AI Fluency Is the New Technical Skill. Is Your Hiring Process Ready? Artificial intelligence has fundamentally changed software development. Developers are no longer working in isolation, writing every line of code from memory. AI has become part of the engineering workflow, helping developers brainstorm approaches, generate boilerplate code, and debug complex issues. The question isn’t whether engineers are using AI. It’s how effectively they’re using it. Hiring […] Read the post](https://coderpad.io/blog/hiring-developers/ai-fluency-is-the-new-technical-skill-is-your-hiring-process-ready/) [Hiring Developers ## AI Didn’t Kill Entry Level Hiring. Bad Screening Did. For the last two years, the narrative has been loud, confident, and mostly wrong: AI is coming for entry level engineering jobs. The story goes something like this: If AI can write code, summarize docs, generate tests, and debug basic issues, why would companies still hire junior engineers? It sounds logical. It is also incomplete. […] Read the post](https://coderpad.io/blog/hiring-developers/ai-didnt-kill-entry-level-hiring-bad-screening-did/) [Hiring Developers ## The Resume Is Dead. Most Teams Just Haven’t Admitted It Yet. Resumes made sense when applying for a job took real effort. That era is over. AI lets candidates apply to hundreds of roles in the time it once took to write a single cover letter. Employer-side AI systems process the flood. The result is a hiring funnel built almost entirely on artificial signals, where the […] Read the post](https://coderpad.io/blog/hiring-developers/the-resume-is-dead-most-teams-just-havent-admitted-it-yet/) [Hiring Developers ## Is Your Technical Hiring Process Screening Out Great Engineers? The short answer: Many technical hiring processes are doing the latter. High-friction interview loops, live coding under observation, and AI-restrictive assessments are measuring interview performance, not job performance. The fix isn’t rebuilding from scratch — it’s auditing whether your process measures engineering capability or something else entirely. If you attended our recent webinar with CoderPad […] Read the post](https://coderpad.io/blog/hiring-developers/is-your-technical-hiring-process-screening-out-great-engineers/) [Hiring Developers ## Junior Developers Are Your Strategic Advantage—If You Can Actually Evaluate Them Campus recruiting season arrives the same way every year: hundreds of applications, a narrow window, and a process that was never designed for this much volume or this much pressure. Meanwhile, the definition of “technical skill” is actively shifting—AI-polished resumes have made traditional screening nearly meaningless, and the skills that predict junior developer success look […] Read the post](https://coderpad.io/blog/hiring-developers/junior-developers-are-your-strategic-advantage-if-you-can-actually-evaluate-them/) ## Hire with confidence. See why engineering teams trust CoderPad to evaluate developers with realistic, AI-ready hiring workflows. [Request a demo](https://coderpad.io/sales/)