Tech Lead / Lead Data Engineer - Outside IR35 - SC + NPPV3 Cleared

Newington, Greater London
1 month ago
Applications closed

Related Jobs

View all jobs

Senior/Lead Data Engineer

Lead Data Engineer

Lead Data Engineer

Lead Data Engineer

Data Engineer

Data Engineer

Tech Lead / Lead Data Engineer (AWS Data Platform)
Rate: £500 - £550 p/d outside IR35
Length: 1st April to end of November (initially)
Location: London (hybrid – typically 1 day per week on-site, remaining remote)
Security Clearance: SC Clearance essential + NPPV3

Overview
We’re looking for a hands-on Tech Lead to lead a small team delivering secure, scalable data solutions within a highly regulated environment. You’ll take technical ownership across an AWS-based data platform using S3, Glue, and Redshift, working closely with delivery leadership, architecture stakeholders, and product teams to deliver incremental value.

This role suits someone who can balance technical leadership, hands-on engineering, and stakeholder-facing communication, while maintaining strong standards around security, quality, and operational resilience.

Key Responsibilities
Lead and mentor a small engineering team across data engineering, analytics engineering, and DevOps.
Own the technical design of data ingestion, transformation, storage, and access patterns.
Drive engineering standards including code quality, testing, CI/CD, Infrastructure as Code, and security-by-design.
Translate high-level requirements into solution increments, technical designs, and well-scoped delivery tickets.
Deliver and optimise data modelling approaches (e.g., star/snowflake schemas) and performance tuning practices.
Build reliable and cost-effective ETL/ELT pipelines, including orchestration and event-driven patterns where appropriate.
Partner with security stakeholders to ensure compliance, including IAM least privilege, encryption, auditability, and secure access controls.
Implement and maintain CI/CD pipelines for data workflows and platform components.
Ensure strong monitoring and operational discipline using cloud-native tooling and engineering best practice.
Communicate technical decisions, trade-offs, risks, and delivery progress to senior stakeholders.
Promote a culture of learning, quality, and continuous improvement.Required Skills & Experience
Proven experience as a Tech Lead / Lead Data Engineer delivering AWS-based data platforms.
Strong hands-on AWS experience, including:

Amazon S3 (data lake patterns, partitioning, lifecycle policies, cost optimisation)
AWS Glue (Jobs, Crawlers, PySpark, Glue Data Catalog, orchestration)
Amazon Redshift (performance tuning, sort/dist keys, Spectrum, WLM)
Strong development skills across:

Python (including PySpark)
SQL (DDL/DML, analytical queries, data performance considerations)
Experience with Infrastructure as Code (Terraform or CloudFormation).
CI/CD experience using tools such as GitHub Actions, Azure DevOps, CodePipeline, CodeBuild, etc.
Strong understanding of security & governance in regulated environments:

IAM, KMS encryption, Secrets Manager/SSM, audit logging
Delivery capability across Agile (Scrum/Kanban) environments with strong backlog refinement discipline.
Confident stakeholder management with the ability to explain technical choices and gain consensus

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.