Senior Site Reliability Engineer - Wikimedia Enterprise

Senior Site Reliability Engineer

Summary

The Wikimedia Foundation is looking for a Senior Site Reliability Engineer to join our team, reporting to the Sr. Engineering Manager. As the Site Reliability Engineer, you will play a key role in designing, developing, and maintaining reliable, scalable, and highly available infrastructure for our API services. You will contribute heavily to the high impact challenges behind innovating, building, and maintaining Wikipedia’s data feeds for high volume reusers. In this role, you will foster cross department collaboration with the wikimedia foundation SRE teams. You will be responsible for ensuring the uptime, performance, and security of our systems, and work closely with the development team to continuously improve our infrastructure and processes. you will be involved in designing and running the infrastructure and services that interact with the base of Wikimedia Foundation’s projects, including, but not limited to: Kubernetes clusters, application servers, code collaboration infrastructure, and  other developer-facing services. You will participate in incident response and be oncall. This role requires frequent work with other members of the enterprise and Foundation SRE team to maintain and improve our systems, as well as interacting with people not in SRE, like Security, Release and Software Engineers, together striving to move our projects and technologies forward. 

Wikimedia Enterprise is a new, revenue-generating product that provides fast, comprehensive, reliable, and secure data ingestion for organizations that wish to repurpose Wikimedia/Wikipedia content in third party environments. Wikimedia Enterprise aims to improve the user experience for Wikimedia/Wikipedia readers beyond our own websites; increase the reach and discoverability of Wikimedia/Wikipedia content; and improve awareness and ease of attribution and verifiability of Wikimedia/Wikipedia content by the organizations that reuse our content the most. You can learn more about the project in WIRED and Insider.

We are a distributed and diverse team of engineers with a drive to explore, experiment, and embrace  technologies. We act sort of like a startup within the Wikimedia Foundation: we build quickly, deploy often, and our work has a very high impact on the global knowledge ecosystem. If you are up to the challenge of working on something fast paced, of creating services that will revolutionize the systems distributing our knowledge for billions of people across the world, and enjoy the idea of working with a globally distributed team, you might be just the person we need. 

You are responsible for:

• Design, implementation and maintenance of public facing infrastructure and services
• Use of configuration management and deployment tools
• Architectural design and operation at scale
• Monitoring of systems and services, optimization of performance and resource utilization
• Common operating system level tasks such as logging and backup / restore
• Cookbook / runbook implementation for common maintenance actions
• Incident response, diagnosis and follow-up on system outages or alerts
• Automation and streamlining of tasks as well as identifying process gaps
• Collaborating with a global and asynchronously communicating team (don’t worry if you have never worked remotely, we’ll help you get used to it)
• Mentoring peers in your areas of technical and operational strength

Skills and Experience:

• Strong experience with automation and configuration management tools such as Terraform, Ansible. Proficient in at least one programming language (Python,, Go, or similar). 
• Strong understanding of CI/CD pipelines and deployment strategies.
• Experience managing Cloud services and discovering cost savings (AWS, Azure, GCP) 
• Experience with monitoring, logging, and alerting tools such as Prometheus, Grafana, or ELK stack.
• Strong troubleshooting and problem-solving skills, and ability to work effectively under pressure. 
• Excellent communication skills with a strong emphasis on contributing to documenting processes and runbooks, and ability to collaborate effectively with cross-functional teams.
• Incident Management: Experience with incident management and on-call rotation practices, as well as tools like PagerDuty or Opsgenie. 
• SRE Best Practices: Understanding of SRE principles, such as Service Level Objectives (SLOs), error budgets, and blameless postmortem. 
• Familiarity with Wikimedia or other open source projects is a plus.
• I