> Markdown version of [/jobs/ext/3273687-lead-devops-engineer](https://www.wearedevelopers.com/jobs/ext/3273687-lead-devops-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Lead DevOps Engineer

- **Company:** Liberis Limited
- **Location:** London, UK
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** .NET Framework, Microsoft Azure, C Sharp (Programming Language), Cloud Computing, Cloud Engineering, Continuous Integration, DevOps, Github, Python (Programming Language), Node.Js, Datadog, Data Logging, Cloud Platform System, Containerization, Kubernetes, Dynatrace, Docker
- **Published:** September 2, 2026
- **Apply:** https://www.apply4u.co.uk/jobs/lead-devops-engineer/46228649

## About the Role

with Chess (Internal Recruiter) (30 mins)Video interview with the Hiring Manager (45 mins)In person code pairing interview with a member of Engineering team (1 hour)Video interview with the wider Liberis team (1 hour)What we think you'll need:Proficient in at least one of .NET (C#), Node.js and Python - able to build, configure, and template production-grade services in each.Strong GCP experience (Azure experience is nice to have)Hands-on experience designing reusable CI/CD pipeline templates - GitHub Actions or Azure DevOps - consistent across stacks and teams.Comfortable with containerisation (Docker) and deployment on Kubernetes or Cloud Run.Observability experience with at least one of: Datadog, incident.io, or cloud-native logging and monitoring (GCP Cloud Operations or Azure Monitor).Infrastructure-as-code with Terraform.A proven track record of driving adoption - building things engineers use, writing docs that get read.Career development is really
important to us here at Liberis, with progression opportunities for both individual contributors and people managers. You can have a look through our Engineering Career Framework via this link Our hybrid approachWorking together in person helps us move faster, collaborate better, and build a great Liberis culture. Our hybrid working policy requires team members to be in the office at least 3 days a week. At Liberis, we embrace flexibility as a core part of our culture, while also valuing the importance of the time our teams spend together in the office.#LI-FC1

## Description

distributed tracing, and alerting integrated into service templates so every new service is production-ready from day one.Work hands-on with Datadog, incident.io, and/or GCP/Azure-native logging and monitoring tooling to build the platform-level observability layer teams plug into.Contribute to our thinking on a potential Azure-to-GCP migration - helping assess what changes for developer tooling and service templates and building proof-of-concept work that informs the decision.Partner with product engineers to understand where developer experience breaks down - slow pipelines, confusing templates, missing runbooks - and fix the root causes, not the symptoms.Lead technical decisions on platform tooling: evaluate new tools, write ADRs, and drive adoption of improvements across multiple engineering teams.Mentor engineers in the Cloud Platform team and act as a go-to resource for product engineers getting to grips with platform tooling.The interview process:Screening call