GATE rewards a specific kind of preparation: concept depth over coverage breadth, numerical fluency over memorisation, and ruthless mock-test discipline. This guide is the branch-agnostic roadmap — the structure, scoring and study system that apply whether you are writing CS, DA, EC, EE, ME or CE.
The exam in one view
- 65 questions, 100 marks, 3 hours, computer-based.
- General Aptitude (GA): 10 questions, 15 marks — common to every paper and important enough to train throughout the plan.
- Your subject paper: 55 questions, 85 marks, mixing three question formats — MCQ, MSQ and NAT (formats and negative-marking maths here).
- Scorecard valid for 3 years under the GATE 2027 brochure for admissions use. Employment notices may require a particular GATE paper or exam year, so check each recruitment notice separately.
- Multi-session papers are normalised, and your GATE score (out of 1000) is not your marks out of 100 — the difference explained.
The syllabus truth nobody says plainly
Every GATE paper has an uneven distribution across its syllabus, visible in previous official papers. Build your priority order from the official syllabus and paper history rather than copying another branch's weight table. Previous-year questions (PYQs) are not merely end-stage practice — they show how the exam applies each topic. Every topic you finish should end with its PYQs, immediately.
The 6-month system
Months 1-3 — Concept building, weight-first. Choose one primary resource per subject and change it only for a named gap, not novelty. End every topic with its PYQs the same week. Maintain a personal formula-and-mistake notebook from day one; in month 6 it becomes your revision base.
Month 4 — Problem volume. Subject-wise tests and topic drills. Build NAT accuracy deliberately because numerical answers provide no option-elimination safety net (NAT strategy).
Months 5-6 — Full mocks + revision loop. One full 3-hour mock every 3-4 days, reviewed for as long as it took to sit. Track errors in three buckets: concept gap, silly/calculation, question misread. Each bucket has a different fix — respectively: reopen the topic, slow down arithmetic, underline what is asked. Between mocks, revise only from your notebook and PYQs.
GA throughout: use a short daily or near-daily block. General Aptitude is 15 marks in the official pattern, so leaving it to the final month creates unnecessary risk.
A repeatable study week
Use five concept/problem days, one mixed-test day and one review/planning block:
- Concept block: one bounded syllabus topic from your current high-weight subject.
- PYQ block: solve the topic's previous-year questions immediately; do not postpone them to revision month.
- Secondary subject block: maintain an already-covered subject so earlier work does not decay.
- GA block: short daily practice rather than a last-month crash course.
- Review block: update formulas, mistakes and the next week's topic order.
Every week should end with evidence: topics closed, PYQs attempted, accuracy by format, and repeated errors. Hours studied are an input, not the result.
Mock strategy inside the 3 hours
A two-pass system is a useful starting point: first solve questions that yield quickly and flag the rest; second, revisit flagged questions using your evidence, marks and remaining time. Derive your personal time threshold from mocks instead of copying a universal two- or six-minute rule. Know the negative-marking maths cold so attempt decisions are policy, not mood (the exact numbers).
Branch notes
The system above is universal; the weight tables are not:
- CS: balance mathematics, programming/algorithms and systems subjects. Avoid becoming excellent at coding questions while leaving theory of computation, networks or architecture untouched.
- DA: probability, statistics, linear algebra and machine learning foundations need continuous numerical practice; vocabulary-only AI preparation is insufficient.
- EC: networks, signals, analogue/digital electronics and communication build on one another, so prerequisite order matters.
- EE: circuits, machines, power systems, control and measurements require both concept recall and calculation speed.
- ME: engineering mathematics, applied mechanics, thermodynamics, fluids, manufacturing and machine design create a broad calculation-heavy paper; units and approximation discipline matter.
- CE: structures, geotechnical, water resources, environmental, transportation and geomatics compete for revision time; rotate subject groups rather than finishing one and abandoning it.
The six linked course pages below map this study system to CS, DA, EC, EE, ME and CE. Choosing between CS and the newer DA paper? That decision guide is here.
Readiness checklist
Before the full-mock phase, confirm: high-weight subjects completed once; PYQs solved topic-by-topic; formula notebook usable without reopening textbooks; GA practised every week; MSQ/NAT formats trained; and at least one mixed test reviewed by error category.
Before exam week, confirm: a stable two-pass policy; calculator familiarity; no repeated sign/unit mistakes; revision material reduced to notes, formulas and error logs; and recent mocks completed at the real time of day without avoidable interruptions.
Quick answers
When should full mocks start? Once most high-weight syllabus areas are covered and you can review a paper meaningfully. Starting too late hides timing problems; starting before basic coverage produces little diagnostic value.
Should I finish the entire syllabus before PYQs? No. Solve each topic's PYQs immediately after learning it.
Is one resource per subject enough? One dependable teaching source plus official syllabus, PYQs and tests is usually more useful than repeated resource switching.
Can one generic weight table serve every branch? No. Use the official syllabus and recent paper history for your selected paper.
