8

IMHO it's not a good idea to directly and immediately apply a team's gains from its DevOps transformation into scaling the team down. At best you'll lose just the team's motivation to do any such improvement in the future. But most likely you'll lose most/all the talent in that team. Instead: allow the team to appreciate the benefits of the difficult ...


8

I believe DevOps is orthogonal to your question, i.e., it changes nothing compared to a "classical" approach (or to hiring any team at all, not only for software development). You identify what your key needs are (for example, an "architect" who is able to structure large software systems; some "hacker" who is able to fix a Kernel driver if needed; a "tester"...


3

Yes. Although DevOps is a culture and not a role, one should assess the mindset and technical skills of a candidate. At my previous work we conducted two interviews. The first one was a conversation about the mindset. If my colleague and I were positive then we offered the candidate the possibility to prepare a demo for the second interview. He or she could ...


3

Yes, there absolutely should be an assessment, however it would be a good idea to agree upfront with one of the few DevOps people you know to validate the content and results. Regarding the contents of the assessment, there are some questions still remaining after your edits. Key one is how your operations are done. Possible options are: you already have ...


3

Since DevOps is a hot trend in IT, companies are seeking top-notch DevOps talent. However, before you begin assembling your team, there are a few things you should consider: What kind of DevOps? Imagine a rock band is searching for a new guitarist. There are lots of people who know how to play the guitar, but there are so many music styles that can be ...


1

I'm currently extending my DevOps team, without forgetting skills, for me, the most important thing is the "mindset". Amazingly, not a lot of people around with the right mindset of continuous improvement.


1

DevOps is a "team" of people that includes the development and operations teams. (security/compliance combined). You shouldn't think about the devops "team" as a separate entity but part of the larger organization. Checkout http://web.devopstopologies.com/ for organizational structure. You can see it's about moving together.


Only top voted, non community-wiki answers of a minimum length are eligible