How to Prepare for GATE: A Stage-Wise Plan for Notes, PYQs and Revision

The short version: GATE preparation means working one branch's syllabus in real depth over nine to twelve months — build core concepts from standard textbooks or NPTEL, start solving previous-year questions from month three onward since GATE reuses concept structures heavily, keep a running formula sheet and error log as you go rather than compiling one later, and reserve the final month for full-length timed mocks and revision, not new topics.

GATE is different in kind from most exams Indian aspirants prepare for, and the difference changes almost every piece of advice that applies elsewhere. RRB, SSC, and even UPSC Prelims reward breadth — covering a wide, shallow syllabus and recognising facts fast. GATE rewards depth on one paper out of roughly thirty branches, tested over three hours with numerical-answer questions that offer no elimination strategy and no partial credit. A candidate who "covers" the syllabus without solving problems discovers the gap on exam day, when recognising a concept and being able to compute the answer under time pressure turn out to be two different skills.

This guide covers what GATE actually tests, a stage-wise plan from foundation through revision, why previous-year questions carry unusual weight here, the handwritten-notes problem that quietly costs marks in the final month, a real source list, a realistic weekly timetable, and an honest answer on preparing without coaching.

GATE in brief

GATE — the Graduate Aptitude Test in Engineering — is conducted as a computer-based test across roughly thirty subject papers, and a candidate sits for exactly one (occasionally two, for a small set of permitted combinations). The exam runs three hours for 65 questions worth 100 marks total: 10 General Aptitude questions worth 15 marks, and the remainder from your chosen subject.

For branches that include Engineering Mathematics as a separate component (most of the large branches — Computer Science, Mechanical, Electrical, Civil, and others), the 100 marks split roughly as General Aptitude 15, Engineering Mathematics 13, and the core subject 72. For branches without a separate Engineering Mathematics section, General Aptitude stays at 15 and the remaining 85 marks sit entirely in the subject paper.

Three question types appear: Multiple Choice Questions (MCQs, one correct answer), Multiple Select Questions (MSQs, one or more correct answers), and Numerical Answer Type questions (NATs, where you type a computed value rather than choose from options). Negative marking applies only to MCQs — 1/3 mark deducted for a wrong 1-mark MCQ, 2/3 for a wrong 2-mark MCQ — while MSQs and NATs carry no negative marking at all, which changes the risk calculus for attempting them compared to MCQs you're unsure about.

Because it's one paper deep rather than many papers wide, the entire preparation strategy differs from the breadth exams this guide's sibling posts cover. There's no "GA and Reasoning across every section" pattern here — there's a syllabus, typically ten or more chapters deep per subject, that has to be genuinely understood, not recognised.

Foundation: build the concept base your semester already started

The first three to four months should go into building core subject concepts chapter by chapter, ideally in roughly the sequence your undergraduate semesters covered them — you're reinforcing existing structure, not learning cold. Work through standard textbooks or NPTEL lecture series (the free, IIT-faculty-taught video courses that closely track most GATE syllabi), and solve textbook-level problems as you go rather than only watching or reading. Passive coverage produces recognition; problems produce recall, and GATE tests recall under a clock.

Start Engineering Mathematics and General Aptitude as fixed weekly slots from month one rather than deferring them — both are high-return, low-glamour sections that lose the most marks when left for "later," because later rarely arrives with enough runway to build genuine speed in either.

Core phase: depth, speed, and the note-taking habit that has to start now

From roughly month four through month eight, the work shifts from building concepts to deepening problem-solving speed and range — harder problems, edge cases, and the numerical-heavy question types (NATs especially) that reward calculation accuracy under time pressure. This is also the phase where your note-taking system has to be running properly, because you cannot rebuild a year's worth of organisation in month nine. Every derivation worked out, every formula that took real effort to arrive at, and every mistake made in a timed set needs to land somewhere you can find it again — not somewhere you'll rediscover by accident during a panicked search in the last week.

Why previous-year questions matter more here than almost anywhere else

GATE is unusual among Indian competitive exams in how heavily it reuses concept structures. A question style tested five years ago on, say, the same circuit topology or the same class of differential equation shows up again with different numbers, not a different underlying idea. This makes previous-year questions a prioritisation tool from early in your preparation, not a late-stage warm-up: solving ten to fifteen years of PYQs, topic-wise, tells you which concepts within a chapter actually get tested versus which sit in the syllabus but rarely appear in a paper.

