Cracking the Aptitude and Coding Round at Mass Recruiters

The round that ends most people's placement season

At a mass recruiter, thousands of candidates apply for one hiring drive. Nobody is reading thousands of resumes. The first thing that happens is a timed online test, and the large majority of applicants are gone at the end of it — before a human has looked at a single project, CGPA or certificate.

That is the uncomfortable shape of it. Your portfolio does not matter yet. Your communication does not matter yet. What matters is whether you can solve a moderate percentage question in ninety seconds and write a working loop under time pressure.

The good news is in the same sentence. This filter measures something you can train. It is not an IQ test, whatever it feels like. It is a test of pattern recognition and speed, and both respond to practice in a way very few things in your life will.

What these rounds are actually testing

Not intelligence. Three things:

1. Speed. You usually get somewhere around a minute per question. The maths is school-level. The difficulty is entirely in the clock.
2. Pattern recall. The same forty or fifty question types repeat, year after year, company after company. Someone who has seen a question type before solves it in forty seconds. Someone meeting it for the first time takes four minutes and gets it wrong.
3. Following instructions exactly. Especially in the coding section, where your output has to match a format precisely.

This is why a student from a tier-1 college with no preparation often fails this round while a tier-3 student with eight weeks of disciplined practice clears it. The test does not know where you studied. It knows whether you have seen the pattern.

Say that to yourself once more, because it is the most useful thing in this article: this round rewards preparation more than it rewards intelligence. That is unfair in some directions and enormously fair in yours.

The sections you will face

Patterns vary by company and change from year to year. Always read the official pattern email or the company's own test-instructions page for the drive you are sitting — do not prepare from a two-year-old YouTube video. That said, the recurring structure across Indian mass recruiters looks like this:

Some tests add a personality or behavioural questionnaire — answer it consistently and honestly; it is largely a consistency check, and trying to game it is how people fail it.

The topics that actually repeat

Prepare these first. They cover the bulk of the paper at almost every mass recruiter.

Quantitative — percentages; ratio and proportion; profit, loss and discount; simple and compound interest; averages; time, speed and distance including trains and boats; time and work including pipes; number system, especially HCF and LCM, remainders, divisibility and unit digits; permutations, combinations and basic probability; mixtures and allegation; ages; mensuration; data interpretation from tables and graphs.

Reasoning — number and letter series; coding and decoding; blood relations; directions; seating arrangements, both linear and circular; syllogisms; Venn diagrams; statement and conclusion; data sufficiency; cubes and dice; clocks and calendars.

Verbal — reading comprehension; error spotting; sentence correction; para jumbles; sentence completion; synonyms and antonyms.

Programming fundamentals — tracing pseudocode output by hand; time and space complexity; arrays, strings, stacks, queues, linked lists, basic trees; recursion; OOP concepts; DBMS with normalisation, keys and joins; OS basics such as process versus thread and deadlock; a little networking.

Number system and percentages alone appear in an outsized share of questions, directly and hidden inside other problems. If you have one week, spend it there.

An honest 8 to 10 week plan

This assumes about 90 minutes on weekdays and three hours on weekends, alongside college. If you can give more, compress it. If you can only give 45 minutes, extend the timeline rather than skipping the mock tests.

Weeks 1–3: build the base, no timer

Take one quant topic and one reasoning topic every two days. Learn the standard method, then do 25 to 30 questions on it. Do not time yourself yet — accuracy first. Speed without accuracy just produces confident wrong answers.

Keep a formula notebook in your own handwriting. Percentage-to-fraction conversions, the compound interest formula, the work-rate shortcut, the train-crossing cases. One page per topic. In the final week you will revise from this and from nothing else.

Alongside, give 20 minutes a day to English — one long article read properly, ten grammar questions. This is the section people ignore and then lose by two marks in.

Weeks 4–6: add the clock, start coding

Now put a timer on everything. Sixty seconds per quant question, and stop when the timer stops. Getting it wrong at sixty seconds teaches you more than getting it right at four minutes.

Start the coding section in parallel. In one language you actually know — C++, Java or Python — solve two easy problems a day. Arrays, strings, basic maths, sorting, hash maps. Do not start dynamic programming. Mass-recruiter coding sections are mostly easy to lower-medium; depth matters far less than being able to write a clean, correct loop without fighting the syntax.

