Which Certification Will I Take Next?
Choosing the next technical certification is a bet on the skills you want to own. After weighing cloud-native growth against breadth and depth, my path is becoming clear — and it’s a lot closer to the metal.
The certification game has changed. It’s no longer about collecting badges for your résumé — it’s about proving you can build and ship in a specific, critical layer of the stack. And right now, inside Sapior, we’re living in that layer every day.
The certification conundrum
The market is flooded. AWS, Google Cloud, Terraform, CKA, CKAD, CKS — the list grows quarterly. The easy answer would be to follow the hype or the one that lands the highest survey salary. But that’s not how I think about it.
The decision always comes back to two questions:
**What am I actually building?**
**Where is the ecosystem friction I need to master?**
For a developer-tools company like Sapior, the answer is undeniably cloud-native infrastructure — and Kubernetes sits at the core of our internal platform engineering work.
Why CKAD now?
I’m not after just any Kubernetes cert. The **Certified Kubernetes Application Developer (CKAD)** stands out because it’s hands-on, performance-based, and explicitly designed for **building applications on Kubernetes**. That’s a sharp contrast to exams that test recall of service descriptions. If I can pass the CKAD, I’m validating that I can define, debug, and deploy production-grade workloads in real time — exactly what we do when we design developer experiences on top of Kubernetes.
According to the CNCF Annual Survey 2023, 66% of organizations using Kubernetes are doing so in production. That number keeps climbing, and the tooling around it is maturing faster than the talent pool. The gap isn't knowledge — it’s applied practice. CKAD fills that gap directly.
What about AWS Solutions Architect?
For a moment, I considered the **AWS Solutions Architect – Associate**. It’s broad, well-recognized, and touches the overwhelming majority of cloud infrastructure. But breadth isn’t what we’re missing at Sapior. We have strong cloud architects. What we need — and what I want personally — is deeper specialization in the runtime that our customers’ workloads depend on. Kubernetes isn’t going away; it’s becoming an operating model. I’d rather be dangerously competent in one paradigm than passably familiar with many.
Making the decision real
I’ve scheduled the exam window. Not because I feel ready — but because a date forces deliberate practice. I’m pairing the CKAD curriculum with two specific habits:
1. **Replaying internal incidents** — every production issue that touched Pod scheduling, RBAC, or network policies becomes a live-fire scenario in my lab cluster.
2. **Contributing to Sapior’s developer docs** — writing quick-start guides for our customers forces me to understand Kubernetes primitives at a level that multiple-choice questions never will.
The Sapior Angle
At Sapior, we ship tools that make ephemeral environments feel as simple as `git push`. That abstraction layer depends entirely on Kubernetes controllers, CRDs, and precise resource management. My CKAD path isn’t a personal hobby — it’s a multiplier for the engineering decisions I’ll make next quarter.
Sometimes the best certification isn’t the one that opens the most doors. It’s the one that opens the door you’re already knocking on.
-//The certification diary continues. Next update: after the first practice exam.//-