Roadmap
GATE CSE preparation
Every GATE CS subject in an order that builds on itself, with free lectures and a quiz for each.
Who it's for
Final-year students and graduates aiming for GATE CSE, for M.Tech admissions or PSU jobs.
Where it leads
- M.Tech at IITs and NITs
- PSU engineer
- Research roles
By the end you can
- Cover the whole syllabus in a sensible order
- Solve GATE-style numericals quickly
- Know your weak subjects from timed mocks
- Walk into the exam having done every past paper
- 1
Know the exam, then start from past papers
Previous-year questions show what is actually asked, which decides how deep to go in each subject.
Do this: Attempt one full past paper cold before you start. Keep the score; it's your baseline.
- 2
Discrete mathematics and engineering maths
Sets, logic, counting, graphs, linear algebra and probability come up directly and sit under every other subject.
- 3
Digital logic and computer organisation
Number systems and gates lead straight into pipelines and caches, GATE's favourite numericals.
- 4
Programming, data structures and algorithms
The heaviest-weighted area: complexity, recurrences, trees, graphs, hashing and dynamic programming.
- CourseIntroduction to Algorithms (6.006)MIT OpenCourseWare
- VideoAlgorithms, by Abdul BariAbdul Bari. Clear whiteboard explanations, much loved by GATE aspirants.
- ToolVisuAlgo: watch algorithms runNUS
Do this: Work every recurrence and complexity question from the last ten papers by hand.
- 5
Theory of computation and compiler design
Automata, grammars and decidability, then how a compiler uses them. Mostly conceptual and very scoring.
- 6
Operating systems
Scheduling, synchronisation, memory management and file systems, with numericals to match.
- 7
Databases
ER models, normal forms, SQL, transactions and indexing.
- 8
Computer networks
Layers, IP addressing and subnetting, TCP and UDP, routing and the data link layer.
- 9
Full-length mocks and revision
Timed full papers expose the subjects you think you know. Revise the weakest two, then mock again.
Do this: One full mock every week for the last two months, each followed by a written error log.
Learning this with others is easier.
Ask questions when you're stuck, find people on the same path, and track your progress on DevLearn.