This role is for a Staff Data Engineer in London (Hybrid) with a contract length of "unknown" and a pay rate of "unknown." Key skills include Python or Scala, Databricks, Apache Spark, and Kafka, with experience in data engineering and cloud environments required.Job Title: Team LeaderLocation: London - HybridAbout The Role: My client is looking for a Data Engineering Team Leader to join their growing data team. This is a hands‑on technical role with a small people‑management component. The ideal candidate will bring strong expertise in data engineering, experience with Python or Scala, and hands‑on work with Databricks, Apache Spark, and Kafka. You will lead by example, guiding a small team of engineers while contributing directly to the design and delivery of data solutions.Key ResponsibilitiesLead and mentor a small team of data engineers, fostering a collaborative and high‑performance culture.Design, build, and maintain scalable data pipelines and streaming solutions using Spark, Kafka, and Databricks.Write high quality, efficient, and maintainable code in Python or Scala.Collaborate with stakeholders to understand requirements and deliver reliable, high‑impact data solutions.Ensure best practices in coding, testing, version control, and CI/CD are followed across the team.Monitor and optimise data workflows for performance, scalability, and cost‑effectiveness.Support the professional development of team members, providing coaching and feedback.Key RequirementsProven background in data engineering, with strong knowledge of Python or Scala.Hands‑on experience with Databricks, Apache Spark, and Kafka.Strong understanding of distributed data processing and data pipeline design.Experience in building and optimising large‑scale data platforms in cloud environments.Excellent problem‑solving skills and a strong technical mindset.Previous experience mentoring or leading engineers is desirable, though this will be a small part of the role.Strong communication and collaboration skills, with the ability to work effectively with technical and non‑technical stakeholders. #J-18808-Ljbffr