Site Reliability / Gitops Engineer - job 2 of 2

As a Site Reliability / Gitops Engineer at Canonical, your primary responsibilities include applying your experience with Infrastructure as Code (IaC) to develop and improve automation processes within our Information Systems team. You'll automate software operations, maintain operational responsibility for core services, and work with observability tools. Additionally, you will collaborate with various teams to design service architecture and troubleshoot issues, making sure that our services are reliable and efficient.

To qualify for the Site Reliability / Gitops Engineer role at Canonical, candidates should hold a Bachelor's degree in computer science or a related field and possess significant experience in defining operations through code. Practical knowledge of Linux, cloud computing concepts, and experience in Python software development are crucial. A strong modern engineering background, as well as excellent communication skills in English, are also required to thrive in this role.

Canonicals supports the growth of a Site Reliability / Gitops Engineer through continuous engagement with team members, mentorship opportunities, and a commitment to shared learning. You’ll have uninterrupted development time for larger projects, and also get the opportunity to share your expertise during design sessions. This ensures that you not only evolve as a professional but also contribute to the team’s success.

Yes, the Site Reliability / Gitops Engineer position at Canonical is remote and available in any timezone. Canonical promotes a flexible work environment, allowing team members from around the globe to connect and collaborate, fostering a culture that values diverse experiences and backgrounds.

A Site Reliability / Gitops Engineer at Canonical should be well-versed in various open-source technologies, particularly those related to cloud computing. Familiarity with tools like Prometheus and Grafana for observability, and expertise in Linux storage systems, along with version control and CI/CD practices, are essential for effectively operating within Canonical’s technological landscape.

When discussing your experience with Infrastructure as Code, focus on specific projects where you've successfully implemented IaC. Highlight the tools you used, such as Terraform or Ansible, and how you applied these to automate the provisioning and management of infrastructure. Include examples of challenges you faced and how you overcame them to improve automation within your team.

In answering this question, share a specific example that outlines the context, your approach, and the results. Discuss strategies you used to enhance reliability, such as implementing redundancy, load balancing, or using monitoring tools. Emphasize the positive outcome and what you learned during the process.

Explain your methodology for prioritizing tasks as a Site Reliability Engineer, such as focusing on issues that affect service availability or security concerns. You can mention tools you use for task management or how you balance operational responsibilities with project work while ensuring effective communication with your team.

Discuss monitoring tools such as Prometheus, Grafana, or ELK Stack that you have experience with. Provide details about how you configured alerts, created dashboards, and used the tools to analyze and troubleshoot system performance or incidents. Emphasize any significant improvements that resulted from your monitoring efforts.

Highlight your commitment to continuous learning by mentioning resources you leverage, such as online courses, webinars, technical blogs, or open-source communities. Discuss any recent technologies or trends you've adopted and how they have positively impacted your work.

Provide insight into your strategies for capacity planning, such as analyzing historical data, forecasting usage patterns, and using performance metrics to inform your decisions. Discuss specific methodologies you've employed to optimize performance, like scaling resources or optimizing configurations.

Describe your systematic approach to troubleshooting complex issues, such as gathering information, isolating variables, and using logs to diagnose the problem. Provide an example of a complex issue you resolved and the steps you took to identify and fix it.

Share your experience with Continuous Integration and Continuous Deployment pipelines, detailing the tools you've used (like Jenkins, GitLab CI, or CircleCI). Discuss how you've implemented these pipelines to automate testing and deployment processes and any specific improvements in deployment frequency or reliability that resulted.

Express your vision of a successful SRE team, focusing on key elements such as collaboration, diverse skills, effective communication, and a culture of continuous improvement. Highlight the importance of supporting one another and sharing knowledge to achieve operational excellence.

Share your passion for open source by explaining how it fosters innovation, collaboration, and a sense of community in the tech industry. Discuss how working with open source technologies has influenced your career path and why you value being a part of this movement.