FCI Assistant Grade III common mistakes
FCI Assistant Grade III · Understand the traps and how to avoid them.
In the Quantitative Aptitude section, spending 3–4 minutes on a single DI (Data Interpretation) question set or a heavy arithmetic word problem before marking it and moving on, instead of skipping after roughly 60–75 seconds.
FCI Assistant Grade III is a speed-plus-accuracy paper with sectional time pressure; candidates come from a habit of 'finishing what you start' and fear that a skipped question means lost marks, so they sink time into one calculation and lose 4–5 easy questions elsewhere.
What to do instead
Adopt a two-pass strategy in every mock: Pass 1 answers only questions you can finish in under 60 seconds (simplification, percentages, averages, ratio, number series); Pass 2 returns to DI and word problems. Practise with a visible timer and record per-question time in a log; target 45–50 seconds average for Quant.
Applying shortcut formulas without checking the base condition - e.g. using successive percentage change a+b+ab/100 when the base changes, or applying the 'work done' LCM trick when workers leave mid-way - and then picking the answer that matches the wrong calculation.
Shortcuts are learned as memorised templates during coaching, not derived, so candidates cannot detect when the template does not apply; the exam deliberately includes questions where the standard shortcut gives a plausible-looking wrong option.
What to do instead
For each shortcut you use, write down in one line the condition under which it is valid (e.g. 'same base for both changes', 'all workers present throughout'). In practice, solve 2–3 questions per topic by the long method weekly to keep the logic visible, and verify one option by back-substitution when time permits.
In Reasoning, attempting puzzles and seating-arrangement sets without first fixing the number of variables and drawing a fixed grid/table, then abandoning the set halfway and restarting it later.
Candidates read the whole paragraph, start placing items mentally, hit a contradiction caused by a missed negative clue, and restart - burning double time. Mental tracking fails beyond 4–5 entities.
What to do instead
Before solving, count entities and categories and draw the table with that exact number of rows/columns. Mark negative clues ('not X') with a cross in the cell, not in memory. If two clues contradict, stop and re-read the clue list rather than the paragraph. Cap a puzzle set at 3–4 minutes; if unresolved, mark and move on.
Treating non-verbal and classification items (odd-one-out, figure series, paper folding, mirror/water image, embedded figures) as 'free marks' and answering from a quick glance rather than applying a defined rule.
These items look trivial, so candidates answer in 10–15 seconds and fall for the distractor that differs in one attribute (rotation vs reflection, number of sides vs number of lines of symmetry).
What to do instead
For each non-verbal type, memorise a short checklist to run in order: rotation direction, reflection, element count, shading, position shift, line/curve type. Apply the checklist explicitly in practice rather than 'seeing' the answer, and record the rule you used so errors become visible.
In General English, choosing an option because it 'sounds right' in cloze tests, sentence improvement and error-spotting, without checking subject–verb agreement, preposition collocation and tense consistency in the given sentence.
Everyday spoken English habits conflict with formal written grammar tested here; options are constructed so that the colloquially natural phrase is the wrong one (e.g. 'discuss about', 'one of my friend').
What to do instead
Build a personal error list of 40–60 high-frequency rules (subject–verb agreement with 'one of the', 'each/every', 'neither…nor', articles, prepositions after common verbs, comparatives) and revise it weekly. In error-spotting, read the sentence in segments and check each segment against the list before looking at options.
In the Hindi Language section (or the English section for Hindi-medium candidates), translating the sentence word-by-word into the other language before answering, instead of judging the option within the target language.
Bilingual candidates habitually translate, which introduces interference - wrong gender/number agreement, incorrect idiomatic usage (मुहावरे/लोकोक्तियाँ), and mis-selected synonyms/antonyms.
What to do instead
Prepare a dedicated list of 100+ मुहावरे/लोकोक्तियाँ with meanings and one usage sentence each, plus संधि/समास/उपसर्ग-प्रत्यय categories, and revise in the target language only. In practice, read the whole Hindi sentence for overall meaning first, then evaluate options; never construct the answer from a literal translation.
Preparing General Awareness only from static GK lists (capitals, rivers, dates) and ignoring the previous 6–8 months of current affairs, especially agriculture, food procurement, PSUs and government schemes.
Static GK feels finite and comfortable to revise, while current affairs feels unbounded; but the current-affairs share in this exam is substantial and is where most candidates lose 8–12 marks.
What to do instead
Maintain a monthly one-page current-affairs sheet covering: central schemes and their ministries, appointments, sports, awards, budget/economic survey highlights, and FCI/agriculture/food-security news. Revise the last 8 months on a rolling basis; do one 25-question current-affairs quiz every week and re-test wrong items after 7 days.
In Computer Knowledge, memorising only definitions of hardware terms and skipping the practical operating details - file extensions, shortcut keys, MS Office menu paths, basic networking and internet terminology, and security concepts.
Candidates assume Computer Knowledge is a small, easy section and study it last, so questions on shortcut keys, default file extensions, or the difference between a hub/switch/router are answered by guesswork.
What to do instead
Make a one-page-per-topic cheat sheet: shortcut keys (Ctrl/Alt/Shift combinations), common file extensions, generations of computers, memory units and their order, network types and devices, and basic security terms (firewall, phishing, malware). Test yourself with 20 rapid-fire items twice a week; practise the actual operations on a computer where possible.
Ignoring the Discipline-Specific Technical Knowledge paper until the last two weeks, assuming the general sections will carry the score, and studying the technical subject only at a conceptual overview level.
The post-specific paper (Accounts, Civil/Electrical/Mechanical Engineering, Laboratory, Hindi, etc.) carries decisive weight and is set at a technical depth - standard codes, definitions, formulae and procedures - that cannot be absorbed in a fortnight of skimming.
What to do instead
Fix the syllabus of your specific discipline on day one and give it a fixed weekly block from the start. For Accounts: journal-to-final-accounts flow, depreciation methods, ratios, GST/TDS basics. For Engineering: IS codes, standard formulae, unit conventions, material properties. For Laboratory: instrument handling, precision/accuracy, standard solutions. Solve 30–40 previous-pattern technical questions per week and keep a formula/definition register.
Taking full-length mocks without reproducing exam conditions - pausing the timer, using a calculator or rough paper freely, or skipping the sectional order - and then reviewing only the total score, not the individual wrong answers.
Mocks are treated as a scorecard rather than a diagnostic tool; without an error log, the same mistakes (misread question, calculation slip, wrong formula) repeat, and untimed practice hides the speed problem that decides selection.
What to do instead
Do at least one full mock per week in strict exam order and time, on screen if the exam is computer-based. Spend as long reviewing as attempting: classify every wrong answer as concept gap, calculation error, misread, or guess, and add it to a dated error log. Re-attempt only the logged items after 7 days; track sectional cut-off scores, not just the total.