As @kylegalbraith
mentioned, try to avoid the trap of thinking about DevOps in terms of a specific tool or piece of software.
While it is true there are several tools or systems one would expect a DevOps practitioner to have experience with, it shouldn't wholly define the methodology.
"The DevOps Handbook" is a good place to start, as well as the precursor "The Phoenix Project".
If you want to take a rigorous, academic dive into the ideas behind some of the architecture, I recommend: Distributed Systems
I'll give you a short list of what I'd look for in a Senior DevOps candidate right now(this is list is by no means exhaustive):
Experience in large-scale, distributed ops environments
Comfortable with at least one interpreted scripting language
Experience designing/deploying fault-tolerant HA systems.]
Extremely comfortable with interacting with other teams and groups, including non-technical stakeholders and senior leadership
Experience deploying in at least one cloud provider
Note one item is in bold, and it's not technical.
It is absolutely imperative that as a DevOps engineer you are comfortable being involved early and often in discussions around system and software design. Knowing your customers, their pain points, and their requirements, are key to being successful. Also being able to advocate for good ops practices, particularly to non-technical stakeholders, as well as senior leadership, is equally important.
"try to avoid the trap of thinking about DevOps in terms of a specific tool or piece of software." Really wish this was the mindset of the general populace. Sadly it seems an automated two step build process is called a 'devops pipeline'. Uggg.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As @kylegalbraith mentioned, try to avoid the trap of thinking about DevOps in terms of a specific tool or piece of software.
While it is true there are several tools or systems one would expect a DevOps practitioner to have experience with, it shouldn't wholly define the methodology.
"The DevOps Handbook" is a good place to start, as well as the precursor "The Phoenix Project".
If you want to take a rigorous, academic dive into the ideas behind some of the architecture, I recommend: Distributed Systems
I'll give you a short list of what I'd look for in a Senior DevOps candidate right now(this is list is by no means exhaustive):
Note one item is in bold, and it's not technical.
It is absolutely imperative that as a DevOps engineer you are comfortable being involved early and often in discussions around system and software design. Knowing your customers, their pain points, and their requirements, are key to being successful. Also being able to advocate for good ops practices, particularly to non-technical stakeholders, as well as senior leadership, is equally important.
Will follow your words. I'd like to be in touch, as I'm at the start of my career. If you're willing, send an email to this ID
Email sent :).
"try to avoid the trap of thinking about DevOps in terms of a specific tool or piece of software." Really wish this was the mindset of the general populace. Sadly it seems an automated two step build process is called a 'devops pipeline'. Uggg.