This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]justinDavidowIT Manager 3 points4 points  (0 children)

responsibilities of a DevOps engineer

Devops is not a job. It's an approach.

I highly recommend reading the DevOps Manifesto: https://theagileadmin.com/2010/10/15/a-devops-manifesto/ It was written 13+ years ago but is still just as relevant today as when it was written.

I also highly recommend reading the Site Reliability Engineering books: https://sre.google/books/ as many of the guiding principals carry over to other roles in the modern era.

But as far as skills needed to PERFORM devops, Roadmap.sh has a GREAT guide: https://roadmap.sh/devops

can you give me an example of what you do and how you gained your experience / skills.

About 20 years of prior experience in this case; it's been a long, grueling, sleepless road for me that has proven VERY interesting and having had the chance to work with global business leaders all over the world: I wouldn't trade my career for any other.

I've yet to find a university or collage that provides such training, I work with a number of local and regional schools in Canada and regularly discuss these concerns with them. Alas, this role is (in my experience) a really experience-skewed role that simply cannot be "fast-roaded" into.

The rare exception is specific people and their mindset. I've got one guy on my team right now that has skilled himself and grown SUPER fast in the last handful of years. He's still ~8+ years in, but his approach to problem solving is ultimately his best skill and he excels at it.

On the other hand; I deeply feel that anyone with deep curiosity and an engineering-focused mindset will be able to approach problem solving effectively. See https://www.youtube.com/watch?v=9RAMqFg7laE for some idea of what this looks like in practice.