Start PYQs around month five or six, topic-wise rather than as full mixed papers at first — solve every previous-year question on, say, control systems or thermodynamics in one sitting, then move to the next topic. This builds the specific pattern recognition full mixed practice can't, because mixed practice never gives enough repetitions on a single question type to make it automatic. For Computer Science and Data Science aspirants specifically, GATE Overflow — a free, crowd-solved archive of previous-year GATE CS/DA questions with detailed community discussion — is worth knowing about early; it surfaces the exact way a concept has actually been tested, which a textbook alone won't show you.

The handwritten-notes problem

Ask anyone who has cleared GATE what they revised from in the final month, and the answer is rarely a textbook. It's a formula sheet, a derivation notebook, and an error log — built up over nine to twelve months, mostly by hand. Handwritten notes remain the default for GATE for a real reason that has nothing to do with the exam format itself: GATE is computer-based, so there's no writing-speed argument the way there is for a handwritten exam like UPSC Mains. The reason is that working through a derivation by hand, or sketching a free-body diagram or a circuit, engages spatial and procedural memory that typing a summary doesn't replicate well for STEM material — you learn a derivation by re-deriving it, not by reading a typed version of someone else's.

The actual failure mode isn't the choice of handwritten over digital. It's what happens to those handwritten pages over a year. By month ten, a typical GATE aspirant has a formula sheet started in month two, a fluid mechanics or circuits notebook, six months of error-log entries, and a photograph of a classmate's control-systems notes from a WhatsApp group — scattered across a physical file, two or three notebooks, and a phone gallery with four hundred other photos in it. None of that is a "make better notes" problem. It's a "where did I derive the entropy relation I needed in week fourteen" problem, and it surfaces at the worst possible time — the final revision month, when speed of retrieval matters more than at any other point in preparation.

This is the specific problem worth solving digitally, even though the actual note-taking stays on paper: photograph or forward handwritten pages as you make them, so a year of derivations and formula sheets is searchable by keyword instead of buried across notebooks. We've compared the tool options specifically for this in best app to organize GATE notes.

Revision: the final month

The last four to six weeks should contain no new topics. Shift entirely to full-length, timed mocks that reproduce the real three-hour format, and use every mock to stress-test your formula sheet against every wrong NAT — a wrong numerical answer almost always traces back to either a mis-remembered formula or a calculation slip under time pressure, and knowing which one it was changes what you fix. Keep General Aptitude in weekly rotation even now; it's the fastest section to lose sharpness on and the fastest to restore with a short, consistent practice slot.

Sources that actually hold up

General Aptitude and Engineering Mathematics are shared across almost every branch, so start there:

• General Aptitude — R.S. Aggarwal's Quantitative Aptitude for Competitive Examinations covers the numerical and verbal reasoning style GATE's GA section draws from.
• Engineering Mathematics — B.S. Grewal's Higher Engineering Mathematics remains the standard single reference across branches that include an Engineering Mathematics component.

Branch-specific texts vary too much to list exhaustively, so here are examples from two large branches — the same principle (pick one or two consistently recommended textbooks per subject, then stop hunting for a better one) holds for every other branch:

• Computer Science and Data Science — Operating System Concepts (Silberschatz, Galvin, Gagne), Database System Concepts (Silberschatz), Computer Networks (Tanenbaum), and Introduction to Automata Theory, Languages, and Computation (Hopcroft, Ullman, Motwani) cover the core CS subjects most GATE CS papers draw from; NPTEL's subject-wise lecture series pair well with all four.
• Mechanical Engineering — Fluid Mechanics and Hydraulic Machines and Strength of Materials, both by R.K. Bansal, Theory of Machines by R.S. Khurmi, and Engineering Thermodynamics by P.K. Nag are the standard references most GATE ME preparation plans build from.

For previous-year papers, the official GATE website archive published by the conducting IIT each year is the authoritative source, alongside compiled PYQ books from established exam-prep publishers. Computer Science and Data Science aspirants specifically benefit from GATE Overflow for discussion-level detail on how a question was actually meant to be solved.

A realistic weekly timetable

This assumes a working week with two to three hours available on weekdays and six to eight hours on weekends — a common split for final-year students and working aspirants alike. Adjust the hours, but keep the shape: a new topic early in the week, practice and PYQs mid-week, and a full test with review on the weekend once you've entered the PYQ and mock phases.

Common mistakes that cost GATE aspirants marks

