Academic snapshot
Marks: 65% or 6.5+ CGPA throughout (candidate-reported / many advts)
Degree: B.E./B.Tech/M.E./M.Tech/M.Sc/PhD in listed fields
Backlogs: None active
Age: Typically 18-35 for entry (advt wins)
DRDO is India’s premier defence research and development organisation, established in 1958 with more than 50 laboratories nationwide. Its scientists and engineers work on missiles, radar, aeronautics, and electronics, making it a respected destination for freshers seeking government R&D careers.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
DRDO is a government defence R&D hirer. The academic floor is often 6.5 throughout. The real cut is usually a GATE score plus a RAC panel, not a HackerRank OA. Campus written papers exist; they are not the only door, and they are not JTO.
| Route | What usually changes | What stays the same |
|---|---|---|
| RAC Scientist B | GATE paper/year, tablet panel | Core subject depth |
| Campus / written advt | 90-min mixed paper | Project + discipline |
| NATS / GTRE apprentice | CGPA + resume; no Scientist conversion | Not a Level 10 offer |
Off-campus RAC does not mean easier thermodynamics. It means your GATE rank is the first number they see.
Is 6.5 CGPA enough? It matches the commonly reported floor across 10th, 12th, and graduation. Selection still hinges on GATE/written and whether you can defend a project on a tablet. A 6.6 with a clean GATE and a real project beats an 8.8 who cannot derive a transfer function.
Age: Often 18-35 for entry Scientist posts, with category relaxation as per government rules. The advertisement wins. Do not guess.
Citizenship: Indian citizens for these posts.
Gaps and backlogs: Active backlogs are a usual blocker. Keep a clean story for any gap. Full-time regular degrees.
What helps the resume/GATE screen: Discipline match to the lab, GATE paper code, one project you can redraw from memory. See certifications after core subjects, not instead of them.
Academic snapshot
Marks: 65% or 6.5+ CGPA throughout (candidate-reported / many advts)
Degree: B.E./B.Tech/M.E./M.Tech/M.Sc/PhD in listed fields
Backlogs: None active
Age: Typically 18-35 for entry (advt wins)
Skills they actually filter
Written / GATE: Discipline technical
Panel: Project, fundamentals, defence context
Tools (role-dependent): MATLAB, C/C++, Python
CS posts: Algorithms + systems at GATE depth
| Item | Typical expectation | Reality check |
|---|---|---|
| Graduation | 65% or 6.5 | Advertisement wins |
| 10th & 12th | Same throughout when listed | Keep scans |
| Branches | Wide STEM list | Match lab / GATE paper |
| Backlogs | None active | Offer-stage check |
| GATE | Required on RAC Scientist B | Year and paper code matter |
Good fit: You like deep core subjects, you can live with a lab city that is not always a metro product office, and you can explain a project without slides.
Harder path: You only grind DSA; you want a 20 LPA product CTC; you applied to JTO and Scientist B with the same PDF; you cannot name one DRDO lab in your discipline.
Download 2026 DRDO placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
DRDO does not publish one permanent unofficial dump that matches every lab. Papers on this site are pattern trainers for discipline technical, aptitude, and interview talk, not leaked RAC scripts.
| Round (typical) | What to practice |
|---|---|
| GATE (RAC path) | Your GATE paper at full depth |
| Written / CBT | Discipline MCQs + aptitude + awareness + English |
| Technical panel | Project, fundamentals, applications |
| HR / personality | Motivation, posting, integrity |
| Apprentice (if that is your form) | Resume + CGPA; not Scientist prep |
People searching DRDO placement and DRDO JTO often land on the same results. They are not the same path.
| Intent | What it usually means | Covered here? |
|---|---|---|
| Scientist B / lab entry | GATE+RAC or advertised written + interview | Yes |
| JTO / JE / telecom board | Separate competitive exam | No - official syllabus only |
| NATS apprenticeship | Training year, often CGPA+resume | Contrast only, not Scientist |
| Theme | Drill next | Why DRDO asks it |
|---|---|---|
| Core MCQ | GATE PYQ in your paper | Written / panel |
| Negative marking | Skip rule, no wild guesses | 0.25 on many CBTs |
| Project | Assumptions, limits, redo | Every panel |
| Lab match | ADE vs DRDL vs LRDE vs NSTL | Posting talk |
| Tablet | Write, do not only type | RAC 2023 note |
Use this only if your advertisement has a mixed written paper. RAC/GATE candidates should stay on their GATE syllabus.
| Discipline | What the technical block usually feels like |
|---|---|
| Aerospace | Aero, propulsion, structures, flight mechanics |
| Electronics | Circuits, signals, comms, embedded, EM |
| Mechanical | Thermo, SOM, design, manufacturing |
| CS / IT | DSA, OS, CN, DBMS, TOC, C/C++ output |
| Electrical | Machines, power, control, measurements |
| Civil | Strength, RCC/steel basics, surveying |
| Physics / chem / maths | Core M.Sc topics plus numerical aptitude |
Do not study all seven rows. Study the row that matches your degree and GATE paper.
If 0.25 is printed: attempt what you can derive in 45 seconds. Leave the rest. A 60% accurate technical section beats a 90% attempted section with guess damage. Mark for review only if you have a real second idea, not a vibe.
CEPTAM (technical/admin staff) is a different notification. Scientist B is the Level 10 research-entry story on this hub. NATS apprentice is a training year. Mixing PYQs across the three is how people waste August.
Week calendars live on the preparation guide. This H2 is the focus split.
| Bucket | Share | What “done” looks like |
|---|---|---|
| Core discipline / GATE | ~40% | PYQs you can derive, not only tick |
| Project + tablet talk | ~25% | Diagram from memory |
| Written extras (if named) | ~20% | Aptitude + awareness + skip rules |
| Defence context + HR | ~15% | One lab sentence + why-DRDO |
If you are RAC/GATE-only, cut aptitude to maintenance and spend the 20% on weaker GATE topics. If you have a 90-minute campus paper, do not hide in a research paper the night before.
Week A: daily core revisions; project redo; one mock written if applicable.
Week B: tablet derivations; viva with a friend who interrupts; documents folder; sleep.
You want long-horizon hardware/software research with a national-security constraint, not a six-month consumer app. You know the lab family that matches your degree. You accept the Level 10 band and a posting that may not be Bengaluru product culture. That is enough. “Serving the nation with cutting-edge synergy” is how people sound like a template.
Confirm the year and paper code on the RAC PDF. A 2025 GATE CS score does not automatically fill a 2024 mechanical Scientist seat. If you are dual-degree, read which qualifying degree the advt wants. Do not assume M.Tech waives GATE unless the PDF says so.
Mon-Tue: discipline PYQs, timed 50-minute blocks.
Wed: aptitude + English, skip rules.
Thu: awareness: three DRDO headlines in your branch, not a GK dump.
Fri: full 90-minute mock.
Sat: error log only.
Sun: project redraw + sleep.
If you are GATE-only, replace Wed/Thu with your weakest GATE unit.
Share core depth. Change the story: space vs defence vs production PSU vs DAE exam. Do not reuse a “why ISRO” paragraph on a DRDO HR. Do not quote BEL CTC on a Level 10 form.
DRDO hires through RAC / GATE, advertisements (Employment News / drdo.gov.in), and select campus cells. After eligibility, the shape depends on the notice name.
RAC / GATE
Scientist B shortlist from GATE. Interview at RAC (Delhi and other centres). Tablet panel in recent CS notes.
Advertisement / Employment News
Follow the PDF: dates, paper pattern, lab, age, fees.
Campus / NATS
College drive or apprentice portal. Read whether it says Scientist or trainee.
Pass habit: speak while you write on the tablet. A correct idea you cannot show is a silent fail.
CS-flavoured panel (from the 2023 note): project architecture, a search/coding probe, a classic DP (knapsack), then core CS (SDLC, TOC, OS, networks). That is GATE-depth oral, not a startup LLD. Bring a pen in your head even if they give a tablet.
Core-flavoured panel: expect a derivation, a “what if we change this assumption,” and a defence application. If you only memorised MCQ keys, the follow-up kills you.
Written (~90 min, ~100-120 Q, 0.25 negative on many papers)
| Section | Questions (reported) | Time feel | Focus |
|---|---|---|---|
| Technical (discipline) | 60-70 | ~50 min | GATE-style core |
| General aptitude | 20-25 | ~20 min | Quant, logical, verbal |
| General awareness | 10-15 | ~10 min | Defence, DRDO, current |
| English | 10-15 | ~10 min | Grammar, RC |
Pass habit: do technical first. Skip a 2-minute blank rather than eat a negative. Student rumours put written pass around 15-20%. Your key wins.
Technical interview (~60 min): fundamentals, one defence application, project. MATLAB/C/Python if the lab is computational.
HR / personality (~30 min): why defence research, posting, family constraints, integrity.
GTRE 2024-25 GFG: CGPA + resume, no written described, not a permanent Scientist conversion. Prep like a training year, not Level 10.
| Phase | Typical duration | Notes |
|---|---|---|
| GATE + RAC form | Months (national calendar) | Not a 2-week campus sprint |
| Campus written | 1 day | Results 1-2 weeks in some notes |
| Interview | 1 day (tech + HR often same day) | RAC may be a single panel |
| Offer / joining | Weeks | Medical + documents |
| Campus-style end to end | ~2-4 weeks after written in some drives | RAC is a longer season |
You will not pick a lab like a product team. Still know where your subject lives:
One lab + one sentence of “my project maps to X” is enough. A 52-lab recitation is not.
If you cannot map the project in one sentence, rewrite the sentence this week. The panel will ask.
Scientist offers commonly run document verification and a medical. Category claims need certificates that match the form. A 12th mark that does not match the “throughout 65%” story is a joining-week problem, not a “we will see.” Keep scans in one folder the day you apply, not the day RAC mails.
Write large. Derive, do not only talk. If you need a diagram, sketch it. The panel sees the same screen. Practise once on a tablet or iPad before you fly to Timarpur with only a gel pen in your head.
10th, 12th, degree, GATE scorecard, photo ID, category certificates if used, experience if any. Throughout 65% means the 12th marksheet is not optional.
Online assessment
Written/OA format notes and timing.
Coding questions
Light DSA for CS-heavy 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 DRDO 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 DRDO 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 and advertisement floors commonly cite 65% or 6.5+ CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/M.Sc/PhD in listed engineering or science disciplines; Indian citizenship; age often 18-35 for entry Scientist posts (relaxation as per govt norms); no active backlogs; full-time degrees. GATE score is the usual shortlist for RAC Scientist B. Always verify the specific recruitment adve.
What you are training for: Two fresher-shaped paths appear. Scientist B (main): GATE score → RAC interview (often tablet-based panel) → document/medical. Campus or advertised written tracks: written/CBT (~90 min, discipline technical + aptitude + awareness + English) → technical interview (~60 min) → HR/personality (~30 min). Apprenticeship (NATS) is a separate non-permanent track. Read the notice name.
Short version of the prep split: Split time roughly: 40% core discipline (GATE-depth for your branch), 25% defence/lab awareness and your project, 20% aptitude/English if a written paper is named, 15% interview talk (tablet practice, motivation). Coding is secondary except CS posts. Full plan: /drdo/preparation-guide/.
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the DRDO 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 DRDO 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 DRDO 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 DRDO?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. 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 DRDO-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 DRDO story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed DRDO papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many DRDO papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in DRDO-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Scientist pay follows 7th Pay Commission levels. City HRA (and posting) changes take-home. Figures below mix gazette basics with candidate-reported all-in bands (as of August 2026).
| Level | Typical basic (7th CPC) | All-in feel (candidate-reported) | Notes |
|---|---|---|---|
| Scientist B | ₹56,100-1,77,500 (Level 10) | ₹8-12 LPA | Fresher entry |
| Scientist C | ₹67,700-2,08,700 (Level 11) | ₹12-18 LPA | Experience / later entry |
| Scientist D | ₹78,800-2,09,200 (Level 12) | ₹18-25 LPA | Not campus default |
| Scientist E (indicative) | Level 13 band | ₹25-35 LPA | Senior research |
Confirm the written offer and posting city. HRA 24-27% of basic appears in many govt tables by city class.
HRA, transport allowance, CGHS-style medical, leave, pension/NPS language as applicable, lab facilities, higher-study support on some programmes. Job security is the government story. Remote-only is not.
Know Level 10 basic and that all-in depends on city. Do not demand Flipkart SDE-1 numbers. Do not pretend you never heard of a lab posting outside a metro.
HRA is the big city swing. Transport and medical are the next two. NPS/pension language depends on the year of the rules in your offer. Do not plan a Bengaluru product lifestyle on Level 10 basic without reading HRA for the actual posting city.
Some scientists later do M.Tech/PhD with lab support. That is a joining-year question for HR, not a reason to skip GATE now. “I will leave for a US MS in eight months” is a bad panel answer.
Net for 2026: prepare as a scientist candidate. Core first. Project second. Written aptitude only if the PDF names it.
Lab cities include metros and non-metros. RAC will not redesign the lab around your rent. If you cannot go, say so before you celebrate a GATE shortlist. Relocation is not a puzzle. It is a yes/no that should already be written on paper.
National Scientist B seats are advertised, not whispered in one college WhatsApp. If your cell never hosts DRDO, you still apply through RAC when the PDF is live. Campus written is a bonus door, not the only one. Bookmark drdo.gov.in and the RAC page the same way you bookmark a product careers site. Screenshot the advertisement PDF the day it drops; paper codes and age lines change between cycles.
Yes. Start with the 2026 PDF or the archive. Scientist/lab-entry trainers, not JTO leaks.
RAC Scientist B: GATE → panel → documents. Campus-style: written (~90 min) → technical → HR. Apprenticeship is separate. About 2-3 weeks after a campus written in some notes; RAC follows a longer calendar.
RAC is often GATE + one panel. Campus loops report 3 stages. Count the advertisement.
No. Different notification and syllabus. Do not reuse these tables for JTO.
Many student-reported written papers use 0.25 per wrong answer. GATE has its own scheme. Read the key.
Commonly 65% or 6.5 throughout; listed STEM degrees; Indian citizen; age per advt (often 18-35 for entry). Your notice wins.
For RAC, yes, usually. Campus written and NATS are other doors. Match the form.
Aerospace, ECE, Mechanical, CS, Electrical, Civil, Materials, Physics, Chemistry, Maths, and related as listed. Lab follows discipline.
Level 10 basic ₹56,100-1,77,500/month plus allowances. Candidate-reported all-in often ₹8-12 LPA. City HRA matters.
Core/GATE 40%, project 25%, written extras 20% if named, defence/HR 15%. Guide: preparation guide.
CS/electronics computational posts: yes, at GATE depth (C/C++/Python/MATLAB). Core mechanical/aerospace: do not skip thermo for LeetCode.
No. GTRE 2024-25 notes: CGPA+resume, no permanent conversion.
DRDO is defence systems. ISRO is space. BEL is more production/electronics PSU flavour. BARC is DAE/research with its own exam. Share core depth; do not copy one interview story onto all four.
Own the project on a tablet. Know one lab mapping. Do not mix JTO PYQs into a RAC week.
DRDO interview experience plus the GFG apprentice and LinkedIn RAC notes below.
CEPTAM is a separate technical/admin staff notification. Scientist B is Level 10 research-entry, usually GATE+RAC. Do not mix PYQs.
Usually no, not like picking a product team. Know one lab family that matches your discipline so posting talk is not a blank stare.
Shortlisted via NATS/grade form. Writer: “The selection is based solely on your CGPA/Grades and the strength of your resume,” with no written exam described for that apprenticeship track, and an explicit note that the year does not convert to permanent appointment. Source: GeeksforGeeks DRDO apprenticeship.
Takeaway: useful contrast. Do not prep GATE for a form that only wants CGPA, and do not treat the year as Scientist B.
~30-minute panel of five. Project CNN architecture, ternary search, coding, knapsack, SDLC/testing, ToC, OS, networks. Logistics: “No paper or pen was used.” A digital tablet was provided and answers were projected live. Source: LinkedIn RAC note.
Takeaway: after GATE, the bar is thinking on a tablet in front of five people. Practise that medium.
What helped: GATE-depth notes; project redraw; skip rules on negative papers; one honest why-lab sentence.
What hurt: JTO dumps; silent tablet; mixing apprentice and Scientist; quoting 18 LPA product CTC; arriving without 12th scans.
A project team and a problem you are assigned, often with classified or export-control constraints. “I will only do GenAI research” is a bad HR answer. “I will own the core problem in this lab’s area and I already rebuilt my GATE notes” is the Scientist B answer. Keep that sentence ready.
More narratives: DRDO interview experience.
ISRO · BEL · BARC · BHEL · NTPC · CDAC
Last updated: August 2026.