I recently earned my CKA certification and have been studying Kubernetes seriously, but my current workplace uses Nomad and Consul instead. We also have some smaller-scale systems and non-containerized workflows, so Kubernetes has not been necessary.
I'm considering platform or SRE roles that request two or three years of production Kubernetes experience. I'm confident I can build and operate realistic clusters through personal work and substantial capstone projects, but I lack firsthand production stories involving incidents, migrations, outages, and scaling issues.
How quickly can experienced Kubernetes engineers spot exaggerated production experience during interviews? Would it be better to be completely honest rather than inventing work stories? I'm not trying to bluff my way through the entire job—I want to know whether a CKA, serious hands-on projects, and experience with Nomad and Consul can still make me competitive for roles that prefer production Kubernetes experience.
5 Answers
Don’t fabricate production stories. You may get through an interview, but experienced interviewers can usually probe details, and the gap becomes much more obvious once you are responsible for a real system. Be upfront that your current employer uses Nomad and Consul, then describe your Kubernetes labs and capstone projects in detail. Let the hiring team decide whether that background is enough.
Some teams care more about whether you can reason through problems and learn quickly than whether every tool was used at your current job. A clear explanation such as “my workplace uses Nomad, and I’m looking to move into an environment where I can operate Kubernetes professionally” is perfectly reasonable. Be ready for practical tests, since strong teams should evaluate skills rather than rely only on work anecdotes.
It is possible to exaggerate your way into a role, but it is a risky strategy. If you do not quickly close the production-experience gap, the pressure can be intense and your credibility can suffer. If you do get hired, spend the extra time learning the environment and be transparent about what you have and have not operated before.
Your Nomad and Consul background is not irrelevant. The transferable parts include scheduling, service discovery, deployment workflows, observability, failure handling, and operating distributed systems. Frame your Kubernetes work as hands-on preparation, not as production experience, and target roles whose requirements are preferences rather than absolute screening criteria.
A certification proves useful knowledge, but it is not the same as operating Kubernetes in production. There are operational issues—incident response, upgrades, networking failures, capacity planning, security, and organizational tradeoffs—that a certification cannot fully demonstrate. Your best approach is to present the CKA and projects honestly while treating your existing Nomad experience as relevant infrastructure experience.
That’s the distinction I’m struggling with. I feel technically fluent from the CKA and hands-on projects, but I’m missing the real-world incidents and operational history. I’ll focus on explaining that gap honestly rather than pretending those experiences happened.