Practise reading input in your language. More candidates lose the coding section to input parsing than to algorithms. Know exactly how to read n followed by n integers, how to read a full line with spaces, and how to handle multiple test cases. Write this from memory until it is automatic.

Weeks 7–8: full-length mocks

This is the part people skip and it is the part that works. Sit a full-length timed mock, in one sitting, at least twice a week. All sections, no pauses, phone in another room.

Then spend as long analysing it as you spent taking it. For every wrong answer, categorise it:

• Did not know the concept — go back and relearn it
• Knew it, ran out of time — a speed problem, drill that topic
• Silly mistake — a process problem, see the next section
• Misread the question — a reading problem, slow down on the first read

Most people's error log is dominated by the last two. That is very good news, because those are the cheapest to fix.

The last 10 days

No new topics. Revise your formula notebook. One mock every two days. Sleep properly. Confirm the logistics: date, time, system requirements, ID proof, whether it is proctored, and what identity documents you must show.

Do not lose the easy marks

Roughly as many candidates fail on process as on knowledge. All of the following are free.

• Read the instructions page. Every single time. It tells you whether there is negative marking, whether sections are individually timed, whether you can move back to a previous question, and whether an on-screen calculator is provided. These change the correct strategy completely.
• Check for negative marking before you guess. With no negative marking, never leave a question blank — mark something on everything, in the last minute if needed. With negative marking, guess only when you have eliminated at least two options.
• If you cannot move back, decide fast. Many of these tests lock a question once you leave it. If you do not see the approach in fifteen seconds, pick the best option and move on. One hard question is not worth four easy ones.
• Do the data interpretation set as a set. You read the table once and answer three or four questions. Highest marks per minute on the paper — do not leave it for last and then run out of time.
• Attempt every section. Some companies apply a sectional cut-off, so a brilliant quant score cannot rescue a weak verbal score. Assume there is one.
• Test your setup the day before. Internet, power backup, browser, webcam, a quiet room, ID ready. Proctored tests flag you for switching tabs or for someone walking behind you. Losing an attempt to a router is a miserable way to lose a placement season.
• Keep your rough sheet organised. Number your working by question. Half of all "silly mistakes" are transcription mistakes from chaotic rough work.

The coding section, specifically

Three habits are worth more than any extra algorithm:

1. Match the output format exactly. If it says print the answer on a new line, do that. No "Enter the value:" prompts, no extra spaces, no trailing text. Automated judges fail cosmetically correct output.
2. Handle the edge cases the problem names. Empty input, a single element, negative numbers, the maximum constraint. They are in the problem statement for a reason.
3. Get a working brute force in first, then improve it. A correct O(n²) solution that passes most test cases scores. An elegant solution you did not finish scores nothing.

Write your solution, run the sample cases, and only then think about optimising. Partial marks are usually real.

If there is a written communication test

Some recruiters include an essay or an email, typically a short piece on a general topic under a tight time limit. It is graded largely by software on structure, grammar and length.

Write plain, correct English. An introduction, two or three body paragraphs, a conclusion. Hit the word count. Do not attempt literary flourishes. Short correct sentences beat long ambitious ones that break.

Where to practise, without paying

Previous-year and pattern-based question sets are widely available for free — IndiaBix and GeeksforGeeks cover the aptitude and fundamentals topics thoroughly, and most prep platforms let you sit some mock tests on a free tier. Your college's placement cell almost certainly has question banks from previous drives; ask for them.

You do not need to buy a ₹15,000 course. You need a question bank, a timer and eight weeks of showing up. If you do buy something, buy it for the full-length timed mocks, which are the hardest thing to replicate on your own — not for videos explaining percentages, which are free everywhere.

What to do this week

1. Find the official test pattern for the specific companies visiting your campus this season. Write the sections and the timing on one page.
2. Sit one full mock today, cold, without preparing. You need a baseline and you need the shock.
3. Start the formula notebook. Percentages and number system, in your own handwriting, this week.
4. Pick your coding language and write the input-parsing boilerplate from memory until you can do it in under a minute.
5. Block the same 90 minutes in your calendar every weekday for eight weeks and treat it as a class you cannot bunk.

This round is not a judgement on how clever you are. It is a filter with a known shape, a known syllabus and a known set of repeated patterns, and it will let through the person who practised over the person who did not. For someone from a college with no brand to lean on, that is the fairest deal you are going to be offered all year. Take it.