Site Reliability Engineer II

• Building Software Applications

1. Responsible for building software applications using relevant development languages and applying knowledge of systems, services, and tools appropriate for the business area.
2. Refactor and simplify code by introducing design patterns when necessary.
3. Ensure the quality of the application by following standard testing techniques and methods that adhere to the test strategy.
4. Write readable and reusable code by applying standard patterns and using standard libraries.
5. Maintain data security, integrity, and quality by effectively following company standards and best practices.

• Software Systems Design

1. Evaluate possible architecture solutions by taking into account cost, business requirements, technology requirements, and emerging technologies.
2. Describe the implications of changing an existing system or adding a new system to a specific area with a broad, high-level understanding of the infrastructure and architecture of systems.
3. Help grow the business and/or accelerate software development by applying engineering techniques (e.g., prototyping, spiking, and vendor evaluation) and standards.
4. Design solutions that meet current requirements and are adaptable for future enhancements.

• End to End System Ownership

1. Own a service end to end by actively monitoring application health and performance, setting and monitoring relevant metrics, and acting accordingly when violated.
2. Reduce business continuity risks and bus factor by applying state-of-the-art practices and tools, and writing appropriate documentation such as runbooks and OpDocs.
3. Reduce risk and obtain customer feedback using continuous delivery and experimentation frameworks.
4. Independently manage an application or service by overseeing deployment and operations in production.
5. Maintain data security, integrity, and quality by following company standards and best practices.

• Technical Incident Management

1. Address and resolve live production issues by mitigating customer impact within SLA.
2. Improve the overall reliability of systems by producing long-term solutions through root cause analysis.
3. Track incidents by contributing to postmortem processes and logging live issues.

• Automation and Toil Reduction

1. Ensure that infrastructure stays current by reducing technical debt, searching for bottlenecks, and preparing for scaling.
2. Reduce the cost of operations and maintenance by leveraging new technologies, automation, and partnering with vendors to stay current.
3. Reduce human labor by writing small software features that address availability, scalability, latency, and efficiency.

• Monitoring and Alerting Improvements

1. Review and verify the performance of production systems and network infrastructure by continuously monitoring appropriate observability metrics, business KPIs, and capacity planning.
2. Improve application reliability by partnering with development teams to advise on setting appropriate observability metrics.

• Critical Thinking

1. Systematically identify patterns and underlying issues in complex situations, finding solutions by applying logical and analytical thinking.
2. Constructively evaluate and develop ideas, plans, and solutions by reviewing them, objectively considering external knowledge, initiating SMART improvements, and articulating their rationale.

• Continuous Quality and Process Improvement

1. Identify opportunities for process, system, and structural improvements (e.g., performance gains) by evaluating current process flows, methods, and standards.
2. Design and implement relevant improvements by defining new or adapted process flows, standards, and practices that enable business performance.

• Effective Communication

1. Deliver clear, well-structured, and meaningful information to a target audience using suitable communication mediums and language tailored to the audience.
2. Achieve mutually agreeable solutions by staying adaptable, communicating ideas clearly, and practicing active listening.
3. Ask relevant follow-up questions to properly engage with the speaker and really understand what they are saying, applying listening and reflection techniques.

• Architectural Guidance

1. Advise product teams toward technical solutions that meet the functional, non-functional, and architectural requirements by challenging the rationale for application design and providing context in the wider architectural landscape.
2. Set a clear direction for technical capability by evaluating and aligning target architecture improvements, reframing architectural designs and decisions for varied stakeholders.

Communication

• Track Members:

1. Product Stakeholders
2. Peers

• Communication Type:

1. Cooperation - Information
2. Cooperation - Persuasion
3. Cooperation - Persuasion

• Communication Frequency:

1. Continuous
2. Frequent
3. Frequent

Level of Education

• Bachelor's degree in a relevant field

Years of Relevant Job Knowledge

• Broad Job Knowledge

  (3 - 5 years)

Requirements of Special Knowledge/Skills

• Building Software Applications
• Software System Design
• End to End System Ownership
• Technical Incident Management
• Operations (Automation & Toil)
• Observability (Monitoring & Alerting)
• Critical Thinking
• Continuous Quality & Process Improvement
• Effective Communication
• Architectural Guidance