DontApply.Club
Login Register

Contract Data Engineer - Snowflake to Microsoft Fabric Migration

Fyre Global — United Kingdom · Posted ~22 hours ago

Senior Contract Hybrid

Skills

Data engineering Snowflake Microsoft Fabric data migration schema mapping data reconciliation cutover planning Lakehouse OneLake API-based ingestion data architecture APIs

🔓 Log in to save this job, tailor your resume & track your apply process — 7 days free, no card needed.

Log in to add to target list

Summary ✨ AI‑Generated

A contract data engineering role focused on migrating a live analytics platform from one cloud data warehouse to a modern integrated analytics platform. You will define the migration approach, map schemas, reconcile data, plan cutover, work with lakehouse architecture and API ingestion, and make architecture decisions with substantial autonomy. The assignment is expected to last approximately six to nine months.

Highlights

Hands-on ownership of a major data platform migration, significant architectural responsibility, an initial scoping phase, hybrid working, and the opportunity to work with modern cloud analytics technologies alongside junior engineers.

Description

Contract Data Engineer - Snowflake to Fabric Migration - Outside IR35 Not another "maintain what's there" contract. A Manchester business is migrating a live, client-facing analytics platform off Snowflake and onto Microsoft Fabric - and they need someone who's actually done a migration before, not just read about Fabric. Exact contract duration tbc, but expected to be between 6-9 months (you'll know for sure after the initial scoping phase). This is a hybrid position, once a week in Manchester What you'll be doing Starting with a proper scoping phase - the first month is about uncovering the real shape of the work, and contract length will follow from what you findOwning the migration approach - schema mapping, reconciliation, cutover planningWorking with Fabric's Lakehouse/OneLake setup, not just theorising about itHandling API-based ingestion where native connectors don't cut itMaking real architecture calls, largely unsupervisedWorking alongside two junior engineers - some mentoring as you go, and a pair of extra hands for the time-consuming-but-doable work that shouldn't eat your time What matters Strong, hands-on Fabric experience - this is non-negotiableProven migration methodology, from any source systemHaving done a Snowflake-to-Fabric migration specifically is massively beneficial, even if not essentialComfortable building custom ingestion against vendor APIsConfidence to own the decisions, not wait to be toldComfortable being the senior voice in the room, including some light mentoring of junior team members If you've done this kind of move before and want to run it, not just support it, then this should be of interest