Lead Data Engineer

WRK digital
Leeds
3 days ago
Create job alert

Job Title: Data Team Lead / Lead Data Engineer


Reporting to: Chief Technology Officer


Salary: £75-90,000 + Excellent Benefits


Type: Full-Time, Permanent


WRK Digital is proud to partner exclusively with a well-known, high-profile organisation on a transformative data journey. This organisation are at the beginning of a significant transformation programme and are building their data capability from the ground up. This is a brand-new, foundational leadership role with the opportunity to define how data is governed, managed and leveraged across a growing, multi-division organisation.


The Opportunity

This is a rare greenfield leadership opportunity within a growing professional services organisation operating at significant scale.


The business supports:



  • ~3,000 organisations
  • ~5,000 end clients
  • Large volumes of sensitive, regulated data
  • Growth via both organic expansion and acquisition

The current data landscape is fragmented across legacy systems. Migration activity is already underway, including modernisation from legacy platforms to SQL and lift-and-shift initiatives from on‑premise infrastructure into Azure.


The objective is clear:


Create a single source of truth and position data as a core commercial driver of the business.


This role sits at the centre of that transformation.


Strategic Mandate

Data is not viewed as a reporting function - it is central to:



  • Driving measurable business performance
  • Unlocking cross‑sell opportunities across service lines
  • Supporting integration of acquired businesses
  • Enabling service expansion
  • Increasing enterprise value as part of a long‑term exit strategy

You will be responsible for building the scalable data foundation that underpins this ambition.


The Role

Reporting directly to the CTO and working closely with Heads of Department and Partners, you will lead the design and implementation of a Microsoft‑based Lakehouse architecture within Azure.


You will operate in a high‑ownership environment with a small, focused team and strong executive visibility.


This is both a strategic and hands‑on role.



  • Design and implement a greenfield Lakehouse architecture in Azure
  • Consolidate fragmented datasets into a unified data stack
  • Lead migration from legacy platforms into SQL
  • Support on‑premise to Azure migration initiatives
  • Build ingestion pipelines into the Lakehouse environment
  • Establish robust data modelling and engineering standards
  • Lay foundations for scalable integration of acquired entities

Success at this stage = a stable, scalable platform forming the single source of truth.


Business Enablement & Commercial Impact

Beyond architecture, you will:



  • Challenge stakeholders on how data is currently used
  • Identify commercial opportunity through modelling and analytics
  • Deliver rapid wins by injecting data into high‑impact areas
  • Define and embed measurable KPIs to run the business
  • Enable cross‑sell insight across specialisms
  • Provide clear, structured reporting to leadership and Partners

The expectation is visible, measurable commercial value, not theoretical transformation.


Automation & Operational Efficiency

This role is automation‑led rather than AI‑led.


You will:



  • Build dashboards and structured reporting frameworks
  • Embed workflow automation
  • Create data‑led operational oversight
  • Ensure performance metrics are measurable across all key functions

Everything should be measurable. Everything should drive value.


Leadership Profile

We are seeking a high‑drive, ambitious technical leader who wants ownership and stretch.


You will:



  • Be a self‑starting builder with strong delivery bias
  • Be comfortable engaging senior stakeholders and influencing Partners
  • Have the confidence to challenge legacy thinking
  • Thrive in a high‑accountability, high‑visibility role
  • Balance strategic thinking with hands‑on engineering

This is not a passive governance role. It requires energy, persuasion, and execution.


The Environment

  • Lakehouse architecture (greenfield build)
  • Ongoing legacy migration
  • MSP support on broader technology stack definition
  • Strong mentorship and oversight from CTO and senior leadership

What Success Looks Like

  • Migration milestones delivered on time
  • Standardised reporting across the business
  • Cross‑sell opportunities identified and monetised
  • Operational metrics embedded across functions
  • Workflow automation implemented
  • Clear commercial value demonstrably added

Why This Role Is Different

  • True greenfield ownership
  • Small team, high influence
  • Business‑critical mandate
  • Tangible impact on company valuation

This is an opportunity to build something that materially changes how a complex, growing professional services organisation operates.


#J-18808-Ljbffr

Related Jobs

View all jobs

Lead Data Engineer

Lead Data Engineer - Azure Synapse

Lead Data Engineer - Hadoop - Spark - Python

Lead Data/Head of Data Engineer

Lead Data Engineer

Lead Data Engineer

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

If you’re trying to break into data science — or progress your career — it can feel like you are drowning in names: Python, R, TensorFlow, PyTorch, SQL, Spark, AWS, Scikit-learn, Jupyter, Tableau, Power BI…the list just keeps going. With every job advert listing a different combination of tools, many applicants fall into a trap: they try to learn everything. The result? Long tool lists that sound impressive — but little depth to back them up. Here’s the straight-talk version most hiring managers won’t explicitly tell you: 👉 You don’t need to know every data science tool to get hired. 👉 You need to know the right ones — deeply — and know how to use them to solve real problems. Tools matter, but only in service of outcomes. So how many data science tools do you actually need to know to get a job? For most job seekers, the answer is not “27” — it’s more like 8–12, thoughtfully chosen and well understood. This guide explains what employers really value, which tools are core, which are role-specific, and how to focus your toolbox so your CV and interviews shine.

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

If you’re applying for data science roles in the UK, it’s crucial to understand what hiring managers focus on before they dive into your full CV. In competitive markets, recruiters and hiring managers often make their first decisions in the first 10–20 seconds of scanning an application — and in data science, there are specific signals they look for first. Data science isn’t just about coding or statistics — it’s about producing insights, shipping models, collaborating with teams, and solving real business problems. This guide helps you understand exactly what hiring managers look for first in data science applications — and how to structure your CV, portfolio and cover letter so you leap to the top of the shortlist.

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

Data science has become one of the most visible and sought-after careers in the UK technology market. From financial services and retail to healthcare, media, government and sport, organisations increasingly rely on data scientists to extract insight, guide decisions and build predictive models. Universities have responded quickly. Degrees in data science, analytics and artificial intelligence have expanded rapidly, and many computer science courses now include data-focused pathways. And yet, despite the volume of graduates entering the market, employers across the UK consistently report the same problem: Many data science candidates are not job-ready. Vacancies remain open. Hiring processes drag on. Candidates with impressive academic backgrounds fail interviews or struggle once hired. The issue is not intelligence or effort. It is a persistent skills gap between university education and real-world data science roles. This article explores that gap in depth: what universities teach well, what they often miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build successful careers in data science.