Focus on the practical benefits: every change is auditable, rollbacks are a git revert, and the repo is the single source of truth for what is deployed.
Look for: understanding of GitOps principles (declarative desired state, versioned in Git, automatically applied, self-healing), tools used (ArgoCD, Flux), benefits (audit trail, rollback, consistency), and challenges (secrets management, handling drift, learning curve). Best candidates discuss when GitOps is appropriate and when simpler approaches suffice.
Modern DevOps practice. Not all environments need GitOps, but understanding the approach shows current knowledge. Ask: "What challenges did you face adopting GitOps?"