We’re witnessing the rise of the SRE (Site Reliability Engineer, in original Google parlance, but now service reliability engineer to others) job title alongside the growth of the DevOps movement.
It seems SREs and DevOps roles are inexorably mixed now. Visit any company practicing DevOps and operating at scale in production, and they will tell you they are looking to recruit a few unicorn SREs.
The job recs are pretty heavy though — ‘Seeking software engineers skilled in all current development and delivery platforms, who also know operations inside and out. Sysadmin types who can respond to tickets and keep everything running flawlessly, while working with the DevOps team to break down silos, define infrastructure as code, and release faster and faster.’
Sounds easy enough, right?
Not so easy. While becoming an SRE is likely a financially rewarding career move, it’s not an easy one to make and has serious hazards — chief of which is the difficulty of catching up with the ever-increasing pace of change.
Keeping up with change
If DevOps is considered a team sport, the SRE on each team might be the goalie, the stadium facility manager, and the play review referee up in the booth all rolled into one. SREs are generally associated with ensuring highly available ‘day 2+’ operations (or maybe ‘minute two’ at these release rates) of any software the DevOps teams put into production…
Read the entire article on Evolven.com here: https://www.evolven.com/blog/change-awareness-the-sre-s-best-friend.html
©2019 Intellyx LLC. Intellyx retains final editorial control of this article. At the time of writing, Evolven and ServiceNow are Intellyx customers. None of the other companies mentioned in this article are Intellyx customers.
