How to crack campus placement aptitude tests: a no-fluff guide for Indian freshers
You've been shortlisted for the placement drive. The company you want most is coming next Thursday. Before any interview, before any HR round, you have to clear the aptitude test — and 60–80% of candidates don't make it past this stage.
Yet most students spend most of their prep time on interview questions and almost none on the test that decides whether they get to the interview at all.
Here's a focused, practical guide to fixing that.
What aptitude tests actually measure
Almost every Indian campus placement test — whether it's TCS iON, Infosys Assessments, AMCAT, CoCubes, or a company's own platform — draws from the same three sections:
Quantitative Ability (Quant): Number series, percentages, profit and loss, time-speed-distance, work and wages, permutations and combinations. The math is Class 10–12 level, but the time pressure is brutal.
Logical Reasoning: Blood relations, seating arrangements, coding-decoding, syllogisms, Venn diagrams, data interpretation. These require pattern recognition more than formulas.
Verbal Ability: Reading comprehension, fill in the blanks, error spotting, sentence completion, vocabulary. Neglected by engineering students, and the easiest to improve quickly.
Some tests add a coding section (TCS, Infosys, HCL, Wipro) with one or two basic problems in Python, C, Java, or C++. Product companies and SDE roles expect this; service companies often have simpler logic-fill questions instead.
How major companies differ
Knowing the format of the specific test you're taking matters more than generic prep.
| Company | Platform | Time | Coding? | Cutoff style | |---|---|---|---|---| | TCS | iON (TCS NQT) | 180 min | Yes (1-2 problems) | Section-wise cutoff | | Infosys | Own platform | 95 min | Yes (optional advanced) | Overall percentile | | Wipro | NLTH / AMCAT | 120 min | Yes | Sectional cutoff | | Accenture | AMCAT | 60 min | No (for some roles) | Overall score | | Cognizant (CTS) | Own platform | 60 min | Yes | Sectional cutoff | | HCL | Own platform | 90 min | Yes | Sectional cutoff | | Capgemini | Cocubes | 115 min | Yes | Sectional cutoff |
Takeaway: Most major IT companies use sectional cutoffs, meaning you can't compensate a weak verbal score with a strong quant score. You must clear every section.
A 4-week prep plan that actually works
Week 1: Diagnose and cover fundamentals
Take a full-length AMCAT or free IndiaBix mock test without preparation. Note which topics you get wrong and in which section. This gives you a map — don't skip it.
Then spend the rest of the week reviewing formulae and shortcuts for your weakest quant topics only. Keep a running one-page cheat sheet of formulae as you go.
Daily target: 30 min quant, 20 min verbal (read one article and spot 5 grammar errors).
Week 2: Drill logical reasoning
LR is learnable fast. The trick is pattern recognition from repetition, not concept memorisation.
Work through the following in order: Number series → Seating arrangements → Blood relations → Syllogisms → Data sufficiency. Do 20-25 questions per topic before moving on.
Resource: IndiaBix Logical Reasoning section is free and has good variety. Hit "Topic Tests" not "Random Tests" at this stage.
Week 3: Full section practice under time pressure
This week, simulate test conditions. Set a timer. If a quant question takes more than 90 seconds, mark it and move on — return only if time allows.
A common trap: students who practise without time pressure perform 20-30% worse on the actual test simply because the pacing is unfamiliar. The test isn't just about knowing the answer; it's about deciding quickly whether you can answer in time.
Speed drills: Pick any 25-question Quant or LR set and target finishing in 20 minutes. Check your score, then review only the ones you got wrong or guessed.
Week 4: Full mocks and the coding section
Take two to three full-length mocks of the specific test you're targeting. Most companies publish sample papers — TCS publishes official NQT prep material, and Infosys has free Prep Resources on their careers page.
For the coding section (if required), you don't need LeetCode-level prep. Practice:
- Pattern printing (loops)
- Array manipulation (sum, max, reverse)
- String operations (palindrome check, frequency count)
- Basic recursion (factorial, Fibonacci)
If you can write clean, working code in 15–20 minutes for problems at this level, you're ahead of most other candidates in a service-company test.
Test-day tactics that move your score
Answer easy questions first. Every attempt scores; every skip might not get a second chance. Skim a section's questions in the first 30 seconds and start with the ones you're confident about.
Never leave verbal blank. It's the fastest section to score in if you've done even moderate prep. A 5-minute focused attempt on verbal can lift your overall score significantly.
Use elimination on MCQs. Many aptitude questions are faster to solve by eliminating two obviously wrong choices and then computing among the remaining two, rather than solving from scratch.
Watch for negative marking. TCS NQT and some AMCAT versions carry a penalty for wrong answers. Know your test format. When in doubt — especially on LR — skip rather than guess.
Maintain a pace log. Know that for a 60-question / 60-minute test you need roughly one question per minute. Check your position every 15 minutes. If you're behind, you don't go faster — you triage: which remaining questions are solvable in under 60 seconds?
The mistake that eliminates most candidates
Students treat the aptitude test as an afterthought and scramble in the last two days before the drive. Two days of cramming formulas cannot fix a foundational weakness in speed or reasoning patterns.
Start four weeks out. One focused hour a day beats five-hour panic sessions. And take at least two full mocks under actual time pressure before the real thing — the pacing is a skill in itself.
The interview is where CareerClutch shines — but to get there, you first have to clear this filter. Don't let a solvable preparation problem be the reason you don't.