Skip to content

DRDO Interview Experience 2026

DRDO hiring is not one loop. Scientist ‘B’ (RAC/GATE) is a deep oral board on your discipline; CEPTAM posts use CBT and trade tests; campus/internship tracks can mix written filters with project-heavy technicals. This page synthesizes RAC panel patterns and intern screens into round tables, outcome notes, and prep traps - confirm your advertisement before you prep the wrong track.

Round-wise process at a glance

Track Stages (typical) What clears you
Scientist ‘B’ (RAC) GATE shortlist → Personal Interview → docs/medical GATE rank + panel depth; meet qualifying interview %
CEPTAM (STA-B / Technician-A) Multi-tier CBT → trade/skill test → verification/medical Aptitude + trade syllabus + hands-on skill
Campus / intern (varies) Written/aptitude screen → technical interview(s) Fundamentals + project ownership + clear reasoning

Technical interview experience 1 - Scientist B, RAC New Delhi (CSE)

Technical interview experience 1

Candidate profile: GATE-shortlisted CSE candidate; Scientist ‘B’ interview 11 February 2023, RAC New Delhi. Source: GeeksforGeeks - DRDO Scientist B RAC New Delhi.

Day logistics
  • Arrived as one of the last candidates that day; long wait after document check
  • Waiting room: staff verify originals; attendance marked; mobile phones not allowed in the wait area
  • Panel of five members; minimal warm-up - questions started quickly after name
Opening - favourite subjects
  • Asked to name 3–4 favourite subjects (not a long “tell me about yourself” monologue)
  • Candidate listed: Compiler Design, Computer Networks, Operating Systems
  • Panel drilled those subjects sequentially, then spilled into adjacent topics
Technical clusters recalled
  • CN: layer mechanisms, VPN working, heavy security/cryptography follow-ups
  • Compiler: phases of a compiler
  • OS: semaphores and applications
  • Coding: square root program; matrix rotation program
  • Concepts: OSI vs TCP/IP stack differences
  • Advice from candidate: prepare basic coding; only claim CN if comfortable with security/crypto; expect questions outside your favourite list

Key takeaways: RAC CSE panels treat “favourite subjects” as a contract - depth beats breadth. CN as a favourite invites the hardest security grilling.

Takeaways

  • What decided it: Surviving sequential drills on named favourites (compiler, CN, OS) plus basic coding (sqrt, matrix rotation)
  • Common fail: Listing Computer Networks without VPN/crypto readiness, or expecting a long soft intro before technicals
  • How to practise: Pick 3 favourites and drill each to security/adjacent depth; write matrix rotation on paper; expect spillover topics

Technical interview experience 2 - Scientist B, RAC Timarpur (CSE, ~30 min)

Technical interview experience 2

Candidate profile: CSE GATE candidate; 16 March 2023, RAC Timarpur, Delhi. Panel of five; mixed Hindi/English. Source: LinkedIn - Aryan Raj DRDO CS interview.

Logistics
  • Waiting room had a digital display of entry/exit times
  • Digital tablet for writing answers (projected live); candidate notes no pen/paper
  • Duration about 30 minutes; chairperson-led, calm tone
Project + algorithms
  • Brief intro; B.Tech project on CNN - why CNN, architecture explanation
  • Ternary search: recurrence relation; compare to binary search; when ternary is preferable
  • Coding: partition array of 0s/1s; code + time complexity + recurrence relation
  • Scenario: minimum fuel refills on a bike route (greedy/DP framing)
  • Knapsack: definition and CS importance
  • DS conversion: queue ↔ stack with code
Core CS fundamentals
  • SDLC purpose; which phase covers testing
  • Testing: regression vs acceptance testing
  • TOC: Turing machine; why TOC matters
  • OS: deadlock, kernel depth, host vs guest OS
  • Additional networking questions followed in the same sitting (candidate truncated public note)

Key takeaways: Even a “short” RAC slot can stack project + coding + SE + TOC + OS. Tablet writing practice helps.

