Why your cloudops staff is quitting

Posted on 17-05-2019 , by: admin , in , 0 Comments

It’s Monday morning and you have another letter of resignation on your desk. This time from a woman who was doing performance monitoring and cloud-system tuning. Last week it was a database operations administrator, and two more from the cloudops team quit the week before.

What happened? The cloud was supposed to make things easier. Are you underpaying or overworking, or is there something else that is harder to fix?

The fact of the matter is that cloud operations teams are going to be abused during the next one to six years. There is very little understanding as to how the jobs will morph, and we grossly underestimated how complicated and challenging the cloudops roles would be.

It all starts upstream. You would expect companies to have a master plan to make things less complex and easier to operate. The fact is most are sprinting from one cloud migration to another, layering complex systems on top of complex systems, using whatever cloud technology seems cool at the time.

This results in a mix of containers, serverless computing, machine learning, big data using columnar databases, big data using object databases, eight brands and flavors of security, topped off with inconsistent governance models and tools. Guess where all this complexity goes to live a long life? Cloud operations. People are figuring out they are being set up for failure and are jumping ship before things get worse.

You have a couple of choices here: