| | SEPTEMBER 20169CIOReviewPart of innovation is lively debate and convincing others (up, down and sideways in the reporting structure) to support your idea or approach. Look for someone that is open to different opinions, conveys their ideas succinctly and can professionally hold to their convictions. DevOps is about effective communication and collaboration first. Given the rise in remote workers, the majority of technical communication is written (email and chat) Give the candidate a problem set and ask them to write out one email to their manager and another for their colleagues, posing a solution. A sense of humorDevOps is, at its core, about bringing groups of people together. Sometimes you are bringing these groups goals into closer alignment. With so many different personalities, conflicting priorities and deadlines, things can get tense. Having a smart and graceful sense of humor can defuse conflicts rather than escalate them. Care must be taken to look for subtle sarcasm, negativity and passive-aggressive humor This type of humor can increase stress and frustration. During the interview process, take the person outside the office for lunch or coffee. Look to see if they can take differing opinions in stride with good humor or if they display a high degree of ontological arrogance. You can also take this opportunity to observe how they interact with different people in a potentially uncomfortable situation. Culture, Aptitude and Skill In order to compare many candidates (often 10-20 at a time) it helps to boil down the previous characteristics into three categories, and give the applicant a score. They are listed in the order of importance; Culture, Aptitude and Skill. Cultural fit is paramount. I have discovered, to my own peril, just how important it is that the person fit the culture of your teams. I once hired a brilliant network engineer that, at the time of hire, I knew would not fit into the team. I was filling "my" need as a manager, but not filling the "teams" need. It is difficult, if not impossible, to change a person's core personality. For this reason, cultural fit gets the veto power for DevOps hiring. Aptitude is not always easy to judge but if you put some reasonable tests in front of the candidate you can discern their aptitude. Low levels of aptitude do not necessarily mean you don't hire but you must understand the runway for value add for that person is much longer. Consider the position need and timing and decide accordingly. Someone with a high level of aptitude can make up for a lack of skills up front and still quickly add value. Skills are the lowest ranking for DevOps. This doesn't mean you should hire someone for a senior engineer position with no relevant skills. It does mean that skills can be easily taught and adopted by an individual with high aptitude. Even though this is the lowest level of requirement, it is the one that gets the most attention when developing the position description and job posting. Given that fact I will expand on this to list the skills that I look for in the resume. Don't get too hung up on a specific tool; remember that if they fit culturally and have aptitude you want someone that can quickly learn new tools and approaches!Look for core skills in the following key areas: Automation: Automating the Value Stream is an important part of deriving value from DevOps. Look for skills in automating system configuration, testing, code builds. Measurement: Understanding current state is critical to planning where you wish to go. Look for skills in tools and process that identify key metrics, recording and measuring those metrics and reporting on those metrics publically. Coding/Scripting: The level and depth of experience in this field will vary, however understanding code supports all the other technical functions of DevOps.If you are new to this approach, I recommend researching CAMS, an acronym describing the core values of DevOps. It was coined by Damon Edwards and John Willis at DevOps Days Mountain View 2010.C ­ Culture; A ­ Automation; M ­ Measurement; S ­ Sharing Micromanaging has no place in the workforce and this is especially true in DevOps. This does not, however, mean that you work alonePauly ComtoisIt's DevOps! It's DevOps! It's DevOps!
< Page 8 | Page 10 >