3 ms·

> "Person who sets up the Kubernetes cluster with terraform, ansible and yaml" Distributed Systems Engineer Cluster Administrator (the actual IAM Role, incide

by dijit 3y ago

> "Person who sets up the Kubernetes cluster with terraform, ansible and yaml" Distributed Systems Engineer Cluster Administrator (the actual IAM Role, incidentally; weirdly not called "DevOps") Container Platform Engineer Deployment Automation Engineer Or should I just call developers "IT"? ;)

pid-1 3y ago
Let me join the exercise: > Distributed Systems Engineer Probably best reserved to people that implement distributed systems. One can deploy and manage a K8s cluster with 0 distributed systems knowledge. > Cluster Administrator That's a good one. But many DevOps do more than managing clusters: I create and manage templates for our CI/CD pipelines, project templates and internal libs that abstract best practices, manage networks, databases, data lakes, identity providers... And develop internal applications to automate ops of all those resources. > Container Platform Engineer Same issues as the titles above. > Deployment Automation Engineer That's a good one, I like that. In the end of the day, everything a "DevOps" do is done to deploy things faster and more consistently to prod, as well as keeping deployments running correctly. I think we can even drop the Automation and use "Deployment Engineer"
jhoelzel 3y ago
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.

by dijit 3y ago

pid-1 3y ago

Let me join the exercise: > Distributed Systems Engineer Probably best reserved to people that implement distributed systems. One can deploy and manage a K8s cluster with 0 distributed systems knowledge. > Cluster Administrator That's a good one. But many DevOps do more than managing clusters: I create and manage templates for our CI/CD pipelines, project templates and internal libs that abstract best practices, manage networks, databases, data lakes, identity providers... And develop internal applications to automate ops of all those resources. > Container Platform Engineer Same issues as the titles above. > Deployment Automation Engineer That's a good one, I like that. In the end of the day, everything a "DevOps" do is done to deploy things faster and more consistently to prod, as well as keeping deployments running correctly. I think we can even drop the Automation and use "Deployment Engineer"

jhoelzel 3y ago

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.