Pete Cheslock

DevOps, RelEng, DevTools, Automation, Randomness

DevOps in Your Job Title Is Doing You Harm

I used to be Director DevOps…Twice. Both times I changed my title later. I even ran a DevOps team - although the team was already called that when I took over.

I have fallen victim to the the abuse of the DevOps title. And I see it all the time; in the devops twitter hashtag, people contacting about DevOps job opportunities. It’s got to be a real thing, right? I mean, we totally have people that are doing DevOps these days, right?

I recently lead an Open Space session on this very topic at DevOpsDays Austin. We talked for about 40 minutes, with about 35 people in attendance and I wasn’t able to find anyone with an dissenting option. Now that doesn’t mean that I’m right, or even that everyone in attendance is right. But there is one very important reason why you might want to think twice before using “DevOps” as part of your job title.

When I ran that session, I started the session with a recent story. My friends (rightfully) give me shit for the fact that I self assigned my title at Dyn to be the Dir. of DevOps (I still feel bad about it). I really hate job titles in general and this is what happens when you don’t give a shit about what your title is. How the story goes is that when I received the offer from Dyn, my original title was “Director of System Automation and Release Engineering”. Since I’m pretty sure that doesn’t fit on a business card, I took the job and asked that we change the title later. Fast forward a month, and I’ve been working at Dyn for about 2 weeks at that point. After talking and trying to formulate my job description & title for about 20 min, I say simply enough…“Fuck This, just call it DevOps, I’ve got other things to do”. I was far too busy to really care much about an arbitrary title.

Fast forward a few weeks to Monitorama, and I was chatting with Mike Rembetsy. After talking for 2 minutes about how the new job was going he says, “Oh, that reminds me, you need to change your job title, it’s fucking terrible”. I tried to convince him for about 3 more minutes, mainly trying to express to him that it doesn’t matter. He then dropped the knowledge bomb that gave me the Ah-Ha moment.

When you are the Head of DevOps, you “Own” DevOps. If DevOps fails it is your failure, when it should be a failure of the entire company to change, adapt, and accept the cultural shift.

That is the major problem with being the “head” of DevOps, or the “Director/Manager/VP/Etc of DevOps”. If DevOps fails inside your Company, it’s a really easy way for the executives/etc to say “Well, you are the head of DevOps so obviously it failed because you failed.” The reality is that DevOps is a culture that should be accepted by every facet of your organization. Everyone needs to embrace the changes of a DevOps culture, and there can not be a single owner of it.

Soon after that conversation, I relaunched my team and title in general to be the “DevTools Team” (A brilliant Etsy recommendation). The more I thought about it, it accurately describes the work that we do. We build the tools needed for Developers(and Ops/QA/NetSec) to spend more of their time writing code, and less time dealing with distractions.

I know some people want to have a DevOps team, or want to call their team the DevOps team. Jez Humble wrote a wonderful blog post last year that I highly recommend that you read. In his post he summarizes that there are scenarios that a “DevOps” team label works, and I do agree with what he says. But don’t just label a team DevOps, assign a new Manager of DevOps and wonder why three or six months go by and things are still shitty. Things are still terrible because all you did was change a team name, or give a brand new team a name. Or in some cases created a new silo, the “DevOps Team Silo”.

Well, what am I supposed to call myself?

Here are some of the examples that came up during the Open Space.

  • Site Reliability Engineer
  • Automation Engineer
  • Release Engineer
  • DevTools Engineer

I don’t know why recently there is a need to move away from the same job titles we’ve used in the past, as if there is some negative connotation towards them. It’s not that the jobs have really changed much, it’s that we’re just getting better and more efficient at doing them with the tools at our disposal. The tools have grown so quickly, it has enabled us to be much better at our jobs, but only if you are willing to learn something new.

  • System Administrator
  • Operations Engineer
  • Network Engineer

In the end - titles really don’t matter very much, and they shouldn’t matter much. But they can actually have a more powerful (negative) impact internally by making you the owner of a culture that should be accepted by everyone. But there is one point that I believe is so important it needs to be repeated:

If DevOps fails, it should be a failure of the entire company.

If you missed DevOpsDays Austin - you can check out my talk “How to Keep the People You Need”, where I discuss recruitment and retention of your hard to fill positions.