Academic snapshot
Marks: 65% or 6.5 CGPA throughout 10th, 12th, graduation
Degree: B.E. / B.Tech / M.E. / M.Tech / M.Sc as listed
Backlogs: None active on most ads
Age: Per notification (often ~35 + relaxations)
ISRO is India’s national space agency, founded in 1969 and headquartered in Bengaluru, responsible for satellite launches and space exploration missions. Fresh engineering graduates typically join as Scientist/Engineer SC through the ICRB recruitment exam, working on rockets, satellites, and deep space programs.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
ISRO is not a campus HackerRank drive. The printed floor is often 65% throughout. The real cut is a hard discipline written, then a multi-member panel.
| Route | What usually changes | What stays the same |
|---|---|---|
| ICRB SC notification | National written + interview | Core depth |
| Campus talk / MoU | Awareness only on most colleges | You still sit the national paper |
| JRF / RA | GATE/NET/PhD rules | Different pay and tenure |
Off-campus here means the official website, not Naukri easy-apply. A college PPT is not an offer.
Is 6.5 CGPA enough? It matches the commonly reported floor. Selection still hinges on written rank and the panel. A 6.7 who can derive on a board beats a 9.2 who only memorised Chandrayaan dates.
Branches: As listed: Electronics, Mechanical, CS, Electrical, Civil, Aerospace, some science degrees. The PDF is the list.
Age: Often up to 35 with relaxations. Read the ad.
Gaps and backlogs: Active backlogs are a usual blocker. Medicals exist.
What helps: GATE-depth notes, one project with a diagram, mission literacy you can defend. See certifications after the written syllabus, not instead of it.
Academic snapshot
Marks: 65% or 6.5 CGPA throughout 10th, 12th, graduation
Degree: B.E. / B.Tech / M.E. / M.Tech / M.Sc as listed
Backlogs: None active on most ads
Age: Per notification (often ~35 + relaxations)
Skills they actually filter
Written: Discipline technical + some aptitude/space
Panel: Derivations, project, fundamentals
Coding: Role-dependent, not the SC default bar
Tools: C/Python/MATLAB helpful
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 65% or 6.5 | Notification wins |
| 10th & 12th | Often same throughout rule | Keep scans |
| Discipline | As advertised | No “any branch” fantasy |
| Backlogs | None active | Confirm ad |
| PhD | Research posts, not default SC | Separate ad |
Good fit: You like hard fundamentals, you will relocate to a centre, and you will put months into a written paper.
Harder path: You only grind LeetCode; you recite missions you cannot explain; you want a 25 LPA product title; you refuse every centre except one city.
Download 2026 ISRO placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
ISRO publishes official notifications and, at times, previous question flavour through student memory. Papers on this site are pattern trainers. Official previous papers and GATE-depth core are the real volume.
| Round (typical) | What to practice |
|---|---|
| Written / CBT | Discipline MCQs, negative marking, some aptitude/space |
| Panel | Project + board derivations + fundamentals |
| HR slice | Why ISRO, centre, integrity |
| Medicals / docs | Throughout % and fitness |
| Theme | Drill next | Why ISRO asks it |
|---|---|---|
| GATE-depth core | Official PYQs in your paper | Written |
| OS/DBMS/CN (CS) | Board explanations | 2024 Bengaluru panel |
| Signals/control (ECE) | One derivation | Electronics SC |
| Thermo/structures (Mech) | Sketch + assumption | Mechanical SC |
| Mission literacy | PSLV vs GSLV in your words | Panel curiosity |
ISRO hires through isro.gov.in notifications, not a standing campus OA. After eligibility, the shape is government science: written, panel, medicals.
Official notification
Apply on isro.gov.in. Download the PDF. Note exam city and discipline code.
Campus awareness
Useful for dates. Not a backdoor.
Research fellowships
JRF/RA have different bars and pay. Do not mix with SC prep.
65% / 6.5 throughout when printed, listed discipline, age, nationality rules. Gate.
Student-reported working map:
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Technical (discipline) | 50-60 | ~60 min | Core engineering |
| General aptitude | 20-25 | ~20 min | Quant, logic, verbal |
| Space awareness (some) | 10-15 | ~10 min | Missions, launchers, satellites |
Pass habit: 0.25 negative means skip guesses that are worse than 25%. Student rumours: 15-20% written pass. Your notification wins.
Multi-member. Project first. Then fundamentals on a board. CS example: OS, DBMS, networks, security. ECE/Mech: branch core + application. They grade whether you think, not whether you memorised a mission list.
Pass habit: derive. If you forget, say the next equation you would write. Fake confidence on a wrong Kepler number is worse than “I will set it up this way.”
Why ISRO, centre, joining, integrity. Know Level 10 basics. Do not quote a 30 LPA product CTC.
As per ad. Centre on the letter.
| Phase | Typical duration | Notes |
|---|---|---|
| Application window | Weeks | Official site |
| Written | 1 day | Centres or CBT |
| Result | 1-3 weeks (varies) | Shortlist for interview |
| Panel | 1 day (slots) | ~30 called in one Bengaluru note |
| Offer / medicals | Weeks | Letter wins |
| End to end | Often 4-8+ weeks after written | Not a 2-week IT OA |
A project is not “I used Python.” Say: input → processing → output → what breaks. Interviewers want the chain. Silent “it worked in the lab” is the fail.
CS example: web app → sessions → SQL injection risk → what you actually sanitised. ECE example: filter → transfer function → one pole you can sketch. Mech example: heat sink → conduction path → one assumption.
Saturday 10:00: 90-minute discipline paper with negative marking.
Saturday 12:00: rewrite five concept misses.
Saturday 16:00: 25-minute board project.
Sunday 11:00: five mission explanations in your words.
Sunday 12:00: why-ISRO and centre yes/no.
Two weekends of that beat a mission-trivia binge.
10th, 12th, degree, ID, category certificates if any. Throughout 65% means the 12th PDF matters.
Written result → slot mail → DV morning, panel afternoon (as in the 2024 Bengaluru note) or similar. Screenshot the admit card. If the ad never mentioned coding contests, do not panic-build LeetCode 300. If it named Electronics, do Electronics.
Pick the five technical items you guessed. Rewrite the assumption. Speak one derivation to a wall. Re-reading 40 mission FAQs you already “know” is how people feel busy and still fail networks or thermo.
Carry a habit, not a marker. Every mock, start with:
That sequence is what a 25-minute panel can grade. A speech about “passion for space” cannot.
SC is a regular scientist/engineer post with Level 10 pay. JRF is a fellowship with a stipend and usually a GATE/NET/PhD bar. Preparing a JRF statement of purpose for an SC written is wasted motion. Read the post name twice.
They are not hiring you as a PI. They are hiring someone who can learn a subsystem and not freeze on fundamentals. A B.Tech project with a measurement is enough. A fake arXiv paper is worse than none. If you have a conference poster, say what you personally did.
One Bengaluru note: about 30 students interviewed that day, 25 minutes each. You cannot charm the written cutoff. You can make sure a board story exists before the 30 become offers without you.
Day 1-3: only your weakest core subject, timed 30-minute slices.
Day 4-5: full 90-minute mixed paper, negative marking on.
Day 6: project board + five mission sentences.
Day 7: light formula sheet, sleep, travel plan for the centre.
Do not start a new textbook on day 6. Do not debate exam-city politics on Telegram until 1 a.m. The written does not care. The 15-20% who pass mostly slept.
Any one of those can end a 25-minute slot early. Honesty about a gap or a weak elective is recoverable. Integrity fails are not.
Admit card, photo ID, and the certificates the PDF listed. Reach the city the night before if the centre is not local. A 25-minute panel after an overnight bus is how people blank a handshake they have drawn ten times. Eat. Carry a print of the project block diagram if it helps you start writing faster. Do not carry a cheat sheet you would be embarrassed to have fall out. If DV is the morning before the panel, keep copies ordered: 10th, 12th, degree, ID, category if any. A missing 12th marksheet is a dumber fail than a hard networks question.
Pair them with official papers.
Online assessment
Written/OA format, timing, and question types.
Coding questions
C/Python practice for CS-flavoured panels.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a ISRO invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for ISRO sits around ₹8-12 LPA (candidate-reported - confirm the letter). Languages students mention most often: C++, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Candidate-reported floor is often 65% or 6.5 CGPA across 10th, 12th, and graduation. Degrees commonly listed: B.E./B.Tech/M.E./M.Tech/M.Sc in the advertised discipline (Electronics, Mechanical, Computer Science, Electrical, Civil, Aerospace, and sometimes Physics/Chemistry). Age typically 18-35 with GoI relaxations. No active backlogs. Research fellow posts may need NET/GATE/PhD as per that ad. Verify isro.gov.in.
What you are training for: Scientist/Engineer SC usually: apply on the official notification → written/CBT (discipline paper, often with negative marking) → interview (multi-member panel, ~25-45 min) → medicals and offer. Some notes mention a short HR/personality slice the same day. Timeline is often weeks to months, not a 2-week campus OA. Campus awareness sessions do not replace ICRB.
Short version of the prep split: Split time roughly 50% core engineering (GATE depth), 20% ISRO/space literacy at fresher level, 15% aptitude if the paper includes it, 15% panel talk (project + derivations on a board). Full plan: /isro/preparation-guide/.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the ISRO previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most ISRO drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at ISRO usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why ISRO?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a ISRO-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the ISRO story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed ISRO papers on three different days, then interview prep on the leftovers.
Week calendars live on the preparation guide. This H2 is the focus split.
| Bucket | Share | What “done” looks like |
|---|---|---|
| Core written | ~50% | Timed papers, error log |
| Space literacy | ~20% | Five missions you can explain |
| Aptitude (if in paper) | ~15% | Accuracy under negative marking |
| Panel + centre | ~15% | 25-minute board + city yes |
If you are CSE who only codes, stop LeetCode for two weeks and sit OS/DBMS/CN at GATE depth. If you are ECE who only reads ISRO tweets, add control systems and communications PYQs.
Week A: daily 45-minute core; one board session.
Week B: two full 30-minute mocks with a friend who interrupts; why-ISRO recorded twice; documents scanned.
You want to apply your discipline to launchers, satellites, or applications. You will go to the centre on the letter. You know Level 10 is not a product ESOP. That is enough. “I have always dreamt of the stars since childhood” only works if you can also derive.
You do not need every elective. You need representatives:
For each type, do three timed, then explain one to a roommate in 90 seconds.
ISRO is not trying to be TCS and not trying to be Google. The written brand is real. The 25-minute Bengaluru panel is also real. You can be CS or Mechanical; both still have to derive. You cannot outsource fundamentals to a dump PDF. You cannot skip the written because a senior said “they only care about passion.” Read your advertisement. Then practise both.
If ISRO, DRDO, and NTPC all land the same season, compare centre vs plant vs lab, exam path, and the letter. Do not pick on brand memory from a 2014 news clip.
If 0.25 is printed, a random guess among four options is negative EV. Skip when you cannot eliminate two choices. Students who “attempt all 100” to look hardworking donate marks. Mark for review only if the interface allows going back. Some CBTs do not.
ISRO written is not GATE. It often rhymes. Use GATE PYQs for depth. Then sit ISRO-style timed papers for flavour and negative marking. Do not skip ISRO space-awareness items because “GATE does not ask them.” Do not skip GATE-depth control systems because “ISRO only asks missions.”
Bengaluru, Thiruvananthapuram (VSSC), Sriharikota (SHAR), Ahmedabad (SAC), and others appear in student talk. You will not pick like a private-job location preference form. You will say whether you will join the centre on the letter. If you cannot leave your state, this may not be your organisation. Decide before the written fee, not after a 25-minute panel you are proud of.
Figures below mix pay-matrix facts and candidate-reported all-in totals (as of August 2026).
| Track | Typical pay | Notes |
|---|---|---|
| Scientist/Engineer SC | Level 10 basic ₹56,100; ₹8-12 LPA all-in in student notes | DA/HRA extra |
| Junior Research Fellow | ₹31,000-35,000 / month | Separate ad |
| Research Associate | ₹47,000-54,000 / month | Usually PhD |
| Technician / SA (indicative) | Lower bands | Diploma/B.Sc posts |
Confirm the written offer. Centre HRA changes the take-home.
Medical, leave, pension/NPS as applicable, training, mission work, government stability. Ask HR about centre. Do not assume only Bengaluru.
Know Level 10 exists. Do not negotiate like a startup. One calm question on posting beats a CTC argument.
Net for 2026: do not prepare as if this were Infosys or a marketplace SDE loop. Sit the paper. Own a board.
Bengaluru is HQ and a common interview city. Joining can be another centre. Write a yes/no this week. Students who “will decide after the offer” stall joining.
If the PDF and a coaching poster disagree, the PDF wins. Students who prepare “ISRO GK” from 2018 booklets and skip their branch paper are the 80% who never see the 25-minute slot.
You will not command a launch. You will join a division, learn a subsystem, write notes, test, and sit reviews. The panel is checking whether you can learn. A B.Tech who can derive is more useful than a brochure reciter. That is why OS/DBMS showed up for a CS candidate in Bengaluru. Space literacy is the seasoning. Fundamentals are the meal.
If the paper has 20 aptitude items, they are a bonus you should not fail, not a section to “max.” Spend your first 60 minutes on technical. Come back. Guessing the last five verbal items under 0.25 is how people donate marks they earned on control systems. Practise a 15-minute aptitude sectional once a week, not a 3-hour CAT course.
Explain your project to a Mechanical friend if you are CS (or the reverse). If they cannot follow the diagram, the panel will not either. Jargon that only your lab partner knows is a fail. Plain boxes and one equation are a pass. Do this twice before the slot. It is cheaper than a paid mock and closer to a multi-member room. Record one 25-minute session on your phone. Watch where you stall. Those stalls are the only syllabus that matters the night before. If you stall on the first equation, write the knowns anyway. A panel can coach a started derivation. They cannot coach a blank board and a speech about missions.
Yes. Start with the 2026 PDF or the archive. Pair with official previous papers.
Typical SC path: official apply → written/CBT → panel interview → medicals. Often 4-8+ weeks after the written, not a 2-week campus OA.
Written plus one substantial panel (HR often same day). Count the notification.
Student-reported ~90 minutes, 80-100 items, heavy technical, some aptitude/space, often 0.25 negative. Details: online assessment.
Commonly 65% or 6.5 throughout; advertised discipline; age per ad; no active backlogs. Your PDF wins.
SC is Level 10 (₹56,100 basic). Student-reported all-in often ₹8-12 LPA (as of August 2026). The written offer is the only number that matters.
Those listed on the advertisement: often ECE, Mech, CS, EE, Civil, Aerospace, some M.Sc. Not “any branch.”
Roughly 50% core written, 20% space literacy, 15% aptitude, 15% panel. Guide: preparation guide.
No. You need a real B.Tech project you can derive, plus honest mission literacy.
C/C++, Python, MATLAB depending on role. Core written still comes first.
ISRO is space centres via ICRB. DRDO is defence labs. NTPC is plant ET via GATE. Compare posting and the letter.
Sit the written like GATE. Then own a 25-minute board. Do not memorise a mission brochure you cannot defend.
ISRO interview experience plus the GFG note in the stories section.
No. The letter names the centre. Say yes or no before you celebrate a written shortlist.
DV 11 August 2024, interview 12 August. “Approximately 30 students were called for the interview on that day.” One slot started 12:30 and lasted about 25 minutes. Multi-member panel on OS/DBMS/networks/security, B.Tech project, whiteboard derivations. Source: GeeksforGeeks ISRO Scientist SC Bengaluru.
Takeaway: 25 minutes is short. Lead with the project. Derive, do not speechify.
What helped: GATE-depth notes, a board sketch, honest “I have not flown a satellite” plus a real lab project.
What hurt: mission trivia without mechanism; fake internships; arguing CTC; refusing every centre.
Explain your B.Tech project in five minutes.
That is an SC-level close. A 12-slide “vision for Indian space” pastiche is not.
You will not cover all of OS, DBMS, CN, and security. Lead with the project. When they pick OS, pick one process vs thread plus one scheduling or deadlock example you can finish. When they pick DBMS, pick normalisation or a join plus one integrity idea. When they pick networks, pick TCP vs UDP or a 3-way handshake you can draw. When they pick security, pick one real control you used (hashing passwords, sanitising input), not a movie hacker story.
If they ask a derivation, start writing. Silence while you “think of the best answer” eats the slot. A messy correct setup beats a polished wrong slogan.
ECE: one communications block, one control sketch, one circuit you can analyse. Mech: one thermo or structures sketch, one manufacturing or materials sentence tied to launchers only if you actually studied it. Do not volunteer propulsion trivia you cannot defend.
You should be able to say, in your words:
Five honest sentences beat fifty memorised dates.
More narratives: ISRO interview experience.