ISRO Scientist/Engineer SC (Computer Science)

ISRO Scientist/Engineer 'SC' (Computer Science) Recruitment Exam

More study resources

About this exam

The ISRO Scientist/Engineer 'SC' recruitment in Computer Science is the entry route into India's space programme for engineers who want to build software for satellites, launch vehicles, ground stations and data centres. The post is advertised by ISRO's centralised recruitment board, and selection begins with a written examination in the discipline; candidates who clear it move on to whatever further stages that advertisement specifies. It suits final-year BE/BTech (or equivalent) computer science and IT graduates, as well as working professionals, who are comfortable with a full undergraduate CS curriculum - engineering mathematics, digital logic, computer organisation, programming and data structures, algorithms, theory of computation and compilers, operating systems, databases, networks, software engineering, and programming languages and web technologies. Nothing in the syllabus is exotic; the difficulty comes from breadth under time pressure. Preparation should be syllabus-first: download the official advertisement and syllabus, map every topic to one standard textbook, and revise your own condensed notes instead of hoarding new material. Because the paper rewards accurate recall across many areas, spaced revision with periodic full-length practice under timed conditions beats deep dives into a single favourite subject. Track weak topics weekly and revisit them rather than restarting from chapter one.

What you'll study

Common questions

About ISRO Scientist/Engineer SC (Computer Science) preparation

What is the format of the ISRO Scientist/Engineer SC Computer Science paper?

It is a multiple-choice written examination in the Computer Science discipline, testing the full undergraduate syllabus. The official advertisement and the ISRO recruitment portal state the current mode (paper-based or computer-based), number of questions, duration and marking scheme for that cycle, so always confirm the details there rather than relying on second-hand accounts.

How hard is it compared with GATE CS?

The core subjects are close to GATE level, but the paper is broader: it also leans on software engineering, computer organisation, programming languages and web technologies, which GATE largely skips. Depth per topic is usually a little lower; the challenge is covering everything and staying accurate. Treat GATE material as a base and add the extra areas.

How much time do I need to prepare?

A fresh graduate typically needs four to six months of steady study, while someone revising after GATE can compress this into two or three. The binding constraint is breadth, not depth, so plan backward from the exam date with one revision pass for every two first-pass topics, and protect weekly practice-test slots.

In what order should I study the subjects?

Start with mathematics, digital logic and computer organisation, since later subjects assume them. Then data structures and algorithms, followed by theory of computation, compilers and operating systems. Databases and networks come next, and finish with software engineering and web technologies, which are largely memory-based and best revised close to the exam.

Is there negative marking, and should I guess?

Negative marking and guessing rules change between recruitment cycles and are stated only in the official advertisement and instructions to candidates. Read that document before the exam and calibrate your attempt strategy accordingly. If the scheme is unclear to you, answer only where you can eliminate options with confidence.

How many attempts am I allowed, and can I retake it?

There is generally no fixed cap on attempts; eligibility is governed by age, qualification and the conditions in that year's advertisement. Candidates commonly reappear in later cycles. Check the current notification for the age relaxation and eligibility clauses that apply to your category before planning a retake.

Why do most candidates fall short?

Three recurring reasons: over-investing in one favourite subject while leaving software engineering or computer organisation untouched, reading new books instead of revising, and poor time allocation in the paper. A fourth is relying on memory of past questions rather than understanding, which fails when the paper shifts emphasis.

What score do I need, and what is the cutoff?

Cutoffs vary each cycle with paper difficulty, the number of candidates and category-wise reservation, and the board publishes them as part of its results process. ISRO's official portal is the only reliable source for the current figure. Aim well above the previous cycle's mark rather than targeting it exactly.

Should I use GATE preparation material?

Yes for the overlapping core: algorithms, data structures, theory, compilers, operating systems, databases, networks and discrete mathematics. But supplement it, because this paper also tests software engineering process models, testing, web technologies and computer organisation details that GATE-focused notes cover thinly or not at all.