Platform Engineer at Progressive Edge

The Role

The senior platform / cloud engineer will be need working experience with Kubernetes and containerised workloads, CI/CD tools and in building and have experience supporting apps running on AWS. This includes:

• Leveraging expert knowledge across a broad variety of topics
• Ability to pick up unfamiliar tasks and learn as they go
• Working in teams following an Agile approach and interact closely to guide and assist engineering teams as they deliver business functionality
• Building complex platforms, and then making these platforms simple for engineering teams to consume through platform-level abstractions
• Mentoring and advising junior platform engineers as they grow in the field

Requirements:

• 3+ years of experience in a platform engineering capacity
• 4+ years of experience as a software engineer with experience in popular languages such as Java / JavaScript/ Golang / Python
• 4+ years of experience in public cloud (AWS / Azure / GCP)
• 4+ years of experience with containerisation and container platforms
• Experience with Kubernetes GitOps practices, and using tools such as ArgoCD / Flux and Helm/ Kustomize
• Experience with the implementation of monitoring and observability solutions (logging, metrics, and distributed tracing) using tools such as Loki, CloudWatch, Prometheus, Grafana, and Xray
• Familiar with DevOps practices and CI/CD tools (AWS DevOps Tools, Jenkins, GitHub actions, etc.)
• Proven experience building complex, production-grade platforms and making these available for self-service consumption by engineering teams

Expert knowledge of:

• Infrastructure as Code tooling (Terraform / CDK / Pulumi / Crossplane) and practices
• Container orchestration principles and Kubernetes, CKA certification preferable
• Public cloud providers (AWS / Azure / GCP) and best practices (Well Architected Frameworks), certification preferable
• Distributed systems, service architectures, cloud native systems, the problems they attempt to solve as well as the related trade-offs to contribute to feature and service design
• Building of platform APIs, automation, system-level tooling and/ or internal developer platforms