Home
/
Blog
/
AI Recruiting
/
6 Ways Candidates Try To Outsmart A Remote Proctored Assessment

6 Ways Candidates Try To Outsmart A Remote Proctored Assessment

Author
Keerthi Kumar
Calendar Icon
November 20, 2020
Timer Icon
3 min read
Share

Tech hiring has undergone a radical transformation with take-home assessments gaining popularity over traditional methods in recent times. Since even a single instance of candidate malpractice can taint the efficacy of the entire test process, it stands to reason that take-home assessments and remote interviews would never have gained their current credibility without a foolproof online proctoring mechanism.

Proctoring is crucial to validate a candidate’s authenticity and integrity. Without some sort of online supervision, it would be impossible to claim that assessment platforms such as HackerEarth offer accurate results and candidate analysis.

In short,

Standardized Developer Hiring = Customized and Intuitive Coding Tests + Robust Proctoring

So, without further ado, let’s take a look at the 6 most commonly deployed tricks your assessment tool needs to guard against, shall we?

#1. Switching tabs to get online assistance/reference during a test

El switch-a-tab-aroo.

Switching tabs to get online assistance/reference during a coding test. Proctoring tips on how to deal with such a case

This is a classic one, and probably the most obvious example in our list. A lot of candidates happily assume that interviewers and creators of assessment software blindly trust in a candidate’s ready inclination to always take the moral high ground. But the angelic souls who create such software are well aware of this age-old technique and have hence installed divine software intervention to guard against it. #NotAllDevelopers

Fixes: Full-screen mode, Custom timer on MCQs, Automatic log-out.

#2. Copy-pasting code from another computer or from the web

El copy-paste-o.

Copy-pasting code from another computer or from the web. Proctoring tip 2 on how to handle this

Another age-old trick in the digital book is the incredibly humble copy-paste. With the latest upgrades in Windows and Mac operating systems, candidates can, in fact, store and keep-at-the-ready, not one but a string of copied texts. You can access these copied pieces of code with just a couple of keystrokes. This includes productivity tools, messengers, data and word processing apps, Mac cleaners, and security software.

Fixes: Copy-paste lock, Full-screen mode.

#3. Getting other users to take the test on their computer

El Imperson-anaa-tor.

How proctoring can detect other users trying to take the coding test on their computer.

What’s the best part about take-home coding tests? Well, it doesn’t necessarily have to be you that’s taking them. Your coding prodigy of a best friend, or perhaps that bespectacled kid in class who hibernates in the library, could take them for you, all for a quick buck.

Fixes: Randomized webcam snapshots, IP Address Lock, Automatic impersonation detection.

Also read: Importance Of Online Proctoring In University Hiring

#4. Moving away from the webcam to look into another laptop/screen/book.

El dos screen-o.

Moving away from the webcam to look into another laptop/screen/book during a coding assessment.

A lot of candidates, unfortunately, give in to the overpowering urge to sneak a peek into another screen or a book. They’re often prepared with a secondary device that’s kept hidden from the web camera’s line of sight. So, it’s extremely easy for them to access these hidden resources unbeknownst to the system. What’s more, the screens of neighboring candidates are also a potential cause for concern.

Fixes: Randomized webcam snapshots, Plagiarism checker, Automatic mobile phone detection.

#5. Having another person in the room who can read out answers and solutions for you

El dos candidate-o.

Having another person in the room who can read out answers and solutions for you (during a coding test).

A good friend will bail you out of jail. But a best friend will be sitting in the cell with you, going “Wow, wasn’t that something?”.

God bless friends who will, more than willingly, aid and abet candidates in a malpractice attempt. Candidates take advantage of the fact that there aren’t any audio recording devices embedded in the test system. So, they can either try taking the assistance of a gifted comrade in the case of remote assessments, or others who are also taking the test if using an onsite group interview room.

Fixes: Randomized webcam snapshots, Plagiarism checker.

#6. Restroom breaks

El missing suspect-o.

Restroom breaks during coding test.

The final and the most elementary (quite literally) of all is the innocent nature’s call card. In the case of remote examinations, the computer and its camera basically account for all of your exam halls, and everything that’s out of the webcam’s line of sight is not. For the briefest time, you’re Alice in ‘Wander’land, and the whole house is your deception oyster.

Fixes: Randomized webcam snapshots, Custom timer on MCQs.

Also read: 5 Must-Have Proctoring Tips For A Developer Assessment Platform

9 Ways They Aren’t. (HackerEarth Proctoring Fixes In Detail)

If you were worried about what you read above, then allow yourself to breathe a sigh of relief. HackerEarth Assessments has in-built proctoring features to ensure that every assessment taken on our platform is monitored to ensure authenticity. Here are the most important ones:

