Find a job 
Featured Companies 
Featured Universities 
For Companies At a Glance
- Tasks: Join our DevOps team to automate AWS infrastructure and orchestrate containers with EKS.
- Company: Dynamic tech company fostering collaboration and innovation.
- Benefits: Enjoy 26 days holiday, competitive salary, and private medical insurance.
- Other info: Inclusive culture with opportunities for personal growth and team-building activities.
- Why this job: Make a real impact in a fast-paced environment while learning cutting-edge technologies.
- Qualifications: 3+ years in DevOps, strong AWS skills, and a passion for automation.
The predicted salary is between 60000 - 80000 £ per year.
We are looking for an AWS DevOps Engineer to join our DevOps team. You will focus exclusively on AWS and Amazon EKS, automating infrastructure with Terraform, orchestrating containers via EKS, building robust CI/CD with GitOps, and implementing strong monitoring/observability + AWS EKS IAM concepts to support secure, high-performance, cost-optimised systems. You will work closely with developers and SREs in an automation-first, collaborative culture.
Key Responsibilities
- Build and maintain robust CI/CD pipelines for automated testing, deployment, and rollouts in AWS/EKS.
- Manage and optimize Amazon EKS clusters for container orchestration in production.
- Implement and evolve Infrastructure as Code (IaC) using Terraform on AWS.
- Support live production AWS/EKS environments, including on-call rotation, incident response, root cause analysis, and blameless post-mortems.
- Automate provisioning, configuration, scaling, observability, and secure workload access across AWS services.
- Collaborate on improving system reliability, observability, security (DevSecOps/EKS IAM), and AWS cost optimization.
Qualifications
- Strong Linux system administration (file systems, processes, networking, troubleshooting, bash scripting).
- Scripting & programming in Python and Bash/Shell; Go/Typescript is a nice-to-have.
- Git workflows, branching strategies, and version control best practices.
- Proficiency with AWS (core services like EC2, VPC, IAM, S3, RDS, Lambda, EKS, CloudWatch, etc.; production-grade experience required).
- Solid experience with Amazon EKS (cluster creation/management, node groups, add-ons, upgrades, scaling, troubleshooting).
- Infrastructure as Code (IaC) expertise, with Terraform strongly preferred (AWS provider/modules experience a must).
- Familiarity with Helm charts and Kustomize (for packaging, templating, versioning, and deploying Kubernetes applications/add-ons in EKS environments).
- Hands-on building and maintaining CI/CD pipelines using GitHub Actions or GitLab CI/CD, plus ArgoCD (GitOps).
- Experience with monitoring/observability tools (Prometheus, Grafana, ELK stack, Datadog, OpenTelemetry) – including metrics, logs, traces, dashboards, alerting, and integration with AWS services (e.g., CloudWatch, X-Ray).
- Solid understanding of AWS EKS IAM concepts, especially for EKS, including: IAM Roles for Service Accounts (IRSA); EKS Access Entries and Access Policies (Cluster Access Management API); EKS Cluster IAM Role and Node IAM Role configuration/management; Principle of least privilege, temporary credentials, avoiding over-permissive roles, credential isolation, and integration between IAM and Kubernetes RBAC.
- Experience analysing and optimising AWS costs using tools such as AWS Cost Explorer, Compute Optimizer, and EKS workload right-sizing.
Skills
- 3+ years of hands-on experience in DevOps, Site Reliability Engineering (SRE), infrastructure engineering, or closely related roles (focused on AWS/EKS environments).
- Proven track record building and maintaining production-grade CI/CD pipelines with AWS/K8S.
- Bachelor's degree in Computer Science, Engineering, IT or equivalent practical experience (degree-optional – we value hands-on AWS/EKS impact most).
- Excellent problem-solving and troubleshooting, especially under pressure in production AWS/EKS setups.
- Automation-first mindset with a passion.
- Growth mindset – eagerness to continuously learn, adapt to evolving AWS/EKS technologies and best practices, embrace challenges as opportunities for improvement, and turn incidents/post-mortems into actionable learning for personal and team growth.
- Proven ability to collaborate effectively with cross-functional stakeholders, including engineering, SRE, security, and product teams.
- Maintain clear technical documentation, runbooks, and operational playbooks for production systems.
We Offer
- Experience a dynamic and team-orientated work environment.
- Opportunities for personal growth and learning.
- An open, inclusive and supportive team where you will be valued, and your suggestions will be welcome.
- 26 days paid holiday per year, in addition to local public holidays.
- Competitive salary.
- Risk Benefits such as pension, Life Assurance (4x annual salary), Private Medical Insurance.
- Team Building activities.
- Local discounts and more!
AWS DevOps Engineer in London employer: Tain
Contact Detail:
Tain Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land AWS DevOps Engineer in London
✨Tip Number 1
Network like a pro! Reach out to folks in the industry, attend meetups, and connect with people on LinkedIn. You never know who might have the inside scoop on job openings or can refer you directly.
✨Tip Number 2
Show off your skills! Create a GitHub repository showcasing your projects, especially those involving AWS, Terraform, and CI/CD pipelines. This gives potential employers a taste of what you can do without them having to dig through your CV.
✨Tip Number 3
Prepare for interviews by practising common DevOps scenarios. Brush up on your knowledge of AWS services, EKS, and IaC. Mock interviews with friends can help you feel more confident and ready to tackle any technical questions thrown your way.
✨Tip Number 4
Don’t forget to apply through our website! We love seeing candidates who are genuinely interested in joining our team. Plus, it’s a great way to ensure your application gets the attention it deserves.
We think you need these skills to ace AWS DevOps Engineer in London
Some tips for your application 🫡
Tailor Your CV: Make sure your CV highlights your experience with AWS, EKS, and Terraform. We want to see how your skills align with the role, so don’t be shy about showcasing relevant projects or achievements!
Craft a Compelling Cover Letter: Your cover letter is your chance to shine! Use it to explain why you’re passionate about DevOps and how you can contribute to our team. Keep it concise but impactful – we love a good story!
Show Off Your Projects: If you've worked on any cool projects involving CI/CD pipelines or container orchestration, make sure to mention them. We’re keen to see your hands-on experience and how you’ve tackled challenges in the past.
Apply Through Our Website: We encourage you to apply directly through our website. It’s the best way for us to receive your application and ensures you don’t miss out on any important updates from our team!
How to prepare for a job interview at Tain
✨Know Your AWS Inside Out
Make sure you brush up on your AWS knowledge, especially around core services like EC2, VPC, IAM, and EKS. Be prepared to discuss how you've used these services in past projects, as well as any challenges you faced and how you overcame them.
✨Show Off Your CI/CD Skills
Be ready to talk about your experience with building and maintaining CI/CD pipelines. Highlight specific tools you've used, like GitHub Actions or GitLab CI/CD, and share examples of how you've automated testing and deployment processes in AWS/EKS environments.
✨Demonstrate Your IaC Expertise
Since Infrastructure as Code is a big part of the role, make sure you can explain your experience with Terraform. Discuss how you've implemented IaC in previous roles, including any challenges you faced and how you ensured your infrastructure was secure and cost-optimised.
✨Prepare for Problem-Solving Scenarios
Expect to be asked about troubleshooting and incident response. Think of specific examples where you had to analyse issues in production AWS/EKS setups, what steps you took to resolve them, and how you documented the process for future reference.