Skip to content

How to Prepare for ISRO

ISRO is not a LeetCode contest. Written papers track core engineering + aptitude. Interviews probe fundamentals of your discipline and projects.

What ISRO actually tests

First round: ISRO written (discipline paper) + interview

Time split that matches how candidates report outcomes (not a marketing pie chart):

  • Technical/GATE topics 50%
  • Aptitude 30%
  • Interview 20%

Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.

Hiring flow you should prep for

Stage Time What they check
Written exam per notification Core technical + aptitude
Technical interview varies Subject depth + projects
HR / personality varies Fit and clarity

Time allocation

  • Core Engineering Subjects (40% time) - Focus on your discipline-specific knowledge (Aerospace, Electronics, etc.)
  • Space Technology Basics (25%) - Satellite systems, rocket propulsion, orbital mechanics
  • Aptitude & Reasoning (20%) - Quantitative aptitude, logical reasoning, verbal ability
  • Technical Interview Prep (10%) - Project discussions, space technology awareness
  • General Awareness (5%) - ISRO missions, recent achievements, space science

Daily loop (2-4 hours nearer to exam)

  1. One timed block that matches ISRO’s first round (written technical paper)
  2. Log misses: topic + why you failed (speed, concept, carelessness)
  3. Re-solve yesterday’s misses cold
  4. Twice a week: 10 minutes of resume/project narration out loud

8-12 week psu / core plan

Week Focus Exit criteria
1-4 Core technical syllabus from notification Topic checklist ~80%
5-6 Aptitude + previous papers Timed sectional accuracy
7-8 Interview revision Subject Q bank + project ready
9-12 (if time) Weak-topic closure + full mocks Stable mock scores

Round-by-round strategy

Written paper

  • Read the latest notification before any book list
  • Attempt previous papers under the real duration
  • Do not skip aptitude - it still rejects people
  • Mark uncertain technical questions and return only if time remains

Technical interview

  • Expect core-subject grilling from your branch, not LeetCode
  • Explain final-year / internship projects like an engineering review
  • If you do not know something, say so and reason from first principles

HR / personality

  • Why ISRO, willingness to relocate, long-term interest in the organization
  • Keep answers short and concrete - no corporate TED talk

ISRO-specific drills

  • GATE-style core subjects for your branch
  • Previous ISRO papers for pattern
  • Space systems basics only as relevant to role

Topic checklist

  • Official syllabus / advertisement
  • Previous year papers
  • Core subject depth for your branch

Final stretch

30 days out: finish syllabus once; start alternating previous ISRO papers and weak-topic revision.

7 days out: only previous papers + short notes. No new subjects. Sleep on a schedule that matches exam timing.

Day before: light formula/notes review, logistics (admit card, ID), stop grinding.

Common mistakes for ISRO aspirants

  1. Grinding DSA while ignoring core engineering syllabus for your branch - fix this first
  2. Preparing only interviews while failing ISRO’s first round
  3. Collecting notes without timed mocks
  4. Listing five frameworks on the resume and defending none
  5. Changing language/stack one week before the drive
  6. Copying FAANG DSA plans for GATE-style papers

Practice on this site

Comments & Suggestions

Similar companies

DRDO · BHEL · NTPC · BEL · BARC · CDAC