#1. Randomized webcam snapshots – 2 every minute

This is the biggest and most potent gun we have in our arsenal. The reason this ranks the highest in our list is that, unlike the other features which are announced by the system, it is easy to forget about this functionality. Randomized webcam snapshots basically pick up any sort of malpractice attempt, ranging from peering into a second screen to verbal communication with another person in the room.

#2. Custom timers on multiple choice questions

This is based on the premise that it takes time to look for or seek any form of assistance. So, a timer on the MCQ questions is a good way to keep the pressure on the candidate, discouraging them from wasting any time scouring the internet or elsewhere for a solution. The other logic behind this feature is that the short amount of time will simply not allow you to cheat, as it just won’t be humanly possible to look for hints, do your calculations, and finally punch them in.

#3. Plagiarism checker. All submissions need to be unique

Another heavy piece of artillery in our war against interview malpractices is our system’s inbuilt plagiarism checker. This advanced AI-assisted function is every recruiter’s dream come true. It investigates a candidate’s code against all the other applicant submissions for the same test.

Even the remotest match in code is picked up by the system immediately and the respective administrator is promptly notified.

Also read: 3 Things To Know About Remote Proctoring

HackerEarth add-ons for robust proctoring

Here are some additional proctoring fixes that further bulletproof our assessments, making it one of the most reliable and accurate sources of remote technical candidate evaluations out there in the market today. Learn more about them in detail in our support article, here.

#4. Restrict test access for certain IP addresses.

#5. Disable the Copy and Paste feature in the code editor.

#6. Negative marking could be activated during MCQ questions.

#7. Automatic impersonation detection (plus) mobile phone detection.

#8. Automatically log a candidate out upon leaving the test environment.

#9. Restrict candidates to full-screen mode for the entirety of the assessment.


Also read: Screen Candidates Better With HackerEarth's Proctoring Feature

Automated invigilation made easy with HackerEarth!

Like with all regulatory orders found in society, there will always be attempts at finding new and innovative ways to beat the system. That’s just natural human behavior, and we fully condone it.

The way we look at it - it’s really a game of who’s the smarter fox in the jungle. In order to help recruiters stay on top, we constantly update our system to stay ahead of the curve. Our team vigilantly looks for dodgy trends much ahead of the competition and anticipates candidate behavior to create smarter features.

HackerEarth has a 7-million-strong developer community, and we know how easy it is for a few bad apples to give the entire community a bad rap. Our goal has always been to create a system that provides developers with fair and objective assessments and helps recruiters pick the best talent. The proctoring features in our Assessment platform do both with equal ease.
Subscribe to the HackerEarth blog and enrich your monthly reading with our free e-newsletter - Fresh, insightful, and awesome articles straight into your inbox from around the tech recruiting world!

Subscribe to The HackerEarth Blog

Get expert tips, hacks, and how-tos from the world of tech recruiting to stay on top of your hiring!

Author
Keerthi Kumar
Calendar Icon
November 20, 2020
Timer Icon
3 min read
Share

Hire top tech talent with our recruitment platform

Access Free Demo
Related reads

Discover more articles

Gain insights to optimize your developer recruitment process.

The Mobile Dev Hiring Landscape Just Changed

Revolutionizing Mobile Talent Hiring: The HackerEarth Advantage

The demand for mobile applications is exploding, but finding and verifying developers with proven, real-world skills is more difficult than ever. Traditional assessment methods often fall short, failing to replicate the complexities of modern mobile development.

Introducing a New Era in Mobile Assessment

At HackerEarth, we're closing this critical gap with two groundbreaking features, seamlessly integrated into our Full Stack IDE:

Article content

Now, assess mobile developers in their true native environment. Our enhanced Full Stack questions now offer full support for both Java and Kotlin, the core languages powering the Android ecosystem. This allows you to evaluate candidates on authentic, real-world app development skills, moving beyond theoretical knowledge to practical application.

Article content

Say goodbye to setup drama and tool-switching. Candidates can now build, test, and debug Android and React Native applications directly within the browser-based IDE. This seamless, in-browser experience provides a true-to-life evaluation, saving valuable time for both candidates and your hiring team.

Assess the Skills That Truly Matter

With native Android support, your assessments can now delve into a candidate's ability to write clean, efficient, and functional code in the languages professional developers use daily. Kotlin's rapid adoption makes proficiency in it a key indicator of a forward-thinking candidate ready for modern mobile development.

Breakup of Mobile development skills ~95% of mobile app dev happens through Java and Kotlin
This chart illustrates the importance of assessing proficiency in both modern (Kotlin) and established (Java) codebases.

