IDBI Bank ESO common mistakes
IDBI Bank ESO · Understand the traps and how to avoid them.
Spending the first minutes on a long General Awareness question about a recent RBI policy rate or a bank merger, trying to recall the exact figure instead of marking it and moving on.
GA is the highest-volume section on the IDBI ESO paper (roughly 40 of 200 questions) and many candidates treat it as a memory test they must 'win'. Because there is no negative-marking-free safety net in their mind, they freeze on one uncertain fact and lose 3-4 minutes that belong to Quant or Reasoning.
What to do instead
Adopt a 20-second rule for GA: if the exact number, name or year does not surface immediately, mark it and move on. Return only after the rest of the paper is attempted. In practice, do 50-question GA sets with a hard 12-minute timer and log every question that took over 20 seconds.
Confusing banking-sector facts that are close but distinct: repo rate vs reverse repo vs MSF vs bank rate, CRR vs SLR, base rate vs MCLR vs EBLR, and which institution sets which (RBI vs SEBI vs IRDAI vs PFRDA).
Candidates revise from headlines and short capsules rather than a structured map, so instruments blur together. Under exam pressure the most recently seen term wins, which is often wrong.
What to do instead
Build a one-page 'who sets what' matrix and a separate policy-rate table with the current values and the tool each rate controls. Rewrite it from memory weekly. For every rate you learn, state in one line what it does to liquidity, credit or inflation.
Treating current affairs as 'last month only' and skipping static-plus-current linkages such as central bank governors, finance ministers, heads of IMF/World Bank, indices and ranks, and the venue/theme of summits.
Coaching capsules emphasise the most recent month, so candidates under-prepare the 6-12 month window and the static anchors that examiners pair with news. They then guess on questions that are actually predictable.
What to do instead
Maintain a rolling 12-month diary organised by category (appointments, schemes, indices, summits, awards, sports, obituaries, banking news). Revise the oldest month each week so the whole year stays live, and add one static fact to each entry (e.g. HQ, founding year, predecessor).
Starting Quant with the arithmetic word problems and Data Interpretation sets in order, instead of scanning for the 8-10 questions that can be solved in under a minute (simplification, approximation, number series, quadratic comparison).
Sectional timing pressure makes candidates read the paper front to back. DI sets with five questions on one chart look efficient but can consume 8-10 minutes, and a single misread axis destroys the whole set.
What to do instead
In the first 60 seconds of the Quant section, mark every simplification/approximation/series/quadratic question and clear those first. Attempt DI only after those are banked, and abandon a DI set after 90 seconds if the data is not yielding. Rehearse this scan-and-prioritise routine in every mock.
Losing accuracy on simplification and approximation by ignoring BODMAS order, decimal placement, percentage-to-fraction conversions and the difference between 'approximate value' and 'exact value'.
These look trivial, so candidates rush them and treat them as free marks. The examiner designs them with near-miss options (e.g. 0.6 vs 6 vs 60) precisely to catch unchecked arithmetic.
What to do instead
Memorise the standard fraction-percentage table (1/2 to 1/16, plus 1/20, 1/25) and the squares to 30 and cubes to 15. For approximation questions, round first and confirm the option gap is wider than your rounding error before selecting. Do 20 such questions daily with a 6-minute cap and track the error type, not just the score.
Solving Data Interpretation questions by reading each question and then hunting the chart, rather than reading the chart once and extracting ratios, totals and growth rates up front.
Question-by-question hunting forces repeated re-reading of legends, units and footnotes, tripling the time per set. It also hides unit traps (thousands vs lakhs, percentage vs percentage points) until a wrong answer appears.
What to do instead
Before touching a question, note the units, the base year and whether the chart shows absolute values or percentages. Pre-compute the two or three derived figures the questions will need (total, difference, ratio). Practise one DI set daily under a 6-minute timer and write down the trap you would have fallen for.
Attempting puzzles and seating arrangements first in Reasoning because they feel 'core', and getting stuck on one arrangement for 10-12 minutes.
Puzzles are the most visible Reasoning topic in preparation material, so they dominate practice time and create a habit of starting there. In the exam, one under-determined puzzle can consume a fifth of the section.
What to do instead
Sequence the Reasoning section: clear syllogism, inequality, coding-decoding, blood relations, direction sense, order-ranking and alphanumeric series first, then take puzzles. Give any puzzle a 3-minute first pass; if the arrangement is not forming, leave it and return only if time remains. Log in a notebook which puzzle types reliably crack in under 3 minutes for you.
Drawing conclusions in syllogism from real-world knowledge or from the diagram instead of strictly from the stated premises, and mishandling 'possibility' cases.
Candidates instinctively apply common sense ('all roses are flowers, so some flowers are roses') and forget that only the premises count. Possibility questions require checking whether a conclusion is true in at least one valid diagram, which many never learn as a rule.
What to do instead
For each statement set, draw the minimum-overlap diagram first, then test each conclusion against it. For 'possibility' conclusions, ask whether a diagram exists in which the conclusion holds; if yes, it follows. Do 15 syllogism questions daily and write the rule you applied next to each answer for the first two weeks.
Reading the English passage once at normal speed and then answering 'inference' and 'author's tone' questions from general impression rather than from the text.
Under time pressure, candidates hunt for keywords and choose the option that matches a word they remember. Inference and tone options are written to reward exactly that shortcut with a plausible but unsupported choice.
What to do instead
Read the passage once for structure (what is claimed, what is conceded, what is concluded), then answer vocabulary and factual questions first and inference/tone last. For every inference option, point to the line that supports it; if you cannot, eliminate it. Practise two passages daily with a 5-minute reading-plus-answering cap.
Treating error-spotting, sentence improvement and fill-in-the-blank questions as 'feel' questions, choosing the option that sounds natural instead of applying grammar rules.
These questions are fast and intuitive, so candidates skip rule-checking. Examiners exploit high-frequency traps: subject-verb agreement across intervening phrases, wrong prepositions, tense sequencing, and countable/uncountable quantifiers.
What to do instead
Keep a personal error log of the 20 rules you actually miss (e.g. 'one of the + plural noun + singular verb', 'since vs for', 'despite + noun/gerund'). Before choosing, name the rule the question is testing. Do 25 mixed grammar questions daily and re-read the log before each mock.