In my blog I usually talk on technology on a “management” level. My aim was trying to explain technical concepts without the “technical” part. Why should any company invest money in something, unless they understand fully what are the benefits of it? Today I am going to drift away from this tendency, and offer a helping hand to recruiters. What makes a good DevOps? How to find out if someone fits in this role? Let’s talk about those things.
First, if you didn’t read this entry, I would recommend you to do so. It’s a brief introduction to what DevOps as a role is. I talk about silos, about communication, and how there is no specific “role description” for a DevOps unless you understand the business culture that the position will fit into. It is important to understand this bit: “DevOps”, as such is currently understood, is a verb, not a noun. Someone “does” DevOps.
Most often DevOps positions are related to deployment pipelines, release management, architecture and provisioning. Creating packages and deploying releases are one of the widely accepted responsibilities of such an occupation. This is because the process of creating and publishing a release is the main intersection between the Development and Operations departments. Thus, DevOps eases the joint effort to move forward new code.
Environment handling is also a burden on a DevOps shoulders. Keeping the machine settings for both the developers and testers collaborating on a release is critical for any mission. Again, the DevOps role works toward helping two units work together.
Going back to the post, let’s focus again on the image that accompanies the text. Specifically, take into account that shows the three different departments we mentioned so far, and brings them together: Development, Quality and Operations. Thus, now we can answer the first question.
What makes a good DevOps? Experience with these three branches of software development. Skills related to this process. I am even going to boldly state that you only need a good grasp on any two of these requirements. A developer with an infrastructure background could work. A QA tester with knowledge of automation and scripting can do. An operations agent that writes his/her own scripts that provision and deploy code from source control can be a perfect fit.
Now, on the second question: How to find out if someone fits in this role? The answer is the final ingredient in the mix of skills that I just brushed over. A DevOps is a team player. Find a collaborator, an enthusiast. Someone passionate, driven to reach his objectives. In my opinion, that is the perfect fit for a DevOps.
Also published on Medium.