IBM·Software Engineer·Technical Phone Screen
May 2026
Technical screen for a DevSecOps role at IBM, pretty deep on Kubernetes tooling. The whole session basically revolved around ArgoCD and GitOps patterns, which I was not expecting to be the entire focus.
- How does ArgoCD implement the GitOps model, and why is Git treated as the source of truth for deployments?
- Walk me through the ArgoCD Application resource. What are the key fields and what does ArgoCD actually do with it?
- What is the difference between manual sync and auto-sync in ArgoCD, and when would you choose one over the other?
- How does ArgoCD reconcile the live cluster state against the desired state in Git? What happens when they drift?
- How would you handle multi-environment promotion with ArgoCD, for example promoting a release from staging to production?
- How do you roll back a deployment using ArgoCD, and how does that interact with the GitOps principle of Git being the source of truth?
“I gave a reasonable answer about Git holding the desired state and ArgoCD polling for changes, but I fumbled a bit explaining WHY that model is better than imperative kubectl commands.” The rest of the author's notes on Software Engineer interview at IBM, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post