Corporate HR Beware: Recruiting for DevOps Enterprise?

October 30, 2015

Recruiting-for-DevOps-Enterprise-Intland-Software-336x336 Corporate HR Beware: Recruiting for DevOps Enterprise? DevOps DevOps is taking the world by storm, disrupting the traditional Enterprise structure, where development, Quality Control and IT operations co-exist in isolated silos.  The DevOps concept breaks down the barriers between these departments.  Such disruption comes with big changes, visible throughout the enterprise; externally, the most visible change of all is in the new job roles created by the Human Resources Department.  The Devops Engineer (replacing the Systems Engineer title) seems to be by far the most prolific, but other roles such as DevOps Architect are also being advertised.  A quick search for jobs (at the time of writing) on indeed.com displayed 9800 open DevOps jobs.  The problem of course is that DevOps Engineers are System engineers, they don’t necessarily think about themselves as DevOps engineers.

The DevOps term has only recently become mainstream (growing since 2013) however the practice of integrating Development and operations teams has been going on for decades by the truly innovative.

HR are Including the DevOps term in senior job titles such as Manager of DevOps (DevOps Manager), but this is risky business for those that do, potentially missing many of those qualified individuals,  and riskier still for those professionals that do rebrand themselves as DevOps Managers since the failure of establishing a DevOps Enterprise will be assigned to the titleholder.  DevOps is Agile, just extended Agile for operations, and just like adopting Agile, DevOps requires a work cultural change across the entire enterprise, a task which lies outside the job description of the DevOps Manager.  It is rather a responsibility and within the skillset of a Change Management professional to facilitate work culture change.

DevOps jobs are posted by companies and HR personnel that want to adopt DevOps but don’t really understand it and therefore, anyone applying for such positions should be wary of what they are walking into.  There is no difference between a Systems Engineer and a DevOps Engineer in terms of their qualifications.  It is rather the individuals experience with the range of tools typically used for testing automation, continuous build and continuous deployment along with the experience of integrating them for what is now called a devops environment, that sets them apart – or not.

Suffice to say, demand for DevOps Engineers is far outstripping supply, with google trends data showing the huge demand escalating year on year (since 2013).  Google trends data also shows that the term DevOps became mainstream in 2013.

The typical role of DevOps Engineer (lifted from various DevOps jobs postings)

  • Applying and Supporting Automation – Continuous Integration + Continuous deployment (tools + integration of tools, ie Jenkins)
  • Strong background in SaaS solutions (Tools that are good for DevOps)
  • Build and maintain technical infrastructure
  • Recommend infrastructure architecture for Engineering tools and systems
  • Work collaboratively with IT, Engineering and Quality Insurance personnel (not forgetting project managers)
  • Cultivate and communicate best practices
  • Secure deployment practices
  • Stay up-to-date with new automation technologies and techniques with the goal of improvement.

DevOps Enterprise Guide: Understand DevOps

Most of the DevOps positions make no mention of the most basic knowledge requirement of all for implementing DevOps and that is knowledge of Agile Methodology and Development and preferably, knowledge of implementing the Scaled Agile Framework (SAFe Certified), – the most widely used framework for scaling Agile for Enterprise use.  By recruiting or consulting with SAFe certified individuals you are working with someone that is trained for DevOps implementation. This would include extensive knowledge of the Application Lifecycle Management tools (ALM Software), and specifically those that are designed for use with the Scaled Agile Framework (such as codeBeamer ALM). This is necessary for integrating with existing tools sets as well as being suitable for Scaling Agile for Enterprise use.  For DevOps, It is essential that the tool adopted must also being suitable for extending Agile for use by operations and equipped with an integrated Service Desk (such as our very own codeBeamer ALM).  

Before recruiting for DevOps, take the time to understand what is DevOps and why Intland Software’s codeBeamer ALM provides a complete end to end solution for the DevOps Enterprise.

facebook Corporate HR Beware: Recruiting for DevOps Enterprise? DevOps twitter Corporate HR Beware: Recruiting for DevOps Enterprise? DevOps google Corporate HR Beware: Recruiting for DevOps Enterprise? DevOps linkedin Corporate HR Beware: Recruiting for DevOps Enterprise? DevOps

Tags:

Related E-Book

DevOps Enterprise Guide

First Name

Last Name

Email Address

Company

Phone Number

Industry

Eva Johnson

Written by

Eva is an Economist (MSc) and also holds an MBA in Marketing Communications. She has over 10 years of experience in journalism, digital media communication and project management working with several multinational companies and governmental institutions. You will find her blogs posts on a variety of subjects from Agile-Waterfall Hybrid, Scrum to DevOps.

Eva Johnson has written 131 posts for Intland Software.

No comments

Leave a Reply

Your email address will not be published. Required fields are marked *