C-DAC (Centre for Development of Advanced Computing) runs lab- and advertisement-specific loops for Project Intern, Project Engineer, and Scientist B. This page synthesizes round patterns, panel themes, and prep traps from public intern, Scientist B, and PE reports - not a single candidate diary.
What decided it: Precise web/OOP answers plus a clear full-stack Java project walkthrough under a Senior Project Engineer
Common fail: Listing HTML5/CSS/SSL or frameworks you cannot explain when pressed
How to practise: Rehearse HTML vs HTML5, responsive CSS units, OOP pillars, SSL one-liners, then a 3-minute project narrative with your own contributions
Technical interview experience 2 - Scientist B panel, 2025
Offline interview at Anusandhan Bhawan, C-DAC Noida in the shared account
~30-50 candidates across areas; DV then panel
Three panelists in room + three virtual in one description
Tip: Carry complete originals; expect a formal conference setup
Technical themes reported
MySQL vs PostgreSQL
Golang: goroutines, concurrency, race conditions (if Go on resume)
OS and networking basics
Hashing vs encryption (example from ScyllaDB work in that account)
Distributed systems; messaging queues and use cases
Deep follow-ups wherever interest spikes
Result: Learning-heavy panel; outcome per merit list
Tip: Every resume keyword is a hook - prune aggressively before applying
Key takeaways: Scientist B C-DAC interviews behave like research-lab boards - depth over buzzwords.
Takeaways
What decided it: Surviving deep follow-ups on every resume keyword (Go concurrency, MySQL vs PostgreSQL, hashing vs encryption)
Common fail: Padding the CV with languages or queues you only know by name before a hybrid in-room/virtual panel
How to practise: Prune the resume; for each remaining tool, prepare definitions, trade-offs, and one project anecdote; drill OS/networking and distributed messaging basics aloud
Written (CBT, ~60 min): 10 very easy aptitude MCQs plus 60 technical items - reported emphasis on OSI layers, attack types, symmetric vs asymmetric crypto, VPN/SSH acronyms, and “given code snippet, which attack applies?” rather than live coding.
Interview: Resume-led cybersecurity discussion after shortlist; candidate reported a rushed preliminary slot - panels still expect honest depth on whatever you list.
Prep takeaway: Domain notifications can swap the syllabus entirely; read desirable skills in the PDF as your study plan.
Stages reported: Online application → written MCQ when included (~100 questions, negative marking, ~40% weight on core CS: C/Java, OOP, DBMS, OS, networks) → technical panel (3–5 members) → HR/fit folded into the same visit for some drives.
Technical themes: OOP with real project examples, ArrayList vs LinkedList, REST flow, second-highest salary SQL, reverse linked list, sliding window - plus deep project ownership (“what breaks at 10× users?”).
HR/fit: Why CDAC, relocation to Electronic City/Pune-style centres, willingness for contract/project tenure.
Candidate profile: Intern or Scientist B candidate
Light fit prompts
Introduction and current work
Why C-DAC / why this domain
Willingness to work on government R&D project constraints
Final result: Usually folded into technical panel for Scientist B
Key takeaways: Motivation for public-digital / R&D mission should be concrete.
Sample answers for high-frequency questions
Use these as frames, not scripts.
Intern track
Q. HTML vs HTML5? A. HTML5 adds semantic tags, native audio/video, canvas, better forms, offline/storage APIs - less dependence on plugins. Give one semantic tag example you used.
Q. What is SSL/TLS? A. Cryptographic protocol securing data in transit - encryption, integrity, authentication via certificates. HTTPS is HTTP over TLS.
Scientist B track
Q. Hashing vs encryption? A. Hashing: one-way fingerprint for integrity/passwords. Encryption: reversible with keys for confidentiality. Example: store password hashes; encrypt PII at rest.
Q. Goroutine race condition? A. Concurrent memory access without synchronisation. Mitigate with channels, mutexes, race detector. Give a tiny shared-counter example.
These links are research inputs used to map C-DAC tracks, written themes, and panel habits - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.
Cross-check the current C-DAC advertisement and lab notification for domain syllabus and DV logistics.
