Aws DevOps Engineer -N

Role & responsibilities

Desired Competencies (Technical/Behavioral Competency)

Must-Have

• Minimum 8 years of experience working on Cloud technologies and/or SRE role

• Hands on experience with AWS services (EC2, EKS, VPC, IAM, Load balancers etc.) and containerization tool Openshift

• Hands on experience with monitoring and observability, best practices

• Well versed with hands on experience in Terraform

• Hands on experience in GitHub.com including GitHub action workflows

• Experience with Kubernetes, Helm chart / Gitops

• An advocate and practitioner of the Production management techniques and philosophy laid out in the SRE Handbook

• Expertise of managing AWS Production Environments and applying SRE practices

• Experience of establishing SLOs and metrics to measure and track service levels for Cloud based deployments

• Experience of establishing automated acceptance testing criteria

• Experience of establishing health and monitoring infrastructure in AWS

• Experience implementing monitoring tools such as PagerDuty would be desirable

• Significant experience in a technical engineering role related to software development, testing or operations, with a very high level of knowledge across all these activities in addition to any specialism.

• Remaining relevant, up to date, connected to the wider technology community with an eye on future technologies, trends, opportunities and our competition is an expectation of all Engineers.

• Willingness to develop their breadth of skills whilst maintaining and developing specific technical skills.

• Able to demonstrate a high skill level across all the activities required to create tested and maintainable code, with an understanding of how effective teams operate in order that they can deploy to production at least once a day.

• Significant experience with high degrees of personal and team ownership.

• Able to perform the Technical Owner function within a team, acting as that teams most senior Engineer, taking ownership for practices to ensure quality and for emergent architectural decisions.

• Expect to be that team’s technical representative with the Product Owner, and in the wider organization.

• Significant working knowledge of agile concepts and expertise playing a very active role in Agile working, leading sessions and workshops with technical and non-technical colleagues.

• Able to demonstrate a high degree of ability to collaborate with others, communicating with technical and non-technical colleagues and be open about successes and failure. They should be a leader within the Engineering community, representing technical concerns in the team and taking on responsibility for driving collaboration, technical and non-technical good practices in their team and beyond

• Able to operate effectively within an agile structure, with separation between their community of peers, delivery and line management responsibilities.

Good-to-Have

Client facing & Stakeholder management

Good communication skills & team leader skills