Site Reliability Engineer

Skills

Description

Each of these SREs will be embedded into a separate scrum team on a rotation where at least 50% (or more) of their time will be dedicated to development efforts while the remainder of their time (which will be capped and no more that 50%) will be involved in operations work (incident tickets, on-call, knowledge sharing with each other, coordinating knowledge transfer sessions etc.). The SREs will report to the Manager of Site Reliability and will collaborate extensively with each other and be part of an on-call rotation that may require 4-5 after-hours work per week as part of an on call rotation. They would be expected to be on call 1 of every 4 or 5 weeks.

Development efforts will initially focus on PBIs that improve observability, dashboarding, performance or other site reliability concerns. However, after clearing technical debt the developers will be allowed to take on features or other work that keeps them up to date on relevant technologies/methodologies/products that the Scrum team is working on.

Additionally the SRE will lead the day-of-deployment monitoring and participate in Go/No-Go calls.

This person should have experience as intermediate wed development experience in either Java, C#/.Net or front end skills (Javascript, Front-end frameworks, CSS, HTML, Angular, React JS).
Required Skills: .NET, AWS, C#, Kubernetes, SRE, Cloud/DevOps Engineering
Nice-to-Have Skills: Dynatrace, Splunk

Responsibilities

• An SRE role focused on improving observability, dashboarding, performance, and site reliability. Candidates should have a background in .NET, AWS, and Kubernetes, and experience with DevOps tools such as Ansible, Puppet, Chef, Jenkins, and APM tools like Dynatrace and New Relic.