Federal Bank PO common mistakes
Federal Bank PO · Understand the traps and how to avoid them.
In Reasoning puzzles and seating arrangements, the candidate fills the grid from the first clue and keeps deriving forward, then abandons the puzzle after 6-8 minutes when two cases remain unresolved instead of switching to a second possible arrangement branch early.
Bank PO puzzles are designed with one or two ambiguous clues whose meaning only resolves when combined with a later clue. Candidates trained on simpler puzzles expect a single linear deduction chain and freeze when they must hold two parallel cases, and sunk-cost thinking keeps them on the same branch.
What to do instead
Adopt a two-case habit: the moment a clue permits two placements, mark Case A and Case B side by side in the rough sheet and test the next clue against both. Set a hard 4-minute checkpoint per puzzle; if neither case has collapsed by then, move on and return only after finishing the section. Practise 15 puzzles a week where you deliberately write both cases before eliminating.
In syllogism and inequality questions, the candidate answers from intuition about what 'seems logically true' in real life rather than applying the possibility/definiteness rule, so they mark 'follows' for conclusions that are only probably true.
Everyday reasoning rewards plausible inference, while these questions demand strict formal treatment: a conclusion follows only if true in every Venn model consistent with the statements. Under time pressure the brain substitutes a quick plausibility check.
What to do instead
Draw the minimum-overlap Venn diagram plus the maximum-overlap variant for every syllogism before looking at the options, and for 'possibility' conclusions check whether at least one valid diagram makes it true. For inequality chains, rewrite the whole chain left to right with a single arrow direction before evaluating. Drill 20 questions daily with written diagrams until the formal check becomes automatic.
In Data Interpretation sets, the candidate reads the chart, then computes each question from scratch with full long multiplication and division, spending 8-10 minutes per set and leaving 2-3 sets untouched at the end.
DI is placed early in the paper and candidates treat it as a calculation test rather than an estimation test. Without approximation discipline, exact arithmetic on large numbers consumes the section.
What to do instead
Before answering, scan all questions in the set and note which ask for ratios, percentages, or differences. Round values to two significant figures, compute percentage change with the fraction-to-percent table (1/6 = 16.67%, 1/7 = 14.28%, etc.), and use options to bound the answer. Target 4-5 minutes per 5-question set and time yourself with a stopwatch for 10 consecutive sets.
On missing-data or caselet DI (where one value is absent or given as a variable), the candidate assumes the missing figure is not needed and answers from partial data, or spends time trying to compute the missing value when the question does not require it.
Caselets hide the required relationship in prose rather than a table, so candidates misjudge which quantities are actually needed. The habit of 'complete the table first' is costly when only one ratio is asked.
What to do instead
Read the question first, then the caselet, and underline only the data the question names. If a variable cancels out, proceed symbolically. If the question genuinely needs the missing value, look for the one equation linking it to known totals. Practise 10 caselets weekly, writing the required quantity at the top of the rough work before reading the passage.
In General and Banking Awareness, the candidate memorises static facts (founding years, headquarters) but cannot answer questions on current policy rates, recent RBI circulars, or banking terminology, and guesses on anything from the last six months.
Static awareness feels finite and learnable, while current affairs feel unbounded, so candidates over-invest in the former. Bank PO awareness sections now weight recent monetary policy, schemes, and appointments heavily.
What to do instead
Maintain a rolling six-month one-page sheet with RBI repo, reverse repo, CRR, SLR, MSF, bank rate, inflation prints, key committees and their chairpersons, and recent banking scheme launches, updated weekly from the RBI press-release page. Revise it every Sunday. Pair this with a fixed banking-terms list (NPA classification, Basel III ratios, CASA, priority sector norms) tested by self-quiz.
In the English section, the candidate reads the entire passage first, then answers, spending 10-12 minutes on one reading comprehension set and rushing the grammar questions that carry equal marks.
School habit teaches full reading before questions, but bank exam passages are long and the questions are mostly local. Time spent reading material never tested is pure loss.
What to do instead
Use question-first reading: scan the questions, note the keyword each asks about, then read the passage once with those keywords in mind, answering vocabulary and factual questions as you encounter them. Cap RC at 6-7 minutes per set. For error-spotting and cloze, revise the ten most tested rules (subject-verb agreement, parallelism, article use, preposition collocations) and do 25 questions daily.
In Quantitative Aptitude, the candidate attempts every question in sequence, sinking 5+ minutes into one quadratic or time-and-work problem and thus missing three easy simplification questions later in the section.
Questions are not ordered by difficulty and the paper rewards selectivity, but candidates treat completion as the goal. Ego investment in a single hard question compounds the loss.
What to do instead
Do two passes: first pass takes only questions solvable within 45 seconds (simplification, approximation, number series, easy percentage), second pass takes the rest. Physically mark and skip after 60 seconds on any question. Build a personal list of the 12 question types you solve fastest and hunt those first in every mock.
In Computer Aptitude, the candidate prepares only awareness-style facts (generations of computers, full forms) and cannot answer operational questions on shortcuts, Excel functions, networking concepts, or security terminology that the paper actually asks.
Computer sections in bank exams mix static awareness with applied knowledge, and candidates rely on outdated guides that over-weight trivia. Applied items on file extensions, topologies, and malware types then feel unfamiliar.
What to do instead
Split preparation: one list for abbreviations and generations, one for applied items (common Excel functions like VLOOKUP and COUNTIF, IP address classes, OSI layers at a conceptual level, types of malware, backup types). Practise shortcut recall by actually using the software, and self-test 30 applied MCQs weekly.
The candidate writes full step-by-step solutions for every DI and arithmetic question on paper, consuming rough-sheet space and time on transcription rather than on the calculation itself.
Coaching habit and fear of error push candidates to 'show work', but in a speed test the rough sheet is a scratchpad, not an answer script. Writing full sentences and copying numbers wastes 20-30 seconds per question.
What to do instead
Restrict rough work to symbols, numbers, and arrows: write the operation, not the explanation. Use vertical alignment for multi-step arithmetic and a consistent abbreviation set. Time a 20-question set with and without this discipline to see the difference, then keep the faster format in all mocks.
The candidate takes full-length mocks but never analyses them, so the same error types (misread question stems, unit slips, wrong option marked) recur, and sectional cut-offs are missed despite a good overall score.
Mock-taking feels productive and analysis feels like lost practice time. Without a written error log, candidates cannot see that most lost marks come from a handful of repeatable behaviours rather than from lack of knowledge.
What to do instead
After each mock, spend equal time on review: log every wrong and skipped question with its cause (concept gap, misread, calculation, time), tag the domain, and count causes weekly. Fix the top cause with 30 targeted questions before the next mock. Track sectional scores separately against expected cut-offs, not just the total.