Finally PLACED at C-DAC Pune 🔥 | CDAC Interview Experience | Questions Asked & Preparation

Summary of the Video (Subtitles)

Personal Update: Placement Success

• Parikshit announces that he has finally been placed through CDAC Pune.
• He explains that he attended an interview yesterday, and received the offer/confirmation by email the next day.
• After receiving the placement email, he also says he was blocked from the CDAC “Placement Management System (PMS)”, meaning he could no longer participate in further placement rounds.

Acknowledgements and Motivation

• He credits viewers/commenters for encouraging him, saying some advised him to be patient and that he would get placed.
• He mentions receiving negative comments from some viewers who claimed he “was not placed” or criticized his content; he responds that he ultimately got placed.
• He also credits someone he met earlier who works at CDAC for guidance, but says he hasn’t confirmed whether he can publicly name them.

Role and Interview Context

• Parikshit says the placement was for the role of Project Associate with a security/network defense focus.
• He frames the role as potentially aligned with either:
  • Cybersecurity, or
  • Network/security operations (he later references terms like SOC / NOC / SIEM).

Explanation of the Selection Process (Two Rounds)

• He describes the interview as having two rounds (yesterday morning and a second round after).
• He says he had very little food during the first round and felt unwell.
• He was interviewed first because of his high percentage, which led to him being shortlisted earlier than other candidates.

---

Round 1: Questions He Faced

He lists technical questions including:

• Self/introduction, project explanation, and “your role in the project”
• Cybersecurity concepts and implementation
• Linux knowledge and command-based (CLI) questions
• What to do when a system crashes (recovery/response)
• PKI (Public Key Infrastructure)
• Symmetric vs asymmetric cryptography, plus general cryptography
• Confidentiality vs integrity
• Why security is important and how to justify using multiple security tools
• CI/CD pipeline explanation (he implies he struggled with parts)

He admits he couldn’t answer multiple questions, and emphasizes an interview strategy: if you don’t know, don’t make things up—instead, say you don’t know and/or that you will follow up.

Location/Relocation Discussion (After Round 1)

• After Round 1, he was told there was no vacancy at the location he expected.
• He was told about client locations in Bengaluru and New Delhi.
• He says he felt anxious and reluctantly agreed to relocate because he wanted the job and others advised him to focus on getting placed.

---

Round 2: Scenario-Based Security/Network Questions

In the second round, he reports more scenario-based questions, including:

• Switch vs router
• A networking scenario involving two virtual machines not communicating within the same vs different networks, and how to “shoot/determine” connectivity (interpreted as troubleshooting communication issues)
• DHCP / DSR / DSCB-type acronym questions (the transcript is unclear, but he asks about configuring something related to DB/DS-style networking/security components)
• CI/CD pipeline again
• SCA and SLA concepts
• NOC / SOC / EM / SIEM-type security operations concepts (the transcript is noisy, but it clearly involves security monitoring terms)

He also says he forgot some questions afterward, reinforcing that the interview required broad preparation.

---

Final Decision and Outcome

• He says the interview ended with them confirming the role/location preferences, and then he was allowed to leave.
• After a waiting period, he received a mail confirming he was placed at CDAC Pune.
• He summarizes the experience as: hard work led to results, even though he felt unsure during the process.

---

Broader Message: Expectations vs. Unpredictability

• He shares his belief that the thing you expect most often doesn’t happen, but unexpected outcomes can occur.
• He uses examples from his life (including his channel monetization) to argue that results may arrive when you least expect them.
• Final advice: don’t over-stress, be patient, and trust that outcomes can come unexpectedly.

---

Presenters / Contributors

• Parikshit (presenter/narrator)