

Data Engineer (Microsoft Azure) – Contract – Outside IR35 – 1st July Start – Ref: 25035
⭐ - Featured Role | Apply direct with Data Freelance Hub
This role is for a Data Engineer (Microsoft Azure) on a 6-week contract, starting 1st July, with a pay rate of £400 per day. It requires strong SQL skills, ETL development experience in Azure, and familiarity with legacy system integrations. Remote work with occasional travel to Ipswich is expected.
🌎 - Country
United Kingdom
💱 - Currency
£ GBP
-
💰 - Day rate
400
-
🗓️ - Date discovered
June 12, 2025
🕒 - Project duration
More than 6 months
-
🏝️ - Location type
Remote
-
📄 - Contract type
Outside IR35
-
🔒 - Security clearance
Unknown
-
📍 - Location detailed
Ipswich, England, United Kingdom
-
🧠 - Skills detailed
#SQL Server #Azure #Synapse #Data Reconciliation #Data Engineering #"ETL (Extract #Transform #Load)" #Microsoft Azure #PHP #SQL (Structured Query Language) #Data Quality #Data Storage #Storage #ADF (Azure Data Factory) #Data Mapping #Azure Data Factory #Azure SQL #MySQL
Role description
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Job title: Data Engineer
IR35 Status: Outside IR35
Day Rate: £400 per day
Start date: Must be available to start 1st July for 6 weeks initially, then fractional
Location: Remote + some travel to Ipswich (as and when required)
Job Ref: 25035
Overview:
As part of the CLIENT strategic redevelopment programme, there is a requirement for a Senior Data Engineer to lead on data mapping, transformation, and synchronisation activities between the legacy Swift Internet-hosted database and a newly provisioned Azure-based solution.
The legacy system presents several data quality and structural challenges — for example, data relating to 'County' may be found in columns labelled 'Country'. Column naming conventions and data storage practices are inconsistent, and the schema is poorly documented.
To gain a complete understanding of the data model and its usage, the Data Engineer will need to:
• Review and interpret the existing PHP codebase to identify how data is handled, populated, and transformed within the application
• Work independently to assess the current data structure within the legacy SQL Server/MySQL database
• Design a clean, normalised target data model within Azure (e.g., Azure SQL or similar)
• Define a robust mapping and transformation approach
• Collaborate with CLIENT stakeholders to validate and sign off the proposed data model and transformation logic
Once approved, the engineer will transition to the implementation phase, including:
• Developing ETL pipelines using Azure-native tooling (e.g., Azure Data Factory or Synapse Pipelines)
• Establishing synchronisation between legacy and new systems
• Supporting delta updates and ensuring both systems remain aligned throughout the transition
• Assisting developers with ad hoc queries, transformation logic, and data reconciliation efforts
Delivery Timeline & Resource Commitment:
• Sprints 0–2 (Full Time): Discovery, schema review, mapping design, and ETL development (30 days)
• Sprints 3–11 (Part Time): Ongoing support for developer-led integration and data sync (reduced involvement) – max 2 days a week, please note there are 2 week gap weeks every 6 weeks.
Required Skills & Experience:
• Strong SQL knowledge (MySQL and/or SQL Server)
• Hands-on experience with data modelling and ETL development in Azure
• Proven ability to reverse-engineer data flows from code (specifically PHP-based applications)
• Experience collaborating with business stakeholders to define and validate data structures
• Understanding of legacy-modern system integrations and ongoing synchronisation challenges
Familiarity with Microsoft Azure’s data services (e.g., Azure SQL, Data Factory) is highly desirable.