Site Reliability Engineer

Site Reliability Engineer II (aka SRE II) are specialists in treating operations as a software problem. They focus on reliability of systems and services - addressing availability, performance, scalability, latency, observability, efficiency. They work on maintaining key components and developing systems that will minimize human labor (through automation) and increase system reliability with the end goal of breaking the relationship between system size, operational toil and complexity.

SRE II are responsible for the implementation of technical solutions based on business requirements, they can estimate the effort and impact of the items they work on, and show a high quality of craft in what they deliver. SRE II work primarily within the scope of their team while occasionally collaborating across partner teams. They are expected to work together with colleagues (potentially in other job roles) to design and implement technical tasks. They are also expected to actively participate in incident response for issues affecting their team.

Because the required technical skills and commercial knowledge can vary from one area to another, SRE II can wear several hats; part of a business service owner team, owner of a piece of infrastructure, and/or consultant to product development teams regarding Site Reliability Engineering related scope.

Key Responsibilities

Building Software Applications

• Is responsible to build software applications by using relevant development languages and applying knowledge of systems, services and tools appropriate for the business area

• Is responsible to refactor and simplify code by introducing design patterns when necessary

• Is responsible to ensure the quality of the application by following standard testing techniques and methods that adhere to the test strategy

• Has sufficient knowledge to write readable and reusable code by applying standard patterns and using standard libraries

• Has sufficient knowledge to maintain data security, integrity and quality by effectively following company standards and best practices

Software Systems Design

• Has sufficient knowledge to evaluate possible architecture solutions by taking into account cost, business requirements, technology requirements and emerging technologies

• Has sufficient knowledge to describe the implications of changing an existing system or adding a new system to a specific area, by having a broad, high-level understanding of the infrastructure and architecture of our systems

• Has sufficient knowledge to help grow the business and/or accelerate software development by applying engineering techniques (e.g. prototyping, spiking and vendor evaluation) and standards

• Has sufficient knowledge to meet business needs by designing solutions that meet current requirements and are adaptable for future enhancements

End to End System Ownership

• Has sufficient knowledge to own a service end to end by actively monitoring application health and performance, setting and monitoring relevant metrics and act accordingly when violated

• Has sufficient knowledge to reduce business continuity risks and bus factor by applying state-of-the-art practices and tools, and writing the appropriate documentation such as runbooks and OpDocs

• Has sufficient knowledge to reduce risk and obtain customer feedback by using continuous delivery and experimentation frameworks

• Is responsible to independently manage an application or service by working through deployment and operations in production

… lees de volledige omschrijving bij Booking.com.