Devops Engineer - Perm (FTC) - Hybrid

London
10 months ago
Applications closed

Related Jobs

View all jobs

Senior Data Engineer

Data Engineer

Data Engineer

Data Engineer - Minerva - Contract - SC Clearance

Java Developer with SQL & GIT

Data Engineer

Devops Engineer - Perm (FTC) - Hybrid

Role - Devops Engineer

Industry - Automotive

Type - Fixed term contract (3 - 6 months)

Rate - £70,000 - £75,000 per annum, pro rata

Location - Hybrid, 50% of the month in the office (London, Victoria)

Spec -

Purpose

Hands-on DevOps Engineer with strong experience in Azure infrastructure and Terraform to enhance, automate, and support a cloud-native data platform. This hybrid role will be responsible for advancing our Infrastructure as Code (IaC) strategy for Azure Synapse, Blob Storage, and surrounding services while enabling secure, monitored, and scalable environments.
You will work alongside platform engineers, data engineers, and application teams to streamline infrastructure provisioning, enhance DevOps pipelines, and support deployment processes for integration components Skills

Terraform (Azure Provider) - solid hands-on experience with modules, state handling, and environment design.
Azure Synapse Analytics - workspace setup, pipeline orchestration, data movement components.
Azure Blob Storage - configuration, access control, and integration.
Azure AD / Entra ID - external user setup, access roles, security groups.
Comfortable with cloud-hosted app deployment integrations (e.g., C#, Blazor).
Good familiarity with SQL Server environments.
DevOps & Automation
Experience with CI/CD pipelines in Azure DevOps.
Familiarity with YAML pipelines and automated release workflows.
Exposure to monitoring tools (Azure Monitor, Log Analytics, or third-party)
Experience with secure data movement and scheduled refresh automation (e.g., via Synapse Triggers, Azure Automation).
Awareness of cost-optimization, telemetry, and observability best practices in Azure environments.

Preferred Qualifications

Microsoft Certifications: AZ-400 (DevOps), AZ-104 (Admin), or equivalent.

Main Duties

Infrastructure & Platform Automation
Extend and improve Terraform-based infrastructure automation for:
Azure Synapse: Workspaces, SQL Pools, Pipelines, Linked Services, Triggers.
Azure Blob Storage: Containers, lifecycle rules, access policies, secure access patterns.
Azure Web Apps and additional cloud services where needed.
Maintain and enhance IaC for RBAC, Entra ID (Azure AD), and secure external access.
Support flexible deployments and environment replication across dev/test/prod.
DevOps & Deployment Automation
Build and maintain CI/CD pipelines using Azure DevOps for infrastructure and application deployment.
Ensure consistent provisioning of environments using pipelines and IaC.
Support integration of cloud-hosted apps (e.g., C# / Blazor front-ends) into provisioned infrastructure.
Coordinate deployment of pre-scripted T-SQL objects .
Identity & Security Configuration
Manage secure access for internal and external users using Azure AD / Entra ID B2B.
Automate setup of roles, groups, linked services, and data access for services like SQL DB, Blob Storage, SFTP.

GCS is acting as an Employment Agency in relation to this vacancy

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 Data Engineering Tools Do You Need to Know to Get a Data Engineering Job?

If you’re aiming for a career in data engineering, it can feel like you’re staring at a never-ending list of tools and technologies — SQL, Python, Spark, Kafka, Airflow, dbt, Snowflake, Redshift, Terraform, Kubernetes, and the list goes on. Scroll job boards and LinkedIn, and it’s easy to conclude that unless you have experience with every modern tool in the data stack, you won’t even get a callback. Here’s the honest truth most data engineering hiring managers will quietly agree with: 👉 They don’t hire you because you know every tool — they hire you because you can solve real data problems with the tools you know. Tools matter. But only in service of outcomes. Jobs are won by candidates who know why a technology is used, when to use it, and how to explain their decisions. So how many data engineering tools do you actually need to know to get a job? For most job seekers, the answer is far fewer than you think — but you do need them in the right combination and order. This article breaks down what employers really expect, which tools are core, which are role-specific, and how to focus your learning so you look capable and employable rather than overwhelmed.

What Hiring Managers Look for First in Data Engineering Job Applications (UK Guide)

If you’re applying for data engineering jobs in the UK, the first thing to understand is this: Hiring managers don’t read every word of your CV. They scan it. They look for signals of relevance, credibility, delivery and collaboration — and if they don’t see the right signals quickly, your application may never get a second look. In data engineering, hiring managers are especially focused on whether you can build and operate reliable, scalable data systems, handle real-world data challenges and work effectively with analytics, BI, data science and engineering teams. This guide breaks down exactly what they look at first in your application — and how to shape your CV, portfolio and cover letter so you stand out.

The Skills Gap in Data Engineering Jobs: What Universities Aren’t Teaching

Data engineering has quietly become one of the most critical roles in the modern technology stack. While data science and AI often receive the spotlight, data engineers are the professionals who design, build and maintain the systems that make data usable at scale. Across the UK, demand for data engineers continues to rise. Organisations in finance, retail, healthcare, government, media and technology all report difficulty hiring candidates with the right skills. Salaries remain strong, and experienced professionals are in short supply. Yet despite this demand, many graduates with degrees in computer science, data science or related disciplines struggle to secure data engineering roles. The reason is not academic ability. It is a persistent skills gap between university education and real-world data engineering work. This article explores that 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 successful careers in data engineering.