Welcome!

Linux Containers Authors: Zakia Bouachraoui, Elizabeth White, Yeshim Deniz, Liz McMillan, Pat Romanski

Article

Key Takeaways from Continuous Discussions (#c9d9) Episode 70 – Hiring for DevOps

Hiring for DevOps

Read the original blog here.

In a recent Continuous Discussions (#c9d9) video podcast, expert panelists discussed hiring for DevOps.

Our expert panel included: Chris Riley, analyst at Fixate.io; Imari Kontulainen, CEO of Deveo; Marc Priolo, software configuration manager at Urban Science; and, our very own Sam Fell.

During the episode, the panelists discussed whether or not a DevOps engineer exists, the challenges of hiring for DevOps, the skills to look for, and more. Continue reading for their full insights!

Is There a DevOps Engineer?

“DevOps” and “DevOps engineer” are often confounded  together, but are actually mutually exclusive explains Riley: “When people started using the title DevOps engineer, they were essentially renaming SRE’s and release automation in QE and QA, and they neglect to include stewardship of the DevOps principles. ‘DevOps’ and ‘DevOps engineer’ are really two separate things. If you want hire somebody who has DevOps principles, it should really be everybody on your team.”

A DevOps engineer could be a variety of roles, it’s up to the company to define what it truly means, per Kontulainen: “Any person on the operations side of the product could be called a DevOps engineer. For example, a system administrator who does a lot of automating is a good example of a DevOps engineer. But, ultimately, it’s up to the company to actually describe what the position means.”

Priolo says that it depends on how your own organization defines DevOps, but, it really is more about culture than a title: “DevOps is more of a culture. I wouldn’t want to use that label as the role because DevOps is meant for multiple teams to work together and not one person to wear the whole teams’ hats.”

There’s no “Agile engineers,” so why does the title “DevOps engineer” exist? Fell digs in: “To say you want an ‘Agile engineer’ or a ‘DevOps engineer’ is sort of saying that you want an engineer who understands DevOps, or an engineer who understands Agile. But I don’t think anyone ever came up with the idea of having the job titled ‘Agile engineer,’ but here we are with a DevOps engineer title running rampant all over LinkedIn, and getting the inbounds from people.”

Why Hiring for DevOps is Difficult?

Organizations are struggling with finding where a DevOps function fits on their teams, so it’s really about having full-stack developers rather than a DevOps engineer, says Riley: “One of the words we haven’t said yet is full-stack. Every developer out there right now has the goal of putting full-stack in front of developer. When they say full-stack, it means they can be autonomous when it comes to building dev environments and not relying on people to hold their hands.”

Full-stack developers are good to have, but be careful once the organization starts to become larger as having domain expertise might be more efficient there, per Kontulainen: “Having a full-stack developer works up to a certain level, but once the organization scales, it’s more important to specialize in continuous integration, test automation, etc. Of course, you don’t need to master all of them or be able to do more of the tiered release to production, but it’s good to have the basic knowledge. Other than that, I fully agree that more developers should be aware of the pipeline as a whole – from idea to production.”

Perhaps, the root of the problem is that people in college are not being taught DevOps and don’t have those collaborative skills when they graduate, says Priolo: “Developers don’t go through college learning the idea of, ‘We want to have this DevOps culture. We want to work in a collaborative environment.’ They go throughout their education saying, ‘I want to be a developer. I’m only going to do this. I want to be a CIS Admin, I’m only going to learn this.’ And then, when they graduate, we say, ‘Hey, we understand you learned this silo, but we’re not looking for siloed approaches. We’re looking for holistic approaches. We’re working at collaboration, seeing the big picture.’ That’s really the challenge is new recruits are not applying for those type of jobs because it’s totally not a match for what they went through their education for.”

Fell breaks down the difference between a full-stack and DevOps engineer: “A full-stack engineer is more developer-focused, but they can understand the ramifications into production. A DevOps engineer would be somebody who’s more focused on the pipeline. They’re not necessarily building features in the product, they’re really building the pipeline as a product.”

What to Look for in a DevOps Skill Set?

Being fearless and quick to learn are key attributes for hiring, says Riley: “It’s more about not having fear. They need to respect the entire delivery process, but not be afraid to learn something new because everything is changing very quickly. I grew up as a .Net developer. Now I’m doing stuff with Python and release automation. So the approach is really being persona-focused, but also making sure that we’re motivating and cultivating the right people.”

Make sure that the person you are hiring aligns with the company culture and values, advises Kontulainen: “What I look on every hiring decision, whether that’s a DevOps role or not, is if the candidate has the values that our company encompasses. For example, we have simplicity, openness, proactiveness, curiosity, and customer focus as our main values. If the candidate agrees on those values, there’s already a fit.”

Priolo makes sure that when he hires someone new that they have a big picture mindset: “The ability for the person to see the larger picture critical. This comes back to the whole silo concept of people who only concentrate on their deliverable and that’s it. What is more critical is the larger picture. How does that deliverable affect at least two layers above you? It’s not about your deliverable, it’s about the customer experience and giving the feedback so that you can continue the loop. When I’m recruiting, I want to see if the prospect has that type of perspective.”

If you are hiring someone for an Agile or DevOps position, they need to have those types of characteristics, not just learned skills, says Fell: “I love the idea of having a doctrine or list of characteristics to look for. I love the idea of making sure that the person is an agile learner. They have to be able to be agile in the way that they progress their skills. They can’t just say, ‘Well, it’s waterfall, and if I need to learn Chef, I’ll see you in 18 months, and then I’ll know everything about Chef.’”

How to Hire, Build and Retain a Winning DevOps Team?

Riley discusses successful use cases of bringing internal people from QA/QE into DevOps roles: “I’ll be very specific when I say quality engineering, because this can’t be typical QA. These are people that are technical and understand scripting and automation, and they have a really strong holistic point of view on the delivery chain. The problem is they don’t tend to be the people that champion themselves. You can find these people who maybe want to take a different direction in their career, but are just too afraid to do it, and morph them into this role and be very successful.”

Autonomy, mastery and purpose are key to retaining your DevOps talent, advises Kontulainen: “DevOps already is all about the autonomy, giving developers the autonomy to do stuff without interfering with what operations is doing. Then, on the mastery level, you need to train people so that they could leave, but treat them well so they won’t. Finally, in regards to purpose, you need to have very clear goals so that everybody understands them. Make sure they are specific, measurable, attainable, realistic, and timely goals to make it clear for everyone where we are going.”

Priolo says, “Whenever the term DevOps comes in, it’s there to empower. As the leader of the team, you must personify that. You must make sure that it’s very clear that that’s the goal of the team. Everything you do follows that principle. The more wins the company has as a whole, the more value that’s seen in the team.”

A blameless DevOps culture helps those who might be shy or scared to step up into a new role finally make that move, explains Fell: “In a team of equals where everybody is contributing to a common goal, and everyone clearly understands that goal, is a fantastic opportunity for those types of people to be able to blossom into something that they could not have done in a culture of finger-pointing.”

Watch the full episode.


Read the original blog here.

More Stories By Anders Wallgren

Anders Wallgren is Chief Technology Officer of Electric Cloud. Anders brings with him over 25 years of in-depth experience designing and building commercial software. Prior to joining Electric Cloud, Anders held executive positions at Aceva, Archistra, and Impresse. Anders also held management positions at Macromedia (MACR), Common Ground Software and Verity (VRTY), where he played critical technical leadership roles in delivering award winning technologies such as Macromedia’s Director 7 and various Shockwave products.

IoT & Smart Cities Stories
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...