Streamlining Your Assessment Workflow

The integrated mobile emulator fundamentally transforms the assessment process. By eliminating the friction of fragmented toolchains and complex local setups, we enable a faster, more effective evaluation and a superior candidate experience.

Old Fragmented Way vs. The New, Integrated Way
Visualize the stark difference: Our streamlined workflow removes technical hurdles, allowing candidates to focus purely on demonstrating their coding and problem-solving abilities.

Quantifiable Impact on Hiring Success

A seamless and authentic assessment environment isn't just a convenience, it's a powerful catalyst for efficiency and better hiring outcomes. By removing technical barriers, candidates can focus entirely on demonstrating their skills, leading to faster submissions and higher-quality signals for your recruiters and hiring managers.

A Better Experience for Everyone

Our new features are meticulously designed to benefit the entire hiring ecosystem:

For Recruiters & Hiring Managers:

  • Accurately assess real-world development skills.
  • Gain deeper insights into candidate proficiency.
  • Hire with greater confidence and speed.
  • Reduce candidate drop-off from technical friction.

For Candidates:

  • Enjoy a seamless, efficient assessment experience.
  • No need to switch between different tools or manage complex setups.
  • Focus purely on showcasing skills, not environment configurations.
  • Work in a powerful, professional-grade IDE.

Unlock a New Era of Mobile Talent Assessment

Stop guessing and start hiring the best mobile developers with confidence. Explore how HackerEarth can transform your tech recruiting.

Vibe Coding: Shaping the Future of Software

A New Era of Code

Vibe coding is a new method of using natural language prompts and AI tools to generate code. I have seen firsthand that this change makes software more accessible to everyone. In the past, being able to produce functional code was a strong advantage for developers. Today, when code is produced quickly through AI, the true value lies in designing, refining, and optimizing systems. Our role now goes beyond writing code; we must also ensure that our systems remain efficient and reliable.

From Machine Language to Natural Language

I recall the early days when every line of code was written manually. We progressed from machine language to high-level programming, and now we are beginning to interact with our tools using natural language. This development does not only increase speed but also changes how we approach problem solving. Product managers can now create working demos in hours instead of weeks, and founders have a clearer way of pitching their ideas with functional prototypes. It is important for us to rethink our role as developers and focus on architecture and system design rather than simply on typing c

The Promise and the Pitfalls

I have experienced both sides of vibe coding. In cases where the goal was to build a quick prototype or a simple internal tool, AI-generated code provided impressive results. Teams have been able to test new ideas and validate concepts much faster. However, when it comes to more complex systems that require careful planning and attention to detail, the output from AI can be problematic. I have seen situations where AI produces large volumes of code that become difficult to manage without significant human intervention.

AI-powered coding tools like GitHub Copilot and AWS’s Q Developer have demonstrated significant productivity gains. For instance, at the National Australia Bank, it’s reported that half of the production code is generated by Q Developer, allowing developers to focus on higher-level problem-solving . Similarly, platforms like Lovable enable non-coders to build viable tech businesses using natural language prompts, contributing to a shift where AI-generated code reduces the need for large engineering teams. However, there are challenges. AI-generated code can sometimes be verbose or lack the architectural discipline required for complex systems. While AI can rapidly produce prototypes or simple utilities, building large-scale systems still necessitates experienced engineers to refine and optimize the code.​

The Economic Impact

The democratization of code generation is altering the economic landscape of software development. As AI tools become more prevalent, the value of average coding skills may diminish, potentially affecting salaries for entry-level positions. Conversely, developers who excel in system design, architecture, and optimization are likely to see increased demand and compensation.​
Seizing the Opportunity

Vibe coding is most beneficial in areas such as rapid prototyping and building simple applications or internal tools. It frees up valuable time that we can then invest in higher-level tasks such as system architecture, security, and user experience. When used in the right context, AI becomes a helpful partner that accelerates the development process without replacing the need for skilled engineers.

This is revolutionizing our craft, much like the shift from machine language to assembly to high-level languages did in the past. AI can churn out code at lightning speed, but remember, “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” Use AI for rapid prototyping, but it’s your expertise that transforms raw output into robust, scalable software. By honing our skills in design and architecture, we ensure our work remains impactful and enduring. Let’s continue to learn, adapt, and build software that stands the test of time.​

Ready to streamline your recruitment process? Get a free demo to explore cutting-edge solutions and resources for your hiring needs.

Guide to Conducting Successful System Design Interviews in 2025

What is Systems Design?

Systems Design is an all encompassing term which encapsulates both frontend and backend components harmonized to define the overall architecture of a product.

Designing robust and scalable systems requires a deep understanding of application, architecture and their underlying components like networks, data, interfaces and modules.

