Position: Senior Site Reliability Developer
Company: Svitla Systems
Category: DevOps
Experience required: 5y
English level: upper

**Requirements:**
- Bachelor’s degree in Computer Science, Engineering, or a related technical field (Master’s degree, an asset).
- Minimum 6 years of experience working as a Site Reliability Developer.
- At least 6 years of experience administrating Linux-based environments (Red Hat, CentOS, Debian, or Ubuntu).
- At least 6 years of experience with service-oriented architectures and micro-services.
- At least 2 years of working in Agile development life cycle.
- A minimum of 6 years of experience practicing continuous integration and continuous delivery.
- Minimum 3 years of experience with infrastructure automation frameworks in (at least two of these technologies: Saltstack, Terraform, or Cloud Foundation engine).
- Expertise in infrastructure to support a microservice architecture.
- A minimum of 3 years experience in infrastructure-as-code, specifically with Terraform.
- Strong knowledge of caching technologies (Fastly, Redis) with the ability to identify opportunities for improvement.
- Expertise in RDBMS (MySQL, Postgres) and NoSQL (DynamoDB, DocumentDB, MongoDB) databases at scale.
- Proficiency in cloud resources (AWS) with the ability to operate them for the components owned (certification is preferred).
- Ability to use containers and orchestration frameworks (Kubernetes, Docker, Container registries, etc.).
- Proficiency in Git.
- At least 2 years of experience with Kubernetes.
- Bilingual in French and English.
- Willingness and ability to learn fast.
- High work ethic and results-oriented.
- High sense of accountability and ownership.
- Solution-oriented mindset and can-do attitude to overcome challenges.
- Team player with a natural ability to build relationships.
- Ability to thrive in a fast-paced environment and master frequently changing web technologies and techniques.

**Nice to have:**
- Experience with Amazon EKS, ECS.

**Responsibilities:**
Production Operations - 45%
- Handle emergency response either by being on-call or reacting to symptoms according to monitoring and escalation when needed.
- Be accountable for ensuring & improving documentation on-site reliability measures, either in application documentation or in runbooks, explaining the issues encountered and the solutions implemented.
- Actively seek and identify opportunities to improve the availability and performance of the system by applying the learnings from monitoring and observation.
- Identify parts of the system that do not scale, provide immediate palliative measures and drive long-term resolution of these incidents.
- Improve the client’s codebase by resolving issues.
- Optimize cloud cost and reduce system resource usage by setting clear requirements through efficiency and capacity planning.

Maintain Service Level Objectives (SLO)/ Service Level Indicator (SLI) - 35%
- Plan, design, and execute solutions within the infrastructure team to reach specific goals agreed upon within the team.
- Share the learnings publicly by creating issues that provide context for anyone to understand or by writing blog posts.
- Propose ideas and solutions within the infrastructure team to reduce the workload by automation.
- Identify Service Level Indicators (SLIs) that will align the team to meet the availability and latency objectives.
- Perform and run blameless RCAs on incidents and outages, aggressively looking for answers that will prevent the incident from ever happening again.

Knowledge sharing & coaching - 20%
- Actively contribute to the client’s university, the internal peer learning platform, to promote continuous learning.
- Participate in the onboarding of new developers.
- Mentor junior in all areas and other SREs in their area of profound knowledge.
- Set an example for a team of SREs with positive and inclusive leadership and discussion on work.
- Be trusted to de-escalate conflicts inside the team.
- Review Pull Request documentation to guide and upskill junior developers on various technical/SRE topics.