DevSecOps Kubernetes / CI-CD Technical Screen

A DevSecOps intern interview starts with self-introduction and resume deep dive, then asks rapid-fire infrastructure questions around CI/CD, Argo CD, Helm, Kubernetes troubleshooting, Linux, networking, database deployment safety, and generative AI at work. Requirements Prepare concise answers for the following topics: What CI/CD is, and which CI/CD tools you have used. How Argo CD deploys applications to Kubernetes. How Helm is used, and how Helm chart files are structured. How to troubleshoot a pod, including a JDBC pod in CrashLoopBackOff. HPC and VPC concepts. Why applications are containerised. Linux command to inspect process id 9003. Linux command(s) to find directories or files. Commands or tools used for network troubleshooting. Approach for making a database deployment safe. Thoughts on generative AI at work. Kubernetes StatefulSet vs Deployment. Notes The format is verbal and broad, not a coding exercise. Expect interviewers to pivot from resume projects into concrete tooling commands. For Kubernetes troubleshooting, structure the answer around kubectl describe, logs, events, image/pull/config issues, probes, resource limits, and dependency connectivity. Preparation Build a rapid-fire command sheet: kubectl describe pod, kubectl logs --previous, kubectl get events, ps -p 9003 -f, find, ss/netstat, curl, dig, and traceroute/tracepath. For Argo CD and Helm, practise one concrete deployment story: Git commit changes manifest values, Argo detects drift and syncs, Helm renders Chart.yaml, values.yaml, and templates/ into Kubernetes manifests. For database deployment safety, prepare a phased answer: backward-compatible schema change, migration plan, backup/restore point, health checks, canary rollout, and rollback criteria.