Learn from BARC OCES/DGFS Computer Science interview experiences for Scientific Officer roles. We synthesized GeeksforGeeks and GATE Overflow reports (2023-2025) into round tables and prep takeaways - written/GATE shortlist, then a deep board interview in Mumbai.
Prior job responsibilities and GATE rank discussed briefly (working professional path)
Wrote five subjects on the board; panel drilled OS, DBMS, CN, C, and COA in sequence
Interview ran ~1 hour 26 minutes - longer than many campus panels
Sample depth (reported clusters)
OS: logical vs physical address space, kernel stack, system calls vs page faults, deadlock conditions with resource allocation graph drawn on board, ostrich algorithm
DBMS: nth highest salary SQL, referential integrity, keys/constraints, storage on disk
CN: MAC vs IP, error detection vs correction, DNS caching TTL, Hamming distance
C: delete nth node of linked list with extensive edge-case cross-questions; recursive variant requested
What do you know about BARC and DAE centre locations?
Willingness to relocate to assigned centres
Result: Selected; funnel that year was extremely tight (nine selects from 178 interviewees in the same report - treat as one-cycle data)
Key takeaways: Panels chain “why?” across subjects you listed; COA and OS can consume 30+ minutes alone. Closing questions test posting realism, not trivia.
HR interview experience
HR interview experience
Candidate profile: Fresher or experienced CS candidate
Light HR inside the board
Tell us about your education / GATE journey
Master’s admits and next-year plans
For experienced hires: current role, why leave, why BARC / public sector research
Awareness of Scientific Officer training and posting
Final result: Technical depth dominates the decision
Key takeaways: Do not bluff career plans. Inconsistency on higher studies vs joining is a common trap.
Sample answers for high-frequency questions
Use these as frames, not scripts.
Technical
Q. Implement a queue - then survive follow-ups. A. Array circular queue or linked-list queue: enqueue/dequeue at opposite ends, empty/full conditions, complexity. Be ready for: why circular, wasted space, when to prefer linked list, thread safety if asked.
Q. How does a program become a process? A. Walk loading, memory image (text/data/heap/stack), PCB creation, state transitions (new → ready → running → waiting → terminated). Use the board. Expect interrupts and context-switch follow-ups.
Q. TCP vs UDP - when each? A. TCP: reliable, ordered, connection-oriented - file transfer, HTTP. UDP: low overhead, no connection - DNS, streaming, gaming. Know what “reliable” actually guarantees.
Q. SQL: person with 5th highest salary. A. Classic approaches: ORDER BY salary DESC with offset/limit (dialect-specific), or dense-rank window functions. Discuss ties - whether 5th means rank or distinct salary.
Fit
Q. Why BARC if you have corporate offers? A. Mission, research depth, and long-term technical ownership - tied to a subject you love. Avoid “government job safety” as your only line.
Q. Are you comfortable with classified / radiation-related service? A. “I read the OCES service conditions and understand DAE work can be sensitive and centre-based. I am applying because [specific technical mission], and I accept the posting and safety regime that come with it.” Do not claim comfort you have not thought through.
Q. Logical address space vs physical - why two spaces? A. User isolation and kernel protection; page tables map logical to physical; system call traps to kernel mode. Expect follow-ups on heap growth, kernel stack placement, and page faults - common in 2025 CS write-ups.
These links are research inputs we used to map round structure and recurring questions - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for BARC.
