Senior AWS DevOps Engineer

This engagement focuses on hardening and automating an existing AWS estate so it can scale smoothly through upcoming product launches. I need an engineer who has spent at least four years living in the DevOps world and can take ownership of the entire release workflow—from infrastructure provisioning to runtime monitoring—without constant hand-holding. The cloud layer is 100 % AWS, so deep familiarity with its core services (VPC, EC2, ECS/EKS, RDS, IAM, CloudWatch, etc.) is essential. All infrastructure changes are to be expressed as code; I have already standardised on Terraform and would like you to extend and refine those modules rather than starting from scratch. Our build and release processes currently run across three tools—Jenkins, GitHub Actions and GitLab CI/CD—because different teams have different historical preferences. You will be expected to streamline these pipelines, add automated testing and security gates, and document the workflow so future contributors can follow it effortlessly. Containers are already used in development, and the next step is production-grade Kubernetes. You’ll package the applications with Docker, push them to ECR, and orchestrate them on an EKS cluster, wiring in blue/green or canary deployments as appropriate. Robust scripting skills in Python or Bash (PowerShell when targeting Windows hosts) will be needed for glue logic and one-off automation. Reliability is non-negotiable, so part of the job is to hook everything into CloudWatch, Prometheus, Grafana and an alerting channel that wakes the right people only when absolutely necessary. Production issues must be traceable and recoverable within SLA. Deliverables you will hand over: • Re-usable Terraform modules covering network, compute, storage and IAM • Unified CI/CD pipelines in Jenkins, GitHub Actions and GitLab CI/CD with security and quality gates • Dockerfiles and Kubernetes manifests/Helm charts ready for EKS deployment • Monitoring and alerting configuration with clear runbooks and rollback procedures • Concise documentation and a walkthrough session to transfer knowledge Work begins as soon as we agree on milestones and cut-over dates. All code will live in my organisation’s GitHub repo, and you will push through PRs so we keep a clean audit trail. If your background matches the stack above and you are comfortable owning production outcomes, I’m ready to move quickly.