Online Coding Assessment Tips: HackerRank, CoderPad and Timed Tests

How online assessments work

Many companies screen candidates with a timed coding test before any interview. You are given one to four problems, a fixed time limit (often 60–120 minutes) and an online editor. Your code runs against visible and hidden test cases, and your score depends on how many pass, sometimes also on speed and code quality. Platforms commonly used include HackerRank, HackerEarth, Codility, CodeSignal, Mettl and custom company portals.

The test is a filter, so the goal is consistency: solve what you can solve, and do not lose marks to avoidable mistakes.

Before test day

1. Practise on the same kind of platform. Get used to reading input from standard input and printing exact output.
2. Choose one language and know its input and output idioms well (fast reading of integers, splitting lines, printing lists).
3. Learn the boilerplate for your language so you can type it from memory. For example, in Python: n = int(input()), arr = list(map(int, input().split())).
4. Practise under time limits: 2–3 mock tests with a real timer.
5. Check technical requirements: browser, camera, microphone, screen sharing, stable internet, charged laptop, a quiet room, and ID if required.
6. Read the instructions email twice. Rules about proctoring, allowed tools and the number of attempts vary.

The first five minutes of the test

• Scan all problems before starting. Rank them by difficulty.
• Start with the one you can solve fastest to secure marks early.
• Note the time allocated per problem, for example 25 minutes each for three problems with a buffer.

The method for every problem

1. Read the statement twice. Note the input format, constraints and sample output.
2. Look at the constraints. If n can be 10⁵, an O(n²) solution will time out; you need about O(n log n) or O(n). If n is 20, brute force or backtracking may be fine.
3. Work through the sample by hand.
4. Pick the approach (hash map, two pointers, sorting, binary search, BFS, dynamic programming).
5. Write the code carefully, with clear names.
6. Test with the samples, then with edge cases: smallest input, all equal values, already sorted, negatives, maximum size.
7. Check output formatting. Extra spaces, missing line breaks or printing extra text fail tests.

Passing hidden test cases

Hidden tests catch what samples do not. Common causes of failures:

• Time limit exceeded from an inefficient algorithm. Revisit the constraints.
• Integer overflow in languages like Java and C++ when sums or products get large. Use long.
• Off-by-one errors in loops and indexes
• Empty or single-element input
• Duplicates and negative numbers
• Reading input incorrectly, for example assuming one line when values are on several
• Recursion depth problems in Python for deep recursion, so consider an iterative version

Time management

• If you are stuck for 10 minutes with no progress, move on and come back.
• A partially working solution scores partial marks on many platforms. Submit a brute-force solution that passes some cases before searching for a perfect one.
• Reserve the last 10 minutes for re-running tests and checking you submitted every problem.
• Do not rewrite your solution completely in the final minutes unless you are sure.

Proctoring rules

Many tests record your screen, webcam and microphone, and detect tab switches.

• Keep the test window active; do not open other tabs or apps
• Sit alone in a well-lit room, face the camera and keep your phone away
• Do not look away repeatedly or read aloud
• Never use unauthorised help or share the questions. Cheating can lead to a ban, and companies often share data about flagged candidates.

Quick checklist

• Language boilerplate memorised
• Mock tests done under a timer
• Equipment and internet tested
• ID and instructions email ready
• A plan: easiest first, 10-minute stuck rule, final review

Where to go from here

Build the underlying skill with the 12-week DSA study plan, review the technical interview checklist for the interview rounds, and see how test-based hiring works at Infosys and banks and fintech firms.

Latest changes (2025–2026)

Updated 28 October 2026.

• Read the AI rules first. Some assessments now allow a limited AI assistant (Goldman Sachs's diagnostics challenge, for example), while others forbid any outside help (Microsoft and, reportedly, Amazon). Using AI where it is not allowed can disqualify you.
• Expect proctoring: camera on, full-screen mode, tab-switch detection and sometimes an ID check or room scan.
• Practise debugging. Some formats give you a broken program to fix instead of a blank editor.
• Explain your code. If a later round is in person, you may be asked to rewrite or explain your solution.

For the wider picture, read how tech hiring has changed in 2025–2026.