Question 1

How long should a coding test be?

Accepted Answer

For most roles, 45–60 minutes is the safe range. Long tests don't automatically give better signals; they mostly increase drop-offs. If you need more depth, add a second short task (e.g., debugging) instead of stretching a single test to 2 hours.

Question 2

Should we allow AI tools (such as ChatGPT/Copilot) in coding assessments?

Accepted Answer

Allow them only if you also allow them on the job, and you know what you're scoring. If AI is allowed, don't score "who can generate code fastest." Score how they verify, debug, and explain choices. If AI isn't allowed, say it clearly in the instructions and explain why.

Question 3

Should I pay candidates for take-home assignments?

Accepted Answer

If the take-home is more than 3 hours, yes, consider a small honorarium. That's the fairest approach, and it reduces ghosting. If you don't want to pay, keep it under 90 minutes and keep the scope clear. Senior candidates often drop out when they see a long, unpaid project before they've even met the team.

Question 4

How do I stop candidates from using ChatGPT or Copilot during the test?

Accepted Answer

You can reduce it, but you can't fully stop it. The better approach is to design the test so AI can't "finish it" on its own. Add at least one debugging or code review task, and ask candidates to briefly explain their choices. If you need stronger control for high-stakes roles, use proctoring signals, but judge the overall behavior, not a single tab switch.

Question 5

How do you prevent cheating without over-proctoring?

Accepted Answer

Start with light controls that don't annoy genuine candidates, like question randomization and clear time windows. If the role is higher-stakes, add signals such as tab-switch and copy/paste flags. Use strict proctoring only when it's truly needed. Most importantly, don't treat one alert as proof. Look for patterns across the whole attempt.

programming skills test

How to administer programming tests effectively

How to administer programming tests effectively

Cut through the Noise, Hire with Clarity

Before you go. Want to see how top teams assess talent?