In the technical interview, I was given Kubernets cluster with some common problems in connectivity/scheduling, etc. The task was to figure out what's wrong. The next couple interviews focused about specific knowledge in releasing software (due to the team). There wasn't a clear format, just "tell me how you release this web app + what's problem do you expect". My guess is that they are trying to see if you have done X in Y ways.
Anonymous
The Kubernetes bits was easy if you work with it long enough. For the release process, I shared about processes that I worked with, e.g: tagged release being triggered manually, deploy-on-commit, blue-green/canary, feature flags, etc. ****** Ultimately, Gitlab picked another candidate that passed the same rounds I that did. They did flag that I don't have enough experience with releasing things. This is somewhat fair, as I don't work exclusively in the area. However, I would expect these are knowledge that you could pick up on the job. Reflecting on this, I would say choosing the right team that would want your skillset is important. I went in thinking that deep expertise in Kubernetes is an advantage, but it seems the team put more weight on something else.
Check out your Company Bowl for anonymous work chats.