I've had several interviews where Kubernetes experience in a production environment was listed as a requirement. None of my previous employers used Kubernetes, although I understand the core concepts and have deployed workloads on AKS as a personal learning project. I'm wondering how to build credible experience, whether certifications or a public project would help, and if it's ever acceptable to claim production experience that I don't actually have.
4 Answers
Focus on being able to explain what you actually built and operated. Saying, “I haven’t run Kubernetes commercially yet, but I managed this AKS environment and can walk you through a failed deployment, the debugging process, and the design decisions,” is much stronger than simply claiming production experience. A small, well-documented project where you have dealt with failures is valuable because production experience is largely about handling things when they break.
Don’t lie on your resume. Experienced interviewers can usually expose an invented production background quickly by asking how you handled node drains, failed deployments, CrashLoopBackOffs, incident response, monitoring, or cost problems. If you’re caught, you could lose the job and gain a reputation for being unreliable.
Instead, describe your AKS work honestly and make it more substantial. Run a real service, add resource requests and limits, monitoring, logging, alerting, GitOps with something like Argo CD, and practice rolling back broken releases. A public repository and a short write-up explaining an incident, the fix, and the tradeoffs you made can demonstrate much more than a vague resume claim.
You may be targeting roles that are too specialized for your current experience. Look for broader DevOps, platform, cloud, or Linux-focused positions where Kubernetes is one part of the environment rather than the entire job. Be clear that you have professional experience with related areas such as Linux, containers, monitoring, and cloud infrastructure, plus hands-on AKS experience. A team may be willing to teach you its internal practices if your fundamentals are strong.
Keep in mind that at some companies Kubernetes is not a small side responsibility; it is the main platform. Those teams may need someone who can contribute immediately, so applying to less Kubernetes-heavy roles may produce better results.
Certifications can help get past initial screening, especially the KCNA or KCSA as entry-level options, and the CKA or CKS if you want a more hands-on credential. They won’t replace professional experience, but they can validate your knowledge and show that you’re serious. Pair the certificate with a practical project rather than relying on the credential alone.
It doesn’t need to be a commercial product. Hosting something useful for friends or family, such as a game or collaboration server, can still give you real operational problems to solve and discuss honestly.