The interview process was structured with multiple rounds.

It started with an initial recruiter call, followed by a technical assessment that focused on Kubernetes, infrastructure reliability, and incident handling.

The real challenge came in the deep-dive technical interview, where I was asked detailed questions about the Kubernetes control plane.

As someone who primarily uses Kubernetes rather than managing its internals, I struggled with questions about how components like etcd, the API server, and controllers work under the hood.

The behavioral round was fine, but I didn’t make it past the technical stage.

The experience showed me that I need to deepen my understanding beyond just using Kubernetes.

How does the Kubernetes API server handle incoming requests? How does it ensure consistency in a distributed system?