Senior DevOps Engineer

WeDo; Greater London; Hybrid; GBP 90,000 - 120,000; Full time

Job summary

WeDo is seeking a DevOps/Cloud Engineer with a security-first mindset to join during its cloud and security journey. UK-based with 1 day per month in Shoreditch, London, the role sits in a DevOps/Platform function aiming for SOC 2 compliance by Q1 2027 and ISO AI Governance achievement.

You will bridge DevOps, Cloud and Security across AWS and Azure, implement secure by design practices, and contribute to governance and automation as the team migrates client environments.

Qualifications

• Experience across AWS and Azure cloud environments with security focus.
• Ability to implement security controls in CI/CD pipelines.
• Hands-on with IaC and cloud security tooling.
• Strong understanding of IAM, RBAC and least-privilege access.

Responsibilities

• Improve security across AWS and Azure environments.
• Work with AWS: GuardDuty, CloudTrail, IAM, Security Hub.
• Work with Azure: Defender for Cloud, Entra ID, Key Vault, Azure Policy.
• Strengthen IAM, RBAC and least-privilege access.
• Embed security into CI/CD pipelines.
• Support Infrastructure as Code with security controls.
• Improve cloud monitoring, logging, observability.
• Identify vulnerabilities and misconfigurations.
• Embed Zero Trust across infra and cloud services.
• Automate security and infra processes.
• Assist client migrations to AWS and Azure.
• Collaborate with Platform/DevOps and Compliance teams on SOC 2.

Skills

DevOps background

Security mindset

AWS/Azure experience

CI/CD tooling

Scripting: Python

IAM & RBAC

Tools

Terraform

CloudFormation

GitHub Actions

GitLab CI

Azure DevOps

Jenkins

Job description

Location: UK-based – 1 day per month in Shoreditch, London

Work Type: Permanent

Role

Are you a DevOps or Cloud Engineer who enjoys the security side of what you do and wants to make it a bigger part of your career?

This is an opportunity to join a technology business at an important point in its cloud and security journey.

Over the last two years, the business has been focused on moving its hosting into the cloud, predominantly across AWS, while continuing to grow its Azure footprint. There are still client environments being migrated, alongside a wider focus on improving security, reducing technical debt and strengthening the overall cloud platform.

Security currently sits within the DevOps/Platform function, and with the business working towards SOC 2 compliance by Q1 2027, they’re looking for someone who can bring together strong DevOps fundamentals with a security-first mindset.

Responsibilities

You’ll work across DevOps, Cloud and Security, helping to build more secure, observable and resilient cloud environments.

Day to day, this could include:

• Improving security across AWS and Azure cloud environments
• Working with AWS security services including GuardDuty, CloudTrail, IAM and Security Hub
• Working across Azure security services such as Microsoft Defender for Cloud, Entra ID, Key Vault and Azure Policy
• Strengthening identity and access management, including RBAC, least-privilege access and authentication controls
• Building security controls and best practices into CI/CD pipelines
• Supporting Infrastructure as Code and embedding security into cloud deployments
• Improving cloud monitoring, logging, alerting and observability
• Identifying vulnerabilities, cloud misconfigurations and potential security risks
• Helping embed a Zero Trust approach across infrastructure and cloud services
• Automating repetitive security and infrastructure processes
• Supporting ongoing client migrations into AWS and Azure
• Working alongside the wider Platform/DevOps and Compliance functions as the business progresses towards SOC 2 compliance
• Helping shift security further left within the engineering lifecycle

Required Skills

You don’t need to be a career Security Engineer.

We’re looking for someone with a strong DevOps, Platform or Cloud Engineering background who has naturally gravitated towards security and wants that to become a bigger part of their role.

Experience across some of the following would be valuable:

• AWS experience, ideally with exposure to IAM, GuardDuty, CloudTrail and/or Security Hub
• Azure experience, particularly around Defender for Cloud, Entra ID/IAM, Key Vault, Azure Policy and cloud security best practices
• Infrastructure as Code such as Terraform or CloudFormation
• CI/CD tooling such as GitHub Actions, GitLab CI, Azure DevOps or Jenkins
• Scripting and automation using Python, Bash or PowerShell
• Monitoring, logging and observability tooling
• Vulnerability management and cloud security scanning
• Secrets and key management
• IAM, RBAC and least-privilege access

Most importantly, you’ll have a security-first mindset. You might currently be the DevOps Engineer who is always thinking about IAM policies, vulnerabilities, cloud configuration, access controls and how infrastructure could be made more secure.

If that’s the direction you want your career to go, this role gives you the opportunity to make that transition.

Why should I apply?

This isn’t a role where you’ll simply inherit a finished platform and keep the lights on.

The business is still evolving its cloud environment, migrating clients, growing its Azure footprint and tackling technical debt, meaning there is plenty to get involved with and improve.

There’s also a clear security journey ahead. The business is targeting SOC 2 compliance by Q1 2027, while its work around AI and automation means security, compliance and governance are becoming increasingly important.

They were also one of the first two companies in the UK to achieve ISO certification for AI Governance, giving you exposure to an environment where cloud, security, AI and governance increasingly overlap.

For a DevOps/Cloud Engineer who wants to move towards DevSecOps/SecOps, this is an opportunity to take the security knowledge you’ve already built and make it a much bigger part of your career.

The interview process is straightforward:

Stage 1: Interview with the hiring manager, including a technical round

Stage 2: Interview with the wider team, which includes Engineering and Governance

Stage 3: Interview with CTO