Find a job 
Featured Companies 
Featured Universities 
For Companies At a Glance
- Tasks: Lead the transformation of data architecture and build a high-performing team.
- Company: Global branded entertainment business with a focus on innovation.
- Benefits: Competitive salary, 20% bonus, hybrid working, and leadership visibility.
- Other info: Opportunity to influence company culture and work with senior stakeholders.
- Why this job: Shape the future of data in a pivotal role with real ownership.
- Qualifications: 5-8 years in data engineering, leadership experience, and expertise in Databricks and Azure.
The predicted salary is between 120000 - 120000 £ per year.
We're working with a global branded entertainment business, operating across multiple international markets, to find a Principal Data Engineer who will shape the future of their data estate. This is a genuine player-coach role at a pivotal moment. The business is mid-transformation, moving from a legacy environment to a modern, cloud-native platform built on Databricks and Azure. You'll define the architecture, drive execution, build the team, and set the technical culture from the ground up. You'll be the technical face of data to the business: sitting with senior stakeholders, translating complex trade-offs into plain language, and holding the line on what gets built right versus what gets fixed fast.
Responsibilities:
- Define the directional architecture for the new data estate, including Lakehouse, Medallion and Eventing patterns on Databricks and Azure
- Lead discovery of the legacy estate: identify what to kill, what to keep, and how to migrate without breaking continuity
- Line manage, hire and develop the Data Engineering squad, setting technical standards and team culture
- Implement modern engineering hygiene: CI/CD, automated testing, observability and FinOps
- Partner with the Data Delivery Lead to balance tactical fixes against strategic build
- Represent the data function in setting organisation-wide standards for coding, security and DevOps
Requirements:
- 5 to 8 years in data engineering or data architecture, with at least 3 years in a leadership position
- Expert-level Databricks, Azure and SQL/Python
- Proven track record of refactoring legacy estates onto modern platforms without breaking things
- GCP and BigQuery experience is a strong advantage
- High EQ, comfortable presenting to leadership and managing non-technical stakeholders
- A software engineering mindset, not a scripting one
Why apply:
- Real architectural ownership from day one, not inherited decisions
- A mandate to build the team and culture around you
- Visibility at VP and leadership level across a major international business
- Hybrid working from London
If you're a Principal Data Engineer who wants to lead something meaningful rather than maintain something inherited, this is worth a conversation. Apply below or reach out directly. Due to the high volume of applications, not all applicants will receive feedback.
Principal Data Engineer - employer: Formula.
Contact Detail:
Formula. Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land Principal Data Engineer -
✨Tip Number 1
Network like a pro! Reach out to your connections in the industry, especially those who work at companies you're interested in. A friendly chat can open doors and give you insider info on job openings.
✨Tip Number 2
Show off your skills! Create a portfolio or GitHub repository showcasing your projects, especially those involving Databricks and Azure. This gives potential employers a taste of what you can do beyond your CV.
✨Tip Number 3
Prepare for interviews by practising common questions and scenarios related to data engineering. Think about how you'd explain complex concepts in simple terms, just like you would with senior stakeholders.
✨Tip Number 4
Don't forget to apply through our website! It’s the best way to ensure your application gets seen. Plus, we love seeing candidates who are proactive about their job search.
We think you need these skills to ace Principal Data Engineer -
Some tips for your application 🫡
Tailor Your CV: Make sure your CV speaks directly to the role of Principal Data Engineer. Highlight your experience with Databricks, Azure, and any leadership roles you've held. We want to see how you’ve shaped data estates in the past!
Craft a Compelling Cover Letter: Your cover letter is your chance to shine! Use it to explain why you're passionate about this role and how your skills align with our needs. We love seeing genuine enthusiasm for the position and the company.
Showcase Your Technical Skills: Don’t just list your technical skills; demonstrate them! Include specific examples of projects where you’ve implemented CI/CD, automated testing, or worked with legacy systems. We’re looking for real-world applications of your expertise.
Apply Through Our Website: We encourage you to apply through our website for the best chance of being noticed. It helps us keep track of applications and ensures you’re considered for the role. Plus, it’s super easy!
How to prepare for a job interview at Formula.
✨Know Your Tech Inside Out
Make sure you’re well-versed in Databricks, Azure, and SQL/Python. Brush up on your knowledge of Lakehouse and Medallion patterns, as well as eventing strategies. Being able to discuss these topics confidently will show that you’re the right fit for shaping the future data estate.
✨Showcase Your Leadership Skills
Prepare examples of how you've successfully led a team or project in the past. Highlight your experience in managing a data engineering squad and setting technical standards. This role is about building a culture, so demonstrating your leadership style will be key.
✨Translate Complexity into Simplicity
Practice explaining complex technical concepts in plain language. You’ll need to communicate effectively with senior stakeholders who may not have a technical background. Being able to simplify trade-offs will set you apart as a candidate who can bridge the gap between tech and business.
✨Emphasise Your Problem-Solving Mindset
Be ready to discuss how you've tackled challenges in refactoring legacy systems onto modern platforms. Share specific examples where you balanced tactical fixes with strategic builds. This will demonstrate your ability to think critically and act decisively in a transformative environment.