Skip to content

Instantly share code, notes, and snippets.

@habutre
Last active February 14, 2016 23:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save habutre/d7f180e6ce16ac57ac26 to your computer and use it in GitHub Desktop.
Save habutre/d7f180e6ce16ac57ac26 to your computer and use it in GitHub Desktop.
Devops recruiting done wrong

#Devops became another buzzword

How many guys including me have named (him|her)self as a DevOps Engineer or DevOps Manager or DevOps Guru?

Given the scope of Dev+Ops is almost impossible - outside of paper - to someone to say "I'm a DevOps professional!"

Its important to know and believe which DevOps is a culture, a mindset, a number of concepts, best-practices and actions. You can be a wizard or ninja (both names are being used as a title to exceptional professionals, almost gods in some area) in infrastructure field, or in a certain technology, but alone, without other brilliant ninjas or wizards probably you'll failure or at mininal take a wrong path.

The collaboration and the sum of skills will give you a perfect environment to create all you wish or you dream. So please, when you recruit talents to your company, startup or a project try to invite ninjas/wizards specialists to become part of your team, certailly your entire dream will become true sharing the skills of your team of wizards.

The:

Infrastructure professional != DevOps Infrastructure

Software Developer != DevOps engineer 

Release Manager != DevOps engineer

Except if:

They work with DevOps culture in mind!

So:

Create your team and give it the DevOps culture, not names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment