I recently earned the CKA and have been studying Kubernetes seriously, including building and operating realistic environments through several substantial personal projects. However, my current workplace uses Nomad and Consul instead, along with some non-containerized workflows, so I have not managed Kubernetes in production.
I'm applying for platform and SRE roles that often request two or three years of Kubernetes experience. I understand the technology well, but I'm missing firsthand production stories involving incidents, migrations, outages, scaling issues, and similar operational challenges.
How obvious is it to experienced interviewers when someone exaggerates their production background? Would it be better to present my CKA, projects, and Nomad/Consul experience honestly, or is that profile still competitive for roles asking for production Kubernetes experience?
4 Answers
Some companies will require direct production Kubernetes experience, while others will value strong fundamentals and adjacent infrastructure experience. Apply anyway, but target roles where the requirements are flexible and describe yourself accurately. If a company rejects you because it needs someone who can immediately own a large cluster, that is a hiring fit issue—not a reason to invent a background.
Be honest about the distinction between certification, personal projects, and production experience. A CKA demonstrates useful technical knowledge, and Nomad/Consul gives you relevant experience with scheduling, service discovery, operations, and troubleshooting. Explain that your current environment does not use Kubernetes and that this is one reason you are looking to move. A good employer should assess your actual skills rather than require you to repeat polished work anecdotes.
Interviewers can usually tell when someone has memorized a few Kubernetes stories but cannot explain the tradeoffs, failure modes, or follow-up details. Even if exaggeration gets you through an interview, being hired into a role based on invented experience can create a stressful situation for you and the team. It is safer to discuss your real projects in depth and prepare for practical troubleshooting exercises.
The CKA is useful, but it is not equivalent to years of running Kubernetes for a business. Production work involves change management, monitoring, capacity planning, security, incident response, upgrades, and communicating during outages. You can close some of that gap by documenting your projects like real services: define reliability goals, introduce controlled failures, practice upgrades and recovery, and explain the decisions you made. That gives you concrete experience to discuss without claiming it happened at work.
That seems like the strongest framing: be clear about what you have done personally and what you have not done in production, without underselling the operational experience you gained from similar systems.