i can still argue each of your role titles: > Distributed Systems Engineer Not every distributed system is a kubernetes cluster > Cluster Administrator Ther

i can still argue each of your role titles: > Distributed Systems Engineer Not every distributed system is a kubernetes cluster > Cluster Administrator There are many services which should always run outside of kubernetes, loadbalancers are the easiest counter example. The IAM Role is called like that because its closely scoped to all things cluster in amazon. > Container Platform Engineer entails that you only work on the container platform, while a cluster admin for instance can setup everything on VMs or bare metal > Deployment Automation Engineer This sounds like you are only taking care of deployments, monitoring and logging come to mind as counter examples > Or should I just call developers "IT" I tend to call myself Freelance Sr. Engineer with Kubernetes / GitOps / DevOps / Golang Focus in order to bring german exactness to a widely defined field. So depending on my hat, I become what's necessary in that scope. But yeah, to most managers, I am simply someone from IT Companies have a goal in mind when they go out an hire staff for their objectives. Overall I still think that DevOps is neither b*s* nor insufficiently defined to yield a job title. Titles are vague on purpose, because especially in the realm of DevOps your scopes will get extended to more things than just terraforming.