<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Data Engineer - Fyre Global Ltd RSS Feed</title>
    <link>https://jobs.co.uk/job/data-engineer-fyre-global-ltd--076350a5-4500-4831-8c42-113c01235256</link>
    <description>RSS feed for Data Engineer at Fyre Global Ltd.</description>
    <language>en-gb</language>
    <lastBuildDate>Wed, 02 Sep 2026 18:31:45 GMT</lastBuildDate>
    <item>
      <title>Data Engineer - Fyre Global Ltd</title>
      <link>https://jobs.co.uk/job/data-engineer-fyre-global-ltd--076350a5-4500-4831-8c42-113c01235256</link>
      <guid>https://jobs.co.uk/job/data-engineer-fyre-global-ltd--076350a5-4500-4831-8c42-113c01235256</guid>
      <pubDate>Wed, 02 Sep 2026 11:52:34 GMT</pubDate>
      <description>Location: City | Salary: 550.00-550.00 Daily | Type: Contract | 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.   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 find   Owning the migration approach - schema mapping, reconciliation, cutover planning   Working with Fabric''s Lakehouse/OneLake setup, not just theorising about it   Handling API-based ingestion where native connectors don''t cut it   Making real architecture calls, largely unsupervised   Working 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-negotiable   Proven migration methodology, from any ...</description>
      <category>Contract</category>
    </item>
  </channel>
</rss>