PhilNITS FE common mistakes
PhilNITS FE · Understand the traps and how to avoid them.
Treating the FE as a pure coding test and spending most preparation time writing programs in a single language, skipping the wide non-coding syllabus (databases, networks, security, project management).
Candidates with programming experience assume the exam rewards implementation skill, but the FE is deliberately broad and the bulk of questions are conceptual and terminology-based across many areas.
What to do instead
Build a coverage checklist from the published exam scope and allocate study time proportional to topic weight, not personal familiarity. Reserve hands-on coding for the algorithm and data-structure questions only, and schedule weekly review of the non-coding domains.
Memorising formulas and definitions without being able to apply them, so questions that phrase a familiar concept in an unfamiliar scenario are answered by pattern-matching the wrong keyword.
The exam often tests the same idea in a situational wrapper; rote recall produces fast but wrong recognition, especially in probability, queueing, and reliability questions.
What to do instead
Practise by explaining each formula in words and solving at least two varied scenarios per concept. When a keyword appears, restate what the question actually asks before choosing an answer, and verify units and assumptions.
Running out of time because every question is attempted at the same pace, leaving long calculation or pseudo-code tracing questions to the end when no time remains.
The paper is long and mixed in difficulty; candidates who go strictly in order get stuck on one hard item and lose the easy marks later in the paper.
What to do instead
Do two passes: first answer all quick conceptual items and mark uncertain ones, then return to calculations. Cap time per question (for example one minute on pass one) and practise full-length timed papers to calibrate pace.
Choosing a strategy of studying only past-exam patterns and skipping the strategy and management domains as 'soft' material, then losing easy marks on questions about project scope, risk, and service management.
Technical candidates perceive management topics as low-value, but these questions are largely definitional and highly learnable, so they are among the most efficient marks available.
What to do instead
Study the standard bodies of knowledge referenced in the syllabus at overview level: project phases, WBS, risk registers, SLAs, ITIL-style service concepts, and basic corporate finance and law terms. Use short spaced-repetition cards rather than deep reading.
Confusing similar strategy and management terms (for example feasibility study versus requirements definition, or SLA versus OLA) and answering from the first plausible-sounding option.
These domains are dense with near-synonyms, and candidates often learn them from summaries that omit the distinguishing criterion.
What to do instead
For each term pair, write a one-line contrast that states who owns it, when it applies, and what artefact it produces. Test yourself by matching terms to short scenarios rather than to definitions.
Ignoring the business-context framing in strategy questions and answering as if the question were purely technical, for example recommending a technology because it is newer rather than because it fits cost, risk, and organisational constraints.
Engineers default to technical optimality, while these questions reward trade-off reasoning involving cost, schedule, compliance, and stakeholder impact.
What to do instead
Before answering, identify the decision criterion the scenario emphasises (cost, risk, time-to-market, compliance). Eliminate options that optimise a criterion the scenario does not mention, and justify the remaining option against all stated constraints.
Misreading multi-part questions with negation or 'which is NOT correct' phrasing, and selecting a true statement when the false one was requested.
Under time pressure, candidates scan for keywords and confirm the first true-looking option, missing the logical inversion in the stem.
What to do instead
Underline or mentally flag negation words and superlatives before reading the options. For 'NOT' questions, evaluate every option as true or false explicitly, then choose the odd one out.
Leaving answers blank when unsure, rather than eliminating options and committing to a best guess.
Some candidates believe an incorrect answer is penalised more than a blank, or freeze because they cannot fully justify an answer.
What to do instead
Confirm the scoring rule for the sitting and, if there is no negative marking, answer every question. Use elimination on units, extreme wording, and internal contradictions to raise the odds before guessing.
Tracing pseudo-code or evaluating expressions by reading top-to-bottom without tracking variable state on paper, producing off-by-one and loop-boundary errors.
Working memory overloads on nested loops and recursion; small arithmetic slips propagate silently to the final answer.
What to do instead
Maintain an explicit table of variable values after each iteration, and check boundary cases (first iteration, last iteration, empty input). Re-derive the result once by a different method when time allows.
Skipping the security, law, and ethics items because they feel peripheral, and answering them from general intuition rather than the specific terminology the syllabus uses.
These topics appear in small numbers but use precise vocabulary (confidentiality, integrity, availability, authentication versus authorisation, personal data handling) that intuition alone maps imprecisely.
What to do instead
Learn the core vocabulary and the standard classification of threats and controls, then practise scenario questions where the task is to select the control that addresses the stated risk. Keep a short list of legal and ethical terms with one example each.