CKA Got Me the Interview. It Didn’t Get Me the Offer
The badge showed up in my inbox first. A clean little PNG, “Certified Kubernetes Administrator,” the kind of thing you screenshot and post without really thinking about why. A few weeks later, a different email showed up: “We’ve decided to move forward with other candidates.”
Nobody warns you that these two emails can arrive so close together. One says you’re qualified. The other says you’re not. Both, apparently, were true.
Why I thought CKA was enough
I’d been doing DevOps for six years by the time I sat the CKA exam — running production Kubernetes, managing autoscaling at real scale, the kind of work where “just restart the pod” isn’t a strategy, it’s a confession. I wasn’t chasing the cert to prove I could use kubectl. I already lived in that terminal. I wanted it because I was starting to apply for Senior Platform Engineer and Lead DevOps roles, and everywhere I looked, CKA sat at the top of the "must have" list.
So I assumed the logic was simple: pass the exam, prove the skill, get taken seriously for senior roles. It’s the same logic almost every cert-prep blog sells you. Nobody tells you the exam and the interview are measuring two completely different things.
The interview:
I got past the resume screen faster than usual — recruiters like a CKA badge, it’s an easy checkbox. The technical round started fine too. Cluster architecture, RBAC, a live debugging exercise where I fixed a broken deployment in about the time the CKA exam trains you to move in. I was comfortable. I was fast. I thought I had it.
Then the interviewer leaned back and asked something that had nothing to do with any of that:
“Walk me through how you’d design autoscaling for a workload where traffic bursts unpredictably, but your team has been burned before by scaling on the wrong signal. What do you actually watch, and why?”
There’s no kubectl command for that question. There's no YAML to write. It wanted judgment — what happens when the "obvious" metric lies to you, what trade-offs you accept, what you'd have done differently after getting burned once already. I gave a reasonable answer. It just wasn't a lived answer. And the interviewer could tell the difference.
That was the moment the exam and the job quietly split apart in front of me.
Naming the Gap:
CKA is a performance-based exam, and a genuinely well-designed one — it tests whether you can operate a cluster under time pressure: fix RBAC, troubleshoot networking, recover a broken node, all within a ticking clock. That’s a real skill and it’s not trivial to build.
But a senior or platform engineering interview isn’t testing whether you can fix a cluster someone else broke on purpose for an exam. It’s testing:
- Whether you can design a system before it exists, not just repair one that does
- Whether you can reason about trade-offs when there’s no single correct answer
- Whether you’ve actually been burned by something in production, and what you changed afterward
- Whether you can tell that story clearly to someone who wasn’t there
CKA proves you can operate the system in front of you. Senior interviews want to know if you can be trusted with a system that doesn’t exist yet.
Nobody puts that sentence in the exam syllabus. You only learn it by watching a good CKA score fail to close the gap.
What would have actually gotten me the offer:
Looking back, the material that would have landed that question wasn’t anything I’d studied for CKA. It was sitting in my own incident history, mostly untold.
Get Sabir Khan’s stories in your inbox
Join Medium for free to get updates from this writer.
I run KEDA-based autoscaling against roughly 500+ production SQS queues processing tens of millions of messages a day. Queue depth looks like the obvious scaling signal — until it isn’t. There are failure modes where queue depth spikes for reasons that have nothing to do with needing more workers, and scaling on it blindly makes things worse, not better. That’s a real answer to “what do you actually watch, and why” — but it only exists because I’d been through it, not because I’d read about it.
Same with a Fluent Bit PII-redaction filter I once had to rebuild after it quietly ballooned memory from 130MB to 900MB RSS and pushed CPU to 97% under load — a production incident that taught me more about resource limits, buffering, and observability than any certification module could.
Or a Jenkins pipeline that was failing silently for weeks before anyone noticed, which is its own lesson in why “the build is green” is not the same as “the system is healthy.”
None of that is on a CKA syllabus. All of it is exactly what senior interviews are fishing for, because it proves judgment under real conditions — not simulated ones.
So is CKA still worth it?
Yes — just not for the reason I originally thought. It’s a solid foundation, a real forcing function to learn the fundamentals properly, and it’s still one of the fastest ways to get your resume past an automated filter or a recruiter who’s scanning for keywords. It got me the interview. That’s not nothing.
What it doesn’t do is replace the work of being able to narrate your production experience under interview pressure. Those are two separate skills, prepared for in two separate ways, and treating the cert as the finish line is the mistake — not the cert itself.
If you’re prepping for platform or senior roles:
Get certified. It’s still worth it. If you’re considering the CKA as your starting point, the certification gives you a structured way to build and validate your Kubernetes fundamentals.
But don’t stop there.
Alongside the exam prep, build a small backlog of real incident stories from your own work — the outages, the silent failures, the times a metric lied to you — and practice telling them out loud, structured, in under two minutes each.
That’s the material senior interviews are actually testing for.
Want to get the CKA badge?
If you’re preparing for the Certified Kubernetes Administrator exam, you can use my code:
KUBESAB30 — 30% off
It applies to Kubernetes certifications, e-learning courses, and bundles.
Affiliate disclosure: I may earn a commission from purchases made through my link/code. There is no additional cost to you.
