The process took four weeks.

There were two rounds. The first was a quick tech screen with the hiring manager. The second was a panel following the build of a technical lab environment consisting of cloud infra, IaC, DevOps pipelines, using K8s. It was very time-consuming, and the scope was open.

Based on other interviews on Glassdoor, the panel may be inconsistent in focus. Mine was focused on K8s almost exclusively. The second panel interview sets up to be more comprehensive, but for mine specifically, it was mainly a K8s engineering interview. Very few to no questions were focused on what was built, including cloud architecture, DevOps, or security concepts. The panel zoned in on K8s command-line questions and troubleshooting concepts.

I still feel it would be a great place to work, but assume that there are some growing pains in areas like this (the interview) and with leadership projecting their own skills in the interview process, which is not uncommon in tech organizations. The type of questions being asked felt dated and oddly specific in areas.

Remote into your k8s pod and showcase a file, which was part of the exercise.

How do you reactively block a process from running in k8s?