Cloud Engineer

London
10 months ago
Applications closed

Related Jobs

View all jobs

Cloud Engineer - Fully Remote Contract (OUTSIDE)

Google Cloud Engineer

Google Cloud Engineer - GAE

Senior GCP Network Engineer

DevSecOps Engineer

Cloud Consultant

Job Title: Lead Cloud Engineer

Location: London (Hybrid)

Job Description:

Role Summary:

  • Lead the design, deployment, and management of AWS-based infrastructure, ensuring high availability, scalability, and security.

  • Architect, deploy, and maintain secure cloud-based applications and solutions on AWS services such as EC2, S3, RDS, Lambda, CloudFormation, and VPC.

  • Collaborate with development, operations, and security teams to design scalable and highly available solutions on AWS.

  • Implement and manage cloud security best practices, including IAM, encryption, firewalls, and compliance with regulatory requirements such as PCI DSS.

  • Ensure smooth integration of legacy mainframe applications with AWS cloud infrastructure and manage hybrid cloud solutions.

  • Oversee the integration of payment systems and ensure secure and compliant handling of payment transactions.

  • Design and implement disaster recovery plans, backup strategies, and business continuity for AWS-hosted applications and data.

    Qualifications:

    Experience Required:

  • 7+ years of experience in cloud engineering or architecture, with a focus on AWS.

  • At least 3+ years of experience leading cloud engineering teams or projects on AWS.

  • Experience working with AWS services, including EC2, S3, VPC, Lambda, RDS, CloudFormation, and IAM.

  • Strong knowledge of mainframe systems and experience integrating them with AWS.

  • Experience with payment systems and ensuring compliance with security and regulatory requirements (e.g., PCI DSS).

    Skills & Expertise:

  • Expertise in AWS infrastructure design, automation, and orchestration using tools such as CloudFormation, Terraform, or AWS CDK.

  • Deep understanding of AWS networking concepts, including VPC, Direct Connect, VPN, Load Balancers, and Route 53.

  • Proficient in AWS security practices, including IAM, KMS, security groups, NACLs, and multi-factor authentication.

  • Solid experience in containerization and orchestration using AWS services like ECS, EKS, and Docker.

  • Strong understanding of microservices architecture, serverless computing with AWS Lambda, and event-driven architectures.

  • Ability to design and implement highly available, fault-tolerant systems using AWS services.

  • Expertise in monitoring and troubleshooting AWS environments using CloudWatch, X-Ray, and other AWS tools

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Edge Computing Tools Do You Need to Know to Get an Edge Computing Job?

If you’re trying to start or grow a career in edge computing, it can feel like you’re navigating a maze of tools, frameworks and platforms — Kubernetes, Docker, IoT frameworks, AWS Greengrass, Azure IoT Edge, OpenShift, TinyML toolkits, networking orchestration, real-time streaming frameworks, and on it goes. Scroll job boards and community forums and it’s easy to conclude that unless you master every buzzword imaginable, you’ll never get a job. Here’s the honest truth most edge computing hiring managers won’t necessarily say out loud: 👉 They don’t hire you because you know every edge computing tool — they hire you because you can solve real system problems using the tools you know. Tools matter, yes — but only when they support clear outcomes: reliable systems, performance at scale, secure edge deployments and real business value. So how many edge computing tools do you actually need to know to secure a job? For most edge computing roles, the answer is fewer than you think — and a lot clearer when sorted by fundamentals and roles. This guide shows you what matters, what doesn’t, and how to focus your time wisely so you come across as capable, confident and employable.

What Hiring Managers Look for First in Edge Computing Job Applications (UK Guide)

In today’s fast-evolving tech landscape, edge computing is one of the most sought-after fields — blending distributed systems, embedded systems, networking, cloud, IoT, data and real-time processing. But that also means hiring managers are highly selective. They scan applications fast and look for signals of relevance, impact, technical depth and real-world delivery long before they read every line. This guide demystifies what hiring managers in edge computing look for first in your application — so you can tailor your CV, portfolio and cover letter to jump out of the stack. Whether you’re targeting edge systems roles, embedded IoT edge jobs, edge-native data roles, edge platform engineering or edge-AI positions, this checklist will help you position your experience in a way hiring managers can trust immediately.

The Skills Gap in Edge Computing Jobs: What Universities Aren’t Teaching

Edge computing is rapidly moving from niche concept to critical infrastructure. As organisations deploy connected devices, sensors, autonomous systems and real-time analytics, processing data closer to where it is generated has become essential. From smart cities and manufacturing to healthcare, transport, defence and telecommunications, edge computing underpins systems where latency, reliability and resilience matter. Demand for edge computing skills across the UK is rising steadily — yet employers consistently report difficulty finding candidates who are genuinely job-ready. Despite growing interest and academic coverage, universities are not fully preparing graduates for real edge computing jobs. This article explores the edge computing skills gap in depth: what universities teach well, what they consistently miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build sustainable careers in edge computing.