How to take a coding test, in short: run the platform's system check and sample test a day early, read every task before you write a line, get a simple correct solution submitted first, then spend the rest of your time on edge cases and speed. Most automated tests score you on hidden test cases you never see, so the example that passes on screen proves very little. And on most platforms your last submitted or last run code is what gets graded when the timer hits zero, so submit early and often.
This guide walks through a typical online coding assessment from invite to final submit. The rules quoted here come from the official candidate help pages of HackerRank, Codility and CodeSignal, the three platforms most job seekers meet. Your test may have its own settings (time limit, languages, whether AI tools are allowed), so the invite email always wins over general advice.
Before the test: the setup that costs people points
Most bad test days start with a setup problem, not a coding problem. Fix these the day before.
Use a laptop or desktop and a current browser. HackerRank's pre test FAQ says tests must be taken on a PC or laptop, with phones and iPads not supported, and recommends the latest Chrome, Edge, Safari or Firefox.
Run the system check and the sample test. HackerRank offers a System Compatibility Check and a Sample Test on the test login page. Codility lets you take a demo task first, and its candidate interface notes say the real test does not start when the demo ends, so you can practice and then begin when you are ready. Use these. Learning where the Run button is and how input is read should not eat your timed minutes.
Plan for your internet dropping. HackerRank's campus hiring FAQ says submitted work is saved on its servers and you can log back in, but the timer keeps running while you are offline and the test cannot be retaken or extended after time is up. A phone hotspot ready to go is cheap insurance.
Expect proctoring and read the rules. Many tests now record your webcam and screen. HackerRank's desktop app, for example, asks you to close other applications, grant webcam access, confirm you have a single monitor and share your screen before the test starts, then runs in full screen. The same FAQ warns that switching tabs, copying and pasting, leaving the webcam frame or using screen sharing apps can get flagged when AI tracking is on. Codility's test report shows recruiters a timeline that marks when text was pasted into the editor, though Codility tells recruiters a paste alone does not mean cheating.
Find out whether AI help is allowed. This changed fast. Some newer HackerRank tasks let candidates use AI models inside the task and score how well they use them, while classic proctored tests treat outside tools as a violation. If the invite does not say, assume no outside help.
Step by step: how to take a coding test once the timer starts
Step 1: Read every task before you start coding
On CodeSignal's General Coding Assessment, all questions open as soon as the timer starts and you can solve them in any order. Codility and HackerRank tests also show you the full task list. Spend the first two or three minutes reading all of them. Rank them by how quickly you can get a correct answer, not by number. A guaranteed solve on an easy task beats a half finished hard one.
Step 2: Pin down the input, output and limits
Read the task statement twice and write down three things: the exact input format, the exact output format and the size limits. HackerRank's guide to answering coding questions explains that most programs read standard input and write standard output, and that scoring uses exact string matching. A stray space, an extra blank line or a debug print can fail a correct algorithm. If the task says arrays can hold up to a million items, that is a hint that a nested loop over every pair will time out.
Step 3: Submit a simple correct solution first
Write the plainest version that works, even if it is slow, then run it and save or submit it. This matters because of how time outs are handled. HackerRank's time out rules say code you typed but never ran or submitted is not evaluated; if you submitted, the latest submitted code counts. Codility's run out of time page says your code is saved and assessed when time runs out, but it has to compile to be evaluated. Either way, a working version in the system early is your safety net.
Step 4: Test like the grader will
The example on screen is not your score. Codility's automated scoring principles say the example test case does not count, every task has at least six graded test cases (often more), and your task score is the share you pass: fail 4 of 10 and you get 60 percent. HackerRank marks its hidden tests with a lock icon and hides their input and expected output.
So add your own custom inputs. Both platforms let you run your code on inputs you type in. Try these every time:
- The smallest legal input (an empty list, a single item, zero).
- Duplicates, negatives and values at the stated maximum.
- Already sorted and reverse sorted data.
- The largest size the task allows, to see whether it finishes.
Step 5: Make it fast enough
Many algorithm tasks score speed separately. Codility splits task scores into correctness (moderate inputs and corner cases) and performance (running time on increasingly large data sets), and its candidate tips post tells you to brush up on Big O notation because a working answer is not enough. HackerRank reports "Terminated due to timeout" when code misses the time limit, which differs by language. Once your simple version is submitted, look for the usual upgrades: a hash map instead of a repeated search, sorting once instead of in a loop, or two pointers instead of two nested loops.
Step 6: Clean up and submit again
Remove debug prints if the task expects printed output, run all the sample tests one more time and submit. Then move to the next task. Come back to improve only if time is left.
Time plan for a 70 minute, four question test
CodeSignal's General Coding Assessment page describes four questions of varying difficulty in 70 minutes, with outside IDEs not permitted, scored on correctness, speed, implementation and problem solving. Its technical brief lists the four focus areas as basic coding, data manipulation, implementation efficiency and problem solving. Here is one sensible way to split the time. It is a starting plan, not an official rule.
| Phase | Minutes | What to do |
|---|---|---|
| Read all four tasks | 3 to 5 | Rank them by how fast you can solve each one |
| Easiest task | 8 to 12 | Correct solution, run, submit |
| Second task | 12 to 15 | Correct solution, then edge cases |
| Hardest remaining task | 25 to 30 | Simple version first, then optimize |
| Last task or cleanup | Whatever is left | Partial solution beats a blank editor |
CodeSignal reports the result as an Assessment Score from 200 to 600, according to its score explainer, with higher scores meaning more questions completed. That is why solving three tasks fully usually helps more than four messy attempts.
How the main coding test platforms differ
| Platform | Where you usually meet it | What to know |
|---|---|---|
| HackerRank | Job screening tests, campus hiring | Exact output matching, hidden locked test cases, optional desktop app with strict proctoring |
| Codility | Job screening and interviews | Demo task before the real test, correctness and performance scores, code must compile when time ends |
| CodeSignal | General Coding Assessment shared with many employers | Four questions, 70 minutes, all questions open at once, score from 200 to 600 |
| TestGorilla | Skills test bundles for many roles | Programming tests sit next to cognitive, language and personality tests in one assessment |
| Gradescope | University courses | Instructors grade code assignments, sometimes with automatic tests, rather than employers screening candidates |
If you are on the hiring side and want to know how these platforms are built and priced, our AI assessment tools category lists them with notes.
Mistakes that sink otherwise good candidates
- Coding the hardest task first. You can run out of time with nothing submitted.
- Trusting the green check on the example. Codility's own FAQ includes the question "Why did I score 0% despite passing example test cases?" because it happens so often.
- Leaving debug output in. With exact matching, an extra print line can fail every hidden test.
- Switching languages halfway. HackerRank notes that changing the language resets the editor, so copy your code first.
- Pasting large blocks from elsewhere. It shows up on the report timeline and may break the test rules.
- Ignoring the stated limits. The input size tells you how fast your solution must be.
How to practice for a coding assessment test
Take each platform's free sample or demo test, since they match the real editor. Then practice timed sets: pick three or four problems, set a timer and follow the steps above, including writing your own edge case inputs. Review not just whether you solved the problem but where your time went. Most people find they lose minutes to input parsing and output formatting rather than to the algorithm itself.
If your interest is how AI models are tested on coding rather than how people are, see our guide to MMLU vs SWE-bench, which explains how coding benchmarks for models work.
FAQ
How do I take a coding test for the first time?
Open the invite link on a laptop or desktop, run the system check and take the sample or demo test before the real one. When the timer starts, read every task, submit a simple correct answer to the easiest task first, then test edge cases and improve speed.
What happens if I run out of time on a coding test?
It depends on the platform. On Codility, your code is saved and assessed when time runs out, but it must compile. On HackerRank, code you never ran or submitted is not evaluated, while your latest submission is. Submitting early protects you on both.
Why did I get a low score when my code passed the example?
Example tests usually do not count. The grade comes from hidden test cases that include edge cases and large inputs. A solution that is correct but slow can also fail performance tests by timing out.
Can I use my own IDE or Google during a coding test?
Check your invite. CodeSignal says outside IDEs are not permitted on the General Coding Assessment, and proctored HackerRank tests flag tab switching and copy and paste. Some newer tasks allow AI tools on purpose, and the test instructions will say so.
How is the CodeSignal General Coding Assessment scored?
It has four questions in 70 minutes, scored on correctness, speed, implementation and problem solving. The result is an Assessment Score from 200 to 600, and higher scores mean more questions completed.
Is there a free coding assessment test I can practice on?
Yes. HackerRank's Sample Test and Codility's demo task are free and run in the same editor as real tests, so they are the best warm up before an actual assessment.
