The mythical rivalry that exists between the Development and Operations departments in technology companies is not a story of this decade. Not even from this century. That is why, in 2003, Ben Treynor, Google's vice president of Engineering, decided to put programming specialists to carry out tasks specific to the operational area. Thus was born the concept of Site Reliability Engineering and, with it, the position of Site Reliability Engineer (SRE), a figure increasingly appreciated by companies that aspire to innovate regularly in their products, but maintaining at the same time a high level of service reliability.The SRE team comes to put peace between Development professionals, who aspire to launch more functionalities at the highest possible pace; and the members of the Operations segment, whose obsession is the stability of products. Thanks to SREs, each engineering division can fully focus on its objectives:
Have you thought about working as an SRE? It is a rising role that brings together the best of two worlds and will allow you to learn something new every day. Find out how far you could go and what training and skills you need to get there.
The Site Reliability Engineer (SRE) is a position that splits your time between developing software for stability and performance improvement; and monitoring and problem solving, to ensure both service availability and business growth and innovation.
The SRE specialists are dedicated to devising systems that have a high tolerance for failures, using strategies such as gradual degradation (deactivation of some processes so that the system continues to function, even with incidents); or defense in depth, which provides ways for errors to correct themselves automatically.
The fact that the role of Site Reliability Engineer is conceived as a bridge between Development and Operations leads to confusion with that of an engineer or DevOps engineer. The clearest distinction comes from the hand of Google, which indicates that:
This volume includes basic concepts -according to Google- to delimit and coordinate the work of the SRE, such as:
However, it must be borne in mind that Google's methodology is... that, very Google. And that, outside of there, there will not be two SREs or two equal DevOps, as other companies mix and modulate the tasks of these two profiles according to their needs.
To work as an SRE, your resume should integrate the following vertices:
Professionals in the computing sector are currently facing a multitude of challenges, such as data storage in times of big data, digital transformation, the use of open source software or the renewal of legacy structures. At Site Reliability Engineering, the challenge is automating the most repetitive and cumbersome work (called toil, in Google SRE team jargon).
Likewise, we must not lose sight of the fact that the tasks of resolution of incidents usually absorb a good part of the working hours of the SREs. In fact, according to Catchpoint's 2019 SRE Report, which annually conducts a survey to assess the state of the profession, 49% of site reliability engineers say they have had to deal with one of these issues in the past week. And 50% of the sample affirms to have had to solve cuts in the service of more than a day of duration in some moment of her career.
Can you identify with this description and you would not hesitate to use yourself thoroughly to end any treacherous software failure? So working as an SRE is your thing. Come to BETWEEN and climb one more step in your professional career with us!