I have about 10 years of progressively responsible experience in Windows and infrastructure administration. Over the past three months, I've been learning DevOps practices, Linux, cloud platforms, containers, and Kubernetes, and I'm comfortable with the basic Kubernetes concepts so far. I've built a hands-on project using Terraform, Azure, AKS, Docker, CI/CD pipelines, security scanning, Helm, Argo CD, Prometheus, and Grafana. I understand how the different layers fit together, although I relied on AI tools for some of the application and configuration work. I'm wondering how realistic it is to move into DevOps or Kubernetes-focused roles, whether entry-level Kubernetes positions are available, and what hiring panels typically expect from someone with my infrastructure background.
4 Answers
Be open to pivoting based on the role rather than treating Kubernetes as the end goal. Kubernetes is a tool in a larger platform: Linux, networking, cloud fundamentals, Git, infrastructure as code, security, observability, and automation all matter. Applying for DevOps or cloud infrastructure roles that value your existing experience may be a more realistic first step than searching only for Kubernetes administrator positions.
Your 10 years of infrastructure experience means you aren’t really starting from zero. Networking, storage, troubleshooting, operations, and understanding how systems fail are all valuable DevOps skills. The main caveat is that dedicated entry-level Kubernetes jobs are relatively uncommon, and hiring has been slower recently. You may have better results targeting DevOps, cloud infrastructure, platform engineering, or site reliability roles where Kubernetes is one part of the job.
Keep building the project, but make sure you understand every part well enough to explain and troubleshoot it without blindly relying on AI-generated configuration. Be prepared to discuss why you chose each tool, how Terraform state is protected, how secrets are handled, how the pipeline is secured, how deployments are rolled back, and how you would diagnose an unhealthy workload. A small project you can confidently defend is more impressive than a large stack you can only describe at a high level.
This should be a manageable transition, but focus on practical troubleshooting rather than memorizing Kubernetes theory. A hands-on CKA preparation course is a good way to test and strengthen your skills, even if you don’t immediately take the exam. Interviews often present a realistic cluster problem—such as a failed deployment, networking issue, broken readiness probe, or storage problem—and ask how you would investigate it. Be ready to explain the commands, logs, events, and reasoning you would use.
That kind of course is especially useful because the labs force you to work through realistic problems instead of just watching demonstrations. The troubleshooting practice is probably more valuable than the certificate by itself.