Head of Data

Birmingham
1 month ago
Applications closed

Related Jobs

View all jobs

Head of Data, Pricing and Commercial Analytics

Head of Data – London – Messy Data / Web Crawlers / Data Aggregation

Head of Data Science

Lead Data/Head of Data Engineer

Data Engineer (18 Months FTC)

Data Science Manager – Property Tech – London

Head of Data

Location: Birmingham (Hybrid - 2 days per week onsite)
Salary: Up to £110,000 + benefits

Overview

I'm supporting one of my clients in the search for a Head of Data to lead and mature their end‑to‑end data function. This is a pivotal hire for a business investing heavily in its data strategy, technology, and people.

The successful candidate will be responsible for setting the data vision, providing technical leadership across Microsoft Fabric and Azure, and managing a multi‑disciplinary team consisting of data engineers, a data architect, data scientists, and data analysts.

This role is perfect for someone who thrives on setting direction while still staying close to delivery, architecture, and technical decision‑making.

Key Responsibilities

Define and deliver the client's data strategy, vision, and roadmap.
Provide hands‑on technical leadership across Fabric, Azure, and modern data platforms.
Lead, mentor, and grow a multi‑skilled data team (engineers, architect, scientists, analysts).
Oversee the design and implementation of scalable data solutions across ingestion, modelling, governance, and analytics.
Embed best practice in engineering, architecture, DevOps, performance, and data governance.
Partner with senior business stakeholders to ensure data underpins strategic decision‑making.
Promote a data‑driven culture and champion data accessibility, literacy, and quality.
Own platform direction including architectural frameworks, cost management, and operational excellence.

Strong engineering background in Python, SQL, Spark.
Experience designing enterprise‑scale cloud data platforms and modern data architectures.Leadership

Proven experience leading a multi‑disciplinary data team.
Ability to set strategic direction while staying technically engaged.
Strong stakeholder and senior‑level communication capability.
Experience developing frameworks for data governance, quality, security, and lineage.

Preferred Background

Experience working in a data‑mature or cloud‑native environment.
Familiarity with analytics, machine learning pipelines, and BI/visualisation tooling.
Experience with self‑service analytics and semantic modelling.

What's on Offer

Salary up to £110,000
Hybrid working model: 2 days per week in Birmingham
High autonomy and the opportunity to shape an organisation‑wide data function
A modern tech stack (Fabric + Azure) with strong investment and executive support
Discretionary bonus
And much more

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

If you’re pursuing a career in robotics, it can feel like the list of tools you should learn never ends. One job advert asks for ROS, another mentions Gazebo, another wants experience with Python, Linux, C++, RobotStudio, MATLAB/Simulink, perception stacks, control frameworks, real-time OS, vision libraries — and that’s just scratching the surface. With so many frameworks, languages and platforms, it’s no wonder robotics job seekers feel overwhelmed. But here’s the honest truth most recruiters won’t say explicitly: 👉 They don’t hire you because you know every tool — they hire you because you can apply the right tools to solve real robotics problems reliably and explain your reasoning clearly. Tools matter — but only in service of outcomes. So the real question isn’t how many tools you should know, but which tools you should master and why. For most robotics roles, the answer is significantly fewer — and far more focused — than you might assume. 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, confident, and ready to contribute from day one.

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

Robotics is one of the most dynamic, interdisciplinary fields in technology — blending mechanical systems, embedded software, controls, perception (AI/vision), modelling, simulation and systems integration. Hiring managers in this space are highly selective because robotics teams need people who can solve real-world problems under constraints, work across disciplines, and deliver safe, reliable systems. And here’s the reality: hiring managers do not read every word of your CV. Like in many tech domains, they scan quickly — often forming a judgement in the first 10–20 seconds. In robotics, those first signals are especially important because the work is complex and there’s a wide range of candidate backgrounds. This guide unpacks exactly what hiring managers look for first in robotics applications and how to optimise your CV, portfolio and cover letter so you stand out in the UK market.

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

Robotics is no longer confined to science fiction or isolated research labs. Today, robots perform critical tasks across manufacturing, healthcare, logistics, agriculture, defence, hospitality and even education. In the UK, businesses are embracing automation to improve productivity, reduce costs and tackle labour shortages. Yet despite strong interest and a growing number of university programmes in robotics, many employers report a persistent problem: graduates are not job-ready for real-world robotics roles. This is not a question of intelligence or dedication. It is a widening skills gap between what universities teach and what employers actually need in robotics jobs. In this article, we’ll explore that gap in depth — what universities do well, where their programmes often fall short, why the disconnect exists, what employers really want, and how you can bridge the divide to build a thriving career in robotics.