HR interview questions
Common DRDO HR questions, sample answer frames, and STAR tips.
DRDO Interview Experiences
How DRDO fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
DRDO placement process includes: 1. Written Examination (90 minutes) - Technical questions based on discipline, general aptitude (quantitative, logical reasoning, verbal ability), general awareness, English, 2. Technical Interview (60 minutes) - Detailed discussion into engineering subjects, defence technology questions, project discussion, 3. HR/Personality Round (30 minutes) - General discussion, motivation, behavioral questions. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 6.5+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): ₹8-12 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Written / CBT | 120 min | Technical + aptitude |
| Technical Interview | 30-45 min | Core subjects + basic programming |
| HR / Document verification | 20-30 min | Bond, location, background |
Real interview experiences
Section titled “Real interview experiences”Public DRDO write-ups are thin compared with private-sector companies, and they split across two very different tracks: the RAC / Scientist ‘B’ route (GATE score → subjective written paper → panel interview) and the CEPTAM STA-B / Tech-A route, which is decided by Tier-1 and Tier-2 CBTs with no interview at all. The two accounts below are rewritten from public student posts on the Scientist ‘B’ route.
Experience 1: Scientist ‘B’, RAC panel at New Delhi (Feb 2023)
Section titled “Experience 1: Scientist ‘B’, RAC panel at New Delhi (Feb 2023)”Source: GeeksforGeeks write-up
Before the panel
- Phones and personal items are not allowed in the waiting room, only documents. Originals are verified and attendance marked before candidates are called in.
Panel interview
- Five members on the panel. The candidate reports being asked their name and then taken straight into questions, with no room for a rehearsed introduction.
- Asked to name three or four favourite subjects, then questioned across them, and per the write-up from outside them as well.
- Questions reported: OSI vs TCP/IP models, semaphores and where they are used, phases of a compiler, a matrix-rotation program, and basic security / cryptography.
Takeaway from the write-up: prepare all core subjects, not just the ones you nominate. The author specifically warns against naming Computer Networks as a favourite subject unless you are comfortable with the security side of it.
Experience 2: written paper plus interview, GATE-shortlisted (2019-20 cycle)
Section titled “Experience 2: written paper plus interview, GATE-shortlisted (2019-20 cycle)”Source: GeeksforGeeks write-up
Shortlisting and written stage
- A valid GATE score was needed just to be called for the written exam; the write-up quotes a CSE cutoff of 576 (OBC) for that cycle.
- The written stage was two subjective papers on the same day, roughly 9 am-12 pm and 2 pm-5 pm, not an MCQ test.
Interview (about 45 minutes, five-member panel)
- DSA: find the position of a given character in an array.
- Networks: explain what a URL is; walk a packet down and back up the OSI layers.
- OS / networking: logical vs physical addressing, what a MAC address is.
- Software engineering questions, then a project discussion.
Result: Not selected. The candidate attributes it to interview performance, citing limited prep time alongside a master’s course and weak answers on software engineering.
Takeaway: the panel goes broad rather than deep-tricky. Breadth across OS, CN, compilers and software engineering, plus a project you can defend, matters more than contest-style DSA. Note the calendar too: this cycle ran written in November and interviews the following February.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Basic C output and pointers. Usually expects language fundamentals
- Stack vs queue use-cases. Usually expects DSA basics
- Core-subject numericals from your branch. Usually expects domain depth
- Discussion on core technical and GATE-style depth, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this organisation / PSU?
- Bond acceptance
- Preferred posting
- Willingness to relocate
Practical tips for DRDO
Section titled “Practical tips for DRDO”- 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 DRDO 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
Section titled “HR interview”After technical rounds, DRDO 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.