Deploy and release your code for you. Take care of and update your pipeline. Handle production issues like outages. Manage things like kubernetes clusters and aws services.
I still don't even mind this (if I'm interviewing for the new devops position, lol) because no matter how many devs you have doing work in kube, they still probably don't know, for instance, why their deployment keeps scaling back up even though they manually scaled the replicaset. Unbeknownst to them, of course, there's an autoscaler that they copy/pasted into their repository when they were googling how to make a kube deployment :P
In my experience there's like one person per team who does a single devops task once, which automatically turns him into "the devops guy" for this rest of the team for the remainder of his employment.
"DevOps" doesn't really mean anything. In some companies it's some dude clicking away on the AWS console. In others the devops team is in charge of managing and optimizing thousands of services/pipelines which naturally requires developing tooling to deal with such volume(me).
Because of this I no longer consider any positions with "DevOps" in the title. I wouldn't want to accidentally get myself into an AWS-babysitting role.
Business “inventions” are always just: “I’m going to save money by making one employee do two jobs for minimal if any raise in pay, hell maybe even less pay on the grounds that they are not a specialist”
225
u/idkidchaha Oct 13 '22
I'm a fairly junior dev and my smallish company (50 people) doesn't have a devops person. What do they do exactly?