Takeaways

  • What decided it: Clear CNN project rationale, ternary-search vs binary reasoning, and tablet-written code with complexities
  • Common fail: Freezing on digital-tablet writing, or blanking when the panel stacks SDLC/TOC after algorithms
  • How to practise: Code on a tablet or stylus once; prepare project “why this architecture”; drill deadlock, Turing machines, queue↔stack conversions

Technical interview experience 3 - Scientist B, RAC Delhi (maths + DSA depth)

Technical interview experience 3

Candidate profile: Experienced engineer (Power Grid background) interviewing for Scientist ‘B’; ~1 hour 20 minutes; tablet provided. Source: LinkedIn - Shobhit Pal.

Opening
  • Five-member panel; digital tablet with pen
  • Favourite B.Tech subjects stated: C programming, DSA, Discrete Maths, Engineering Maths, DBMS
Programming and DSA
  • Prime numbers 1–1000 program
  • Swap two numbers using pointers; pointer definitions
  • Search in array of 100 elements; matrix storage in memory
  • Hash functions; best DS for phone directory (primary/secondary indexing)
  • Equivalence partitioning (testing concept)
Maths and architecture
  • Birthday paradox-style probability in a class of 50
  • Prove (AB)⁻¹ = B⁻¹A⁻¹; eigenvalues/eigenvectors; symmetric matrix properties; Cayley–Hamilton theorem
  • Non-singular matrices under multiplication - group or not?
  • Cache purpose; pipelining stages
  • Matrix exponentiation-style probe (A^200 type question)
  • Marksheet-driven question on Scientific Computing course content
Motivation close
  • Direct question: why leave Power Grid for DRDO?
  • Result: Selected (candidate-reported interview score 78; qualifying thresholds often cited as 70 UR / 60 reserved in RAC ads)

Key takeaways: Non-freshers should prep job narrative + maths/DSA together. Panels read marksheets and pull course names.

Technical interview experience 4 - Scientist B, RAC Delhi (ML + crypto + OS)

Technical interview experience 4

Candidate profile: M.Tech background; Scientist ‘B’ interview 10 August 2024, RAC Delhi. Source: LinkedIn - Mohammad Wasif Ansari.

Academic opening
  • Discussion on M.Tech subjects and thesis topic before split technical panels
Panel 1 - ML and data structures
  • Supervised ML: SVM; brief Naive Bayes
  • Linked list vs array efficiency trade-offs
  • BST advantages for search/traversal
Panel 2 - cryptology and probability
  • Modern cryptology vs cryptography
  • Authenticity of message A→B (digital signatures)
  • Probability: independent/conditional, total probability, random variables
Panel 3 - operating systems
  • OS core functions: device drivers, I/O, disk management
  • IPC: shared memory vs message passing

Key takeaways: Postgrad candidates should expect thesis-first questioning, then sequential panels that each go deep in one lane.

Technical interview experience 5 - Scientist B selected (ML + blockchain focus)

Technical interview experience 5

Candidate profile: Selected Scientist ‘B’ (candidate-reported GATE 844/1000, interview 70/100, final 81.52/100). IIT Bombay M.Tech; ~60–70 minutes; five-member panel. Source: LinkedIn - Harsh Raj.

Machine learning (major time sink)
  • Linear regression → cost function / MSE intuition
  • Gradient descent and learning-rate effects
  • Backpropagation and chain rule
  • Optimizers (e.g., Adam) - sequential depth at each step
Blockchain + architecture + project
  • Block structure, headers, Merkle trees and why they matter
  • Computer architecture: registers; instruction fetch cycle
  • Project Q&A: normal vs ML-based retrieval; single- vs multi-vector retrieval
  • DSA application: tries in search engines
Candidate advice
  • Expect 1–2 domains grilled deeply, not shallow coverage everywhere
  • Logical flow matters more than buzzwords
  • Minimum qualifying interview marks often 70 (UR) / 60 (reserved) per RAC advertisements - verify your year

Key takeaways: If ML/blockchain/architecture is on your transcript, RAC can treat it as primary ammunition for follow-ups.