Systems Design, in its essence, is a blueprint of how software and applications should work to meet specific goals. The multi-dimensional nature of this discipline makes it open-ended – as there is no single one-size-fits-all solution to a system design problem.

What is a System Design Interview?

Conducting a System Design interview requires recruiters to take an unconventional approach and look beyond right or wrong answers. Recruiters should aim for evaluating a candidate’s ‘systemic thinking’ skills across three key aspects:

How they navigate technical complexity and navigate uncertainty
How they meet expectations of scale, security and speed
How they focus on the bigger picture without losing sight of details

This assessment of the end-to-end thought process and a holistic approach to problem-solving is what the interview should focus on.

What are some common topics for a System Design Interview

System design interview questions are free-form and exploratory in nature where there is no right or best answer to a specific problem statement. Here are some common questions:

How would you approach the design of a social media app or video app?

What are some ways to design a search engine or a ticketing system?

How would you design an API for a payment gateway?

What are some trade-offs and constraints you will consider while designing systems?

What is your rationale for taking a particular approach to problem solving?

Usually, interviewers base the questions depending on the organization, its goals, key competitors and a candidate’s experience level.

For senior roles, the questions tend to focus on assessing the computational thinking, decision making and reasoning ability of a candidate. For entry level job interviews, the questions are designed to test the hard skills required for building a system architecture.

The Difference between a System Design Interview and a Coding Interview

If a coding interview is like a map that takes you from point A to Z – a systems design interview is like a compass which gives you a sense of the right direction.

Here are three key difference between the two:

Coding challenges follow a linear interviewing experience i.e. candidates are given a problem and interaction with recruiters is limited. System design interviews are more lateral and conversational, requiring active participation from interviewers.

Coding interviews or challenges focus on evaluating the technical acumen of a candidate whereas systems design interviews are oriented to assess problem solving and interpersonal skills.

Coding interviews are based on a right/wrong approach with ideal answers to problem statements while a systems design interview focuses on assessing the thought process and the ability to reason from first principles.

How to Conduct an Effective System Design Interview

One common mistake recruiters make is that they approach a system design interview with the expectations and preparation of a typical coding interview.
Here is a four step framework technical recruiters can follow to ensure a seamless and productive interview experience:

Step 1: Understand the subject at hand

  • Develop an understanding of basics of system design and architecture
  • Familiarize yourself with commonly asked systems design interview questions
  • Read about system design case studies for popular applications
  • Structure the questions and problems by increasing magnitude of difficulty

Step 2: Prepare for the interview

  • Plan the extent of the topics and scope of discussion in advance
  • Clearly define the evaluation criteria and communicate expectations
  • Quantify constraints, inputs, boundaries and assumptions
  • Establish the broader context and a detailed scope of the exercise

Step 3: Stay actively involved

  • Ask follow-up questions to challenge a solution
  • Probe candidates to gauge real-time logical reasoning skills
  • Make it a conversation and take notes of important pointers and outcomes
  • Guide candidates with hints and suggestions to steer them in the right direction

Step 4: Be a collaborator

  • Encourage candidates to explore and consider alternative solutions
  • Work with the candidate to drill the problem into smaller tasks
  • Provide context and supporting details to help candidates stay on track
  • Ask follow-up questions to learn about the candidate’s experience

Technical recruiters and hiring managers should aim for providing an environment of positive reinforcement, actionable feedback and encouragement to candidates.

Evaluation Rubric for Candidates

Facilitate Successful System Design Interview Experiences with FaceCode

FaceCode, HackerEarth’s intuitive and secure platform, empowers recruiters to conduct system design interviews in a live coding environment with HD video chat.

FaceCode comes with an interactive diagram board which makes it easier for interviewers to assess the design thinking skills and conduct communication assessments using a built-in library of diagram based questions.

With FaceCode, you can combine your feedback points with AI-powered insights to generate accurate, data-driven assessment reports in a breeze. Plus, you can access interview recordings and transcripts anytime to recall and trace back the interview experience.

Learn how FaceCode can help you conduct system design interviews and boost your hiring efficiency.

Top Products

Explore HackerEarth’s top products for Hiring & Innovation

Discover powerful tools designed to streamline hiring, assess talent efficiently, and run seamless hackathons. Explore HackerEarth’s top products that help businesses innovate and grow.
Frame
Hackathons
Engage global developers through innovation
Arrow
Frame 2
Assessments
AI-driven advanced coding assessments
Arrow
Frame 3
FaceCode
Real-time code editor for effective coding interviews
Arrow
Frame 4
L & D
Tailored learning paths for continuous assessments
Arrow
Get A Free Demo