Lead Data Engineer

Edinburgh
2 months ago
Applications closed

Related Jobs

View all jobs

Lead Data Engineer

Lead Data/Head of Data Engineer

Lead Data Platform Engineer | Remote | £85k + 4 day week

Lead Data Platform Engineer | Remote | £85k + 4 day week

Lead Data Platform Specialist | Remote | £85k + bonus

Lead Data & AI Scientist

I'm working with a world-class technology company in Edinburgh to help them find a Lead Data Engineer to join their team (hybrid working but there is flex on this for the right person). This is your chance to take the technical lead on complex, large-scale data projects that power real-world products used by millions of people. The organisation has been steadily growing for a number of years and have become a market leader in their field so it's genuinely a really exciting time to join!

You'll be joining a forward-thinking team that's passionate about doing things properly using a modern tech stack, cloud-first approach, and a genuine commitment to engineering excellence. As Lead Data Engineer, you'll be hands-on in designing and building scalable data platforms and pipelines that enable advanced analytics, machine learning, and business-critical insights. You'll shape the technical vision, set best practices, and make key architectural decisions that define how data flows across the organisation.

You won't be working in isolation either as collaboration is at the heart of this role. You'll work closely with engineers, product managers, and data scientists to turn ideas into high-performing, production-ready systems. You'll also play a big part in mentoring others, driving standards across the team, and influencing the overall data strategy.

The ideal person for this role will have a strong background in data engineering, with experience building modern data solutions using technologies like Kafka, Spark, Databricks, dbt, and Airflow. You'll know your way around cloud platforms (AWS, GCP, or Azure) and be confident coding in Python, Java, or Scala. Most importantly, you'll understand what it takes to design data systems that are scalable, reliable and built for the long haul.

In return, they are offering a competitive salary (happy to discuss prior to application), great benefits which includes uncapped holidays and multiple bonuses! Their office in central Edinburgh is only a short walk from Haymarket train station. The role is Hybrid (ideally 1 or 2 days in office), however, they can be flex on this for the right candidate.

If you're ready to step into a role where your technical leadership will have a visible impact and where you can build data systems that continue to scale then please apply or contact Matthew MacAlpine at Cathcart Technology.

Cathcart Technology 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 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.