Technical interview experience 6 - Research intern / campus-style screen

Technical interview experience 6

Candidate profile: CSE aspirant for a DRDO research intern role (public GFG account). Source: GeeksforGeeks - DRDO interview experience.

Rounds
  • Written test filter, then technical interview(s)
  • Mix of theory and coding problems
  • Heavy weight on projects and fundamentals; AI/ML depth if listed on resume
What helped
  • Medium DSA set with complexity proofs spoken aloud
  • Project ownership story (design choices, failures, metrics)
  • Defence/embedded angles when relevant: memory limits, reliability

Key takeaways: Intern loops resemble a compressed campus written + technical - not the full RAC Scientist tablet board, but still project-first.

HR / personality interview experience - Scientist B (RAC)

HR and motivation round

RAC Scientist selection often folds motivation into the technical panel rather than a separate HR stage. Recurring non-technical prompts from public accounts:

Common motivation prompts
  • Why DRDO over corporate PSU/private sector (expect honesty - “national security template” answers fall flat)
  • Why leave current employer (for experienced candidates)
  • Posting / relocation constraints and family considerations
  • Integrity / antecedent verification themes (official process includes character verification per RAC ads)
Separate HR-style tracks
  • Some campus/written advertisements describe a ~30 min personality/HR module after technicals (motivation, posting, communication)
  • CEPTAM routes emphasise document verification and medical fitness rather than a startup-style culture HR

Framed answers and STAR stories: DRDO HR interview questions.

Sample answers for high-frequency RAC prompts

Q. Why DRDO instead of a higher-paying private job?
A. Anchor on problem horizon and lab fit, not slogans: “My thesis/project was on [specific area]. DRDO’s [lab/programme family] works on [named defence-tech domain]. I want to build depth there for years, not ship a six-month feature cycle. I accept the Level 10 pay band and non-metro posting as part of that trade.”

Q. They picked a favourite subject you claimed - then pushed past your comfort zone.
A. State boundaries early: “I can explain semaphores and deadlock prevention; I am weaker on advanced crypto proofs - I will attempt the definition and stop if I am guessing.” Panels respect honesty more than bluffing (multiple candidates report being “broken down” on one concept - persistence still matters).

Q. Write code on the tablet while the panel watches the projected screen.
A. Talk while writing: restate constraints → brute force → optimise → state time/space → mention edge cases. For partition/array problems, mention two-pointer vs counting sort trade-offs before coding.

Q. Ternary vs binary search - when is ternary actually useful?
A. Binary search halves the space each step (O(log n) comparisons). Ternary splits into thirds; constant factor is worse for simple sorted arrays, but ternary can appear in unimodal function optimization on continuous domains. On discrete sorted arrays, prefer binary search unless the interviewer defines a specific ternary-friendly structure.

Q. Digital signatures vs encryption for message authenticity?
A. Encryption gives confidentiality; authenticity needs a signature (hash of message encrypted with sender’s private key, verified with public key) or MAC in symmetric settings. DRDO security questions often probe this distinction after VPN/TLS discussions.

Dense prep checklist

  • Route check: RAC Scientist ‘B’ vs CEPTAM vs intern - three different syllabi
  • GATE depth notes for 4–5 defensible subjects; expect spillover
  • Project redraw: architecture diagram, limitations, why-not alternatives
  • Tablet practice: write algorithms legibly under observation
  • Coding set: primes, matrix ops, partition, square root, pointer swaps - with complexity spoken
  • Motivation: one honest “why this lab/discipline” sentence; posting constraints decided upfront
  • Marks awareness: know your advertisement’s GATE/interview weightage and qualifying interview thresholds
  • Logistics: originals, no phone in wait room, long queues near day end

Sources

These links are research inputs used to map DRDO RAC boards, tablet logistics, and intern screens - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.

Confirm track (Scientist B vs CEPTAM vs intern) against the current RAC/DRDO advertisement.

Similar companies

ISRO · BARC · BEL · BHEL · CDAC