• Reading textbooks cover to cover without solving problems. This produces recognition, not recall — and GATE tests recall under time pressure, not familiarity.
• Starting PYQs only after "finishing" the syllabus. For a syllabus this deep, that day rarely arrives on schedule, and PYQs are most valuable early, as a filter for what to prioritise.
• Not maintaining a formula sheet as you go. Trying to compile one from a year of scattered notes in the final month costs far more time than updating it weekly from month one.
• Treating General Aptitude as unworthy of dedicated time. It's 15 marks that don't need a year of preparation — a fixed weekly slot from month one earns most of those marks reliably.
• Skipping dedicated NAT practice. NAT questions have no negative marking, but also no elimination strategy and no partial credit — calculation accuracy under time pressure needs its own practice, not an assumption that "I know the formula" is enough.
• For Computer Science and Data Science aspirants, not engaging with PYQ discussion platforms like GATE Overflow. A textbook shows you a concept; a well-discussed PYQ shows you exactly how that concept gets turned into a question.

Can you prepare for GATE without coaching?

GATE sits in an interesting middle ground on this question. It's more self-study-friendly than an exam like UPSC, which has an interpretive Mains answer-writing skill that genuinely benefits from feedback — GATE has no such component. But it's less uniformly self-study-friendly than RRB or SSC, where the syllabus is narrow and largely memorisation-and-speed based. GATE's syllabus is genuinely deep, spans nine to twelve months, and a handful of topics in every branch are hard to self-teach from a textbook alone without some form of instruction.

Self-study works well if your undergraduate foundation in the branch is reasonably solid and you're willing to actually solve problems from NPTEL and standard textbooks rather than passively watching or reading. Coaching earns its cost mainly for two things: cohort-paced structure across a genuinely long syllabus, and instructor explanation for the small set of topics — often a few chapters in subjects like electromagnetic theory or control systems, depending on the branch — that resist self-teaching. If you have the discipline for a self-set timeline and access to a peer group solving the same PYQs, the syllabus itself doesn't require coaching.

What self-directed GATE aspirants underrate is what happens to a year's worth of collected material — the derivations, the formula sheets, the PYQ error log, the photographed notes from a study group. None of it is a "notes" problem exactly; it's a "where did I put it" problem that compounds over nine to twelve months until finding a specific derivation feels like re-deriving it from scratch. This is the specific problem Rehearsal exists for: forward whatever you're collecting — a photographed derivation, a formula sheet, a voice memo where you talked through a tricky NAT — and get it back later by asking, rather than by flipping through notebooks. If you'd rather query your own saved material without switching apps, the same collection is reachable directly from ChatGPT or Claude through Rehearsal MCP — you ask your own assistant mid-problem, and it answers from what you've actually saved.

Common questions

Q1: How many months are enough to prepare for GATE without coaching?

Most aspirants with a reasonably solid undergraduate foundation budget nine to twelve months, covering foundation, core practice, PYQs, and a proper mock phase. Someone starting core subjects from a weaker base, or with under six months on the clock, will find the depth GATE demands genuinely difficult to build in a compressed timeline, regardless of coaching.

Q2: Is GATE Overflow useful for branches other than Computer Science?

Not directly — GATE Overflow's community discussion is built around Computer Science and Data Science papers specifically. Other branches typically rely on compiled PYQ books, the official GATE archive published each year, and discussion within their own branch's study communities, which serve a similar purpose even without a single dedicated platform.

Q3: Should I make GATE notes by hand or digitally?

Handwritten remains the stronger choice for the actual note-taking — derivations, diagrams, and formula work engage recall in a way typing doesn't replicate well for STEM material. The problem worth solving digitally is retrieval: photographing or forwarding those handwritten pages so a year's worth of material stays searchable, rather than trying to replace handwriting with typing.

Q4: How important is General Aptitude in GATE?

More important than most aspirants treat it. At 15 of 100 marks, it's a meaningful share of the paper, and unlike the core subject, it doesn't require months of depth to master — a fixed weekly practice slot from month one typically earns most of those marks reliably, which makes neglecting it one of the costlier mistakes in this guide.

Q5: When should I start solving previous-year GATE papers?

Around month five or six, topic-wise rather than as full mixed papers initially. GATE reuses concept structures heavily across years, which makes early PYQ practice valuable as a prioritisation tool — it shows you which parts of a chapter actually get tested — not just as late-stage exam simulation.

Q6: Can I clear GATE with only NPTEL and no coaching?

For many aspirants, yes — NPTEL's lecture series closely track most GATE syllabi and are taught by IIT faculty, which covers the concept-building foundation coaching would otherwise provide. What NPTEL alone doesn't supply is a forced schedule, PYQ-solving discipline, and mock-test rhythm — those have to be self-imposed, and preparation tends to succeed or fail on whether that discipline actually holds over nine to twelve months.