ESE GS&EA common mistakes
ESE GS&EA · Understand the traps and how to avoid them.
Spending the first 40–50 minutes on the two 100-mark General Studies papers and then rushing the eight engineering papers with barely 90 minutes left for 800 marks.
The weightage looks counterintuitive: General Studies carries only 200 of the 1,000 marks but comes first in the paper, so candidates treat it as the priority and lose time where the marks actually are.
What to do instead
Before the exam, fix a time budget by marks, not by paper order: roughly 1.2 minutes per mark for the engineering papers and under 0.5 minutes per mark for General Studies. Write the target clock times for each section on the rough sheet in the first two minutes and check them at every section boundary.
Writing long descriptive paragraphs for the General Studies and Engineering Aptitude objective questions, then running out of time to attempt the numerical engineering items.
Many candidates prepare General Studies through essay-style material (current affairs magazines, long-form notes) and carry that habit into a paper where almost everything is a single correct option or a short numerical answer.
What to do instead
Practise with a strict 45–60 second cut-off per objective question. If an item is not resolved in that window, mark it and move on; return only after all sections are attempted. Do timed full-length mocks at least four times so the pacing becomes automatic.
Skipping the Standards and Quality Practices, Ethics, and Engineering Aptitude sub-topics entirely because they look like 'general awareness' rather than engineering.
These topics feel unfamiliar compared with core technical subjects, and candidates assume they cannot be prepared systematically, so they leave easy marks on the table.
What to do instead
Build a one-page summary for each: the standards bodies and what they cover, the code of ethics principles, and the basic aptitude formulas (percentages, ratios, averages, data interpretation). These are high-yield, low-effort topics; revise them in the last week.
Attempting every technical question in the engineering papers, including ones on topics outside the declared syllabus, instead of leaving them blank.
Candidates fear negative marking or feel obliged to fill every row, and they misjudge how much a guessed wrong answer costs relative to a skipped one.
What to do instead
Apply a clear attempt rule: answer if you can eliminate at least two options or reach a defensible numerical result; otherwise leave it. Track your accuracy in mocks and only loosen the rule if your accuracy stays above roughly 70 percent.
Reading the whole question paper front to back before writing anything, consuming 15–20 minutes of a three-hour paper.
School habits of 'read the paper first' persist, and candidates want to find the 'easy' questions, but the paper is long and the scan yields little advantage.
What to do instead
Use a 60-second skim only to note section boundaries and mark the first two or three questions you will attempt. Start writing immediately and discover difficulty as you go.
Ignoring units and dimensional consistency in numerical engineering questions, so a correct method produces a wrong option.
Mixed SI and practical units (kN vs N, MPa vs Pa, mm vs m) appear in the same paper, and candidates substitute values without converting.
What to do instead
Adopt a fixed habit: write the given quantities with units, convert everything to a single consistent set before substitution, and check the dimension of the final answer. In mocks, mark every unit error separately from method errors so the pattern becomes visible.
Leaving numerical-answer items unattempted because the arithmetic looks tedious, while spending the same time on familiar theory questions worth fewer marks.
Comfort-seeking under time pressure: theory items feel quick and safe, so candidates gravitate to them even when the numerical items carry equal or higher marks.
What to do instead
Rank by marks-per-minute, not by comfort. Attempt all numerical items first within each section, using approximations (round to two significant figures) to reach the option quickly, then return to theory items.
Preparing only from a single textbook per subject and never solving previous-year-style papers under timed conditions.
Reading feels productive and timed practice feels uncomfortable, so candidates postpone it until the final fortnight when there is no time to correct weaknesses.
What to do instead
Schedule one full timed mock per week from the third month onward, and spend as long analysing it as writing it. Keep an error log categorised by topic and error type (concept, calculation, misread, time) and review it before each new mock.
Misreading 'which of the following is NOT correct' and similar negative stems, then selecting the true statement.
Under speed pressure the eye skips the negation, and the options often include the correct statement first, which rewards the misread.
What to do instead
Circle or underline every negative qualifier (NOT, EXCEPT, INCORRECT, LEAST) as you read the stem, and restate the stem in your own words before looking at options. In mocks, tally negative-stem errors separately to confirm the habit is fixed.
Cramming new technical topics in the final week instead of consolidating formulas, standards, and ethics content already covered.
Anxiety drives last-minute breadth, but new material in the final week is rarely retained and displaces revision of high-frequency basics.
What to do instead
Freeze new topics seven to ten days before the exam. Use the final week for formula sheets, a one-page standards and ethics summary, and re-solving errors from your log. Sleep and exam-day logistics are part of the plan, not an afterthought.