What an online assessment is checking, section by section

Sixty-two of the 494 listings live on HireSetu on 22 October 2026 mentioned the hiring process somewhere in their text. Read them and nearly all of those lines turn out to be one of two things: an offer to arrange accommodations during interviews, or a warning that the company never charges a fee. Only a few describe a step you will go through. Turing lays out a 75-minute evaluation, a 60-minute technical interview followed by a short cultural conversation. Marvell warns that using AI tools in an interview without the interviewer's say-so means disqualification. Hitachi Energy says it uses automated and AI-supported tools in recruitment.

So the online assessment, the first real filter in most fresher hiring, is the part of the process listings leave out. It usually arrives as an email with a link and a window of a day or two, and the first time many candidates see its format is when the timer starts. Knowing what each section is screening for changes how you prepare.

The sections, and what each one is looking for

Two details on the instructions page decide more than candidates expect. The first is sectional cut-offs: some tests require a minimum score in every section, so a brilliant coding score cannot rescue a weak verbal one. The second is negative marking. Where wrong answers cost marks, a guess is a bet; where they do not, a blank is wasted. Read that page slowly before you click Start, because it is the only place either rule is written down.

How the coding section is graded

Your program is run against test cases you cannot see. The two or three examples shown with the problem are usually among the easiest. Hidden cases check empty inputs, single elements, duplicates, negative numbers and, most often, very large inputs. On many platforms each hidden case earns its own share of the marks, so a solution that passes six of ten cases scores something, and one that passes the visible examples only may score very little.

Large inputs are where most freshers lose marks without noticing. Take a problem that asks how many pairs in an array add up to a target, with up to 100,000 numbers. Checking every pair means around five billion comparisons, which will not finish inside the usual time limit of a second or two. Storing the numbers you have seen in a hash map and checking for each one's partner takes about 100,000 steps. Both programs give the right answer on the visible examples. Only the second passes the large hidden cases.

Where coding marks quietly go missing

01

Reading input the slow way

For large inputs, line-by-line reading in some languages is slow enough to time out. Learn the fast input method for the language you use before test day.

02

Integer overflow

Sums and products of large numbers overflow a 32-bit integer. Use a 64-bit type whenever totals can grow, and check the constraints to see if they can.

03

Printing extra text

Graders compare output exactly. A stray "Answer:" or a debugging print in the final submission fails every case.

04

Stopping at the samples

Before submitting, run your own tests: empty input, one element, all elements equal, the largest allowed size.

Proctoring

Most remote tests watch you through the webcam, check that you stay in a full-screen window, and log tab switches. Some record audio, ask you to show the room by turning the camera, or compare your face with an ID card at the start. The rules differ by platform and are listed before the test begins. Treat any flag as costly: a switched tab or a second face in the frame can mark the attempt for review, and a reviewer has no way of knowing your sibling walked in by accident.

The evening before a remote test

• Open the system-check link the platform sent and complete it on the same laptop and network you will use.
• Charge the laptop and keep the charger plugged in. Turn off automatic updates.
• Keep a phone hotspot ready as a backup connection, and know how to switch to it in under a minute.
• Choose a room with a plain wall behind you, steady light on your face and a door you can close.
• Keep your college ID or a government ID beside you, and rough paper if the rules allow it.
• Close every other application, including the ones in the system tray.

Two weeks of practice, without a course

1. 1. Days 1 to 4

   Quantitative aptitude in timed sets. Keep an error log of every wrong answer with the reason: misread, slow, or did not know the method.

2. 2. Days 5 to 7

   Logical reasoning and verbal, alternating. Draw every arrangement problem. Read one long article a day.

3. 3. Every day

   Two coding problems from arrays, strings, hashing, sorting and simple recursion, each timed and then tested with your own edge cases.

4. 4. Day 8

   One full mock test under real conditions: timer, webcam on, no breaks. Mark which section ran out of time.

5. 5. Days 9 to 13

   Spend the time on whichever section the mock exposed and skip the one you enjoy.

6. 6. Day 14

   A second full mock, then rest. Tired candidates misread questions they would otherwise get right.

After each real test, write down which sections it had, how long each was and where you ran short of time, but not the questions themselves, which most test terms forbid sharing. Three tests in, that note will tell you more about what to practise than any list of "most asked questions".