Some advice I would give to a junior DevOps Engineer

<p><pre><code> DevOps is not a role, but a culture inside an organization </code></pre> I think we need to give up on fighting this fight. The thousands upon thousands of job postings with that job title clearly indicate otherwise.<p>Better to accept that the philosophical battle has been lost and that DevOps Engineer is the new name for other titles like &quot;System Administrator&quot;, &quot;Infrastructure Engineer&quot;, &quot;Operations Engineer&quot;, or &quot;Site Reliability Engineer&quot;.<p>e.g. &quot;The person responsible for dealing with making sure there is a way for the software to run somewhere and that it stays running.&quot;

I don&#x27;t agree with this generalization for good communication &quot;In my experience more extroverted and “chaty” engineers have it better on average.&quot;<p>Often times we conflate loud communication with good communication. In my personal experience there are lots of verbose individuals that are poor communicators.

None of those skills listed are any more &quot;DevOps&quot; than they are systems administrator, systems programmer, embedded programmer etc.

I disagree that there is no place for a junior role. I can spec out tons of projects a reasonably junior person could handle that would take away a lot of &quot;busy&quot; work for me. The problem is this - very few people actively choose DevOps. I&#x27;ve heard it said that DevOps (I started calling it just &quot;ops&quot; because many devops jobs have very little dev) isn&#x27;t something someone chooses, it&#x27;s something that just happens to you. For me, one minute I&#x27;m volunteering to help out with the builds at a small startup, blink and then 5 years later I&#x27;m a DevOps engineer.<p>I would give juniors this advice:<p>Do not pigeonhole yourself into a particular role. The best &quot;DevOps&quot; I&#x27;ve seen are generalists that can fit in on SRE, Systems&#x2F;platform engineering, network, security types of teams, etc. Same goes with technology. If you find yourself early on spending 2 years working on nothing but Jenkins and CI&#x2F;CD pipelines, guess what your next job is gonna be about. Challenge yourself, always be learning a new thing. If you don&#x27;t like learning, or can&#x27;t learn fast, this isn&#x27;t the job for you. If you don&#x27;t like potentially brutal on-call schedules, this isn&#x27;t the job for you. If you don&#x27;t like mostly thankless work that is invisible if you are doing it correctly, this isn&#x27;t the job for you. Also look at job postings frequently and see what companies are asking for proficiency in and make sure you at least are somewhat competent in those areas.<p>Also I wish more DevOps had more of a CS background. I can&#x27;t tell you how many times I&#x27;ve seen multiple senior DevOps looking at a machine that is clearly and very obviously thrashing and have no idea what they&#x27;re looking at.

One additional one I would add is: don&#x27;t be an ass. I have seen a fair share of people in this role belittle QA, Devs, and interns because they&#x27;re not able to follow along or understand how to use DevOps tooling.<p>I like to think of the role as hospitality; you don&#x27;t particularly have to like the guest but try to create a good working atmosphere.<p>A specific example: if a particular dev runs to you every time a build fails and tries to blame the environment: force them to check their own work first. If there&#x27;s another branch that builds, ask if it&#x27;s related to one of the changes in this branch. Ask if the code builds locally. Ask them what they&#x27;ve tried so far to debug the issue. These questions will help out anyone who does not know how to actually troubleshoot build failures and discourage anyone who is simply trying to pawn off their work.

The last one, Focus, is very import. At school, I had time to think and work on two or three different stuff. When I was a junior &#x27;developper&#x27; (basically I was developing filters to clean data to feed it to an OCR), I continued doing 2-3 different part at the same time. And then I kept doing it as a devops. This was a mistake. As a devops, you really have to be focused on your subject, you can&#x27;t afford to half-ass your projects, and the scope is so large you will always forget important details if you continuously jump from project to project. Keep focus, takes notes (temporary or in comments). And communicate. The rest is easy

DRY. Don&#x27;t contribute to shrapnel infrastructure architecture -- consolidate configuration. Build effective abstractions as an organization. Use terraform only where you have to and use better abstractions everywhere else.

Ah, but it is so difficult to stay focus with all kinds of shit blown up and getting pinged in 10 channels. This is one skill that the military people are super good at.

after &quot;DevOps is not a role, but a culture inside an organization&quot; and &quot;If we’re going to use it as a role, it’s not an entry level role&quot;<p>I left.

Could we get rid of this &quot;junior&#x2F;senior&quot; crap? I have never worked anywhere it was ever useful. You are a programmer - that&#x27;s it. The only people that think otherwise are self-agrandising so-called &quot;seniors&quot;.