ISRO Interview Experiences

How ISRO fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

ISRO placement process includes: 1. Written Examination (90 minutes) - Technical questions based on discipline, General Aptitude (Quantitative, Logical Reasoning, Verbal Ability), Space Technology questions, 2. Technical Interview (60 minutes) - Detailed discussion into engineering subjects, space technology questions, project discussions, 3. HR/Personality Round (30 minutes) - Motivation, interest in space technology, behavioral questions. Total duration: 4-6 weeks from application to offer.

Eligibility (from student reports): 6.5+ CGPA in 10th, 12th, and graduation.

Fresher package ballpark (from student reports): ₹7-8 LPA. Confirm on your offer letter.

How to use this page

Read the round table first, then the experiences. Practise the coding patterns with edge cases, and keep one clear story each for ownership, conflict, and a project failure.

Round-wise process

Round	Duration	What they test
GATE score or ICRB written test	~90 min, ~80 Qs	Discipline-specific technical (no aptitude section)
Technical Interview	~25-45 min	Core subjects + project defence, before a large panel
Document verification	-	Certificates, category, eligibility (usually the day before the interview)

Real interview experiences

ISRO is not campus hiring, so there is no “OA → 3 rounds → HR” story to tell. Scientist/Engineer ‘SC’ recruitment runs through the ISRO Centralised Recruitment Board (ICRB), and the whole thing comes down to one shortlisting score plus one panel interview. Public write-ups are correspondingly thin - a single 25-minute interview does not generate much to report. Here is what recurs.

How selection actually works

• The shortlist is score-driven, not resume-driven. In recent ICRB cycles the Computer Science, Electronics and Mechanical disciplines are shortlisted on GATE score (the score, not the marks or the AIR), commonly quoted at a 1:7 ratio against vacancies. Other disciplines and other post types still use an ICRB written test - objective, discipline-specific, around 80 questions in 90 minutes with negative marking - and shortlist at roughly 1:5, subject to a floor on total candidates.
• The interview carries half the weight. Reported and notification-quoted merit is 50% written/GATE + 50% interview, with a minimum of 50% in each stage and a 60% aggregate for unreserved candidates (relaxed for reserved categories). Unlike PSUs where the interview is confirmatory, at ISRO you can genuinely lose or win here.
• Document verification happens the day before, and the interview the next day - candidates report being called to a centre for both.
• Always read that cycle’s official ICRB advertisement. Weightage, shortlisting basis and eligibility have changed between notifications.

Experience 1: Scientist/Engineer ‘SC’, Computer Science (Bengaluru, 2024)

• Panel size is the thing people are unprepared for. This account reports a panel of 10 members on paper, 6 present on the day. Other CS write-ups describe 7-8 senior scientists. There is a whiteboard in the room and you will be sent to it.
• Duration ~25 minutes. Around 30 candidates were interviewed that day across morning and afternoon slots.
• Subjects covered: Operating Systems, DBMS, Computer Networks, and Security, which was pushed hardest in this account. Plus a defence of the B.Tech project.
• The panel did not stay inside the candidate’s stated favourite subjects. The write-up’s own takeaway is that questions came from random areas of core CS - so a two-subject prep strategy is risky here even though you are asked to name preferences.
• Expect derivations and problem-solving on the board, not verbal-only answers.

What other candidate accounts add

• Interviews commonly open with the final-year or current job project and an instruction to explain it on the board. That explanation sets the tone for everything after it.
• Panels ask which subjects you have prepared and will draw from them, but design/open-ended problems tend to come from your named favourites while factual questions can come from anywhere in the syllabus.
• The consistent prep advice across accounts is unglamorous: solid CS fundamentals - algorithms, data structures, OS, DBMS, computer networks - rather than competitive-programming depth. There is no coding round.

Sources: GeeksforGeeks - ISRO Scientist SC, Bengaluru · GeeksforGeeks - ISRO exam pattern and syllabus · Quora - ISRO CS interview experiences · Candidate blog write-up · official ICRB notification for your cycle

Questions that come up often

Coding / technical

1. Basic C output and pointers. Usually expects language fundamentals
2. Stack vs queue use-cases. Usually expects DSA basics
3. Core-subject numericals from your branch. Usually expects domain depth
4. Discussion on core technical and electronics/CS fundamentals, bottlenecks, failure modes, simple APIs
5. Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

1. Why this organisation / PSU?
2. Bond acceptance
3. Preferred posting
4. Willingness to relocate

Practical tips for ISRO

• Clear the screening round first. Timed practice beats last-minute topic hopping.
• For domain questions, explain core technical in plain language, inputs, outputs, what breaks at scale.
• OOPs and SQL still open a lot of ISRO panels. Do not skip fundamentals.
• HR answers should be concrete. One story with a result beats five slogans.
• If you do not know something, say so and outline how you would find out.

HR interview

After technical rounds, ISRO usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common ISRO HR questions, sample answer frames, and STAR tips.

Similar companies

DRDO · BHEL · NTPC · BEL · BARC · CDAC