Subject-Specific Knowledge (Stream/Programme Applied For)
How this section is built
This paper tests the core of the discipline you have applied for, at roughly the level of the qualifying school or undergraduate syllabus. The smartest first move is to obtain the official syllabus and weightage and map it against your own course material, marking each topic as strong, rusty or unseen. Spend most of your revision time on the middle band - rusty topics yield marks fastest.
What separates a pass from a good score
- Fundamentals over trivia. Questions are usually designed around one defining principle, property or definition; recall of isolated exceptions earns little.
- Application items. Expect numerical or case-based items that apply a rule rather than ask for it. Practise derivation and worked problems, not just statements.
- Edge cases. Boundary conditions, sign and unit conventions, and standard assumptions are the commonest source of error.
- Terminology precision. Two near-synonymous technical terms usually mean different things; the trap is a definition swap.
Worked example (a general rule you can apply in any technical subject)
Before finalising any numerical answer, run a two-part sanity check: (1) dimension and unit check - does the answer carry the units the question asks for, and are all inputs in the same system? (2) magnitude check - is the number physically sensible? A calculated human body mass of 7 kg, or a resistance in microfarads, signals an arithmetic or unit slip, not a novel result. Roughly a quarter of lost marks in technical papers come from unchecked units rather than unknown concepts.
Rule of thumb
Answer every question you can defend in one line; flag genuinely uncertain items and return to them. Negative marking, if present, makes unwarranted guessing expensive.