<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Senior Data Engineer - Protein Works RSS Feed</title>
    <link>https://jobs.co.uk/job/senior-data-engineer-protein-works--c86a3b18-6410-44f1-88ac-d21568819228</link>
    <description>RSS feed for Senior Data Engineer at Protein Works.</description>
    <language>en-gb</language>
    <lastBuildDate>Tue, 14 Jul 2026 17:08:48 GMT</lastBuildDate>
    <item>
      <title>Senior Data Engineer - Protein Works</title>
      <link>https://jobs.co.uk/job/senior-data-engineer-protein-works--c86a3b18-6410-44f1-88ac-d21568819228</link>
      <guid>https://jobs.co.uk/job/senior-data-engineer-protein-works--c86a3b18-6410-44f1-88ac-d21568819228</guid>
      <pubDate>Tue, 14 Jul 2026 11:52:20 GMT</pubDate>
      <description>Location: Liverpool | Salary: 10000-500000 Annual | Type: Permanent | Data moves fast, and the businesses that win are the ones whose data can keep up with their ambition. That is the problem this role exists to solve, and it is a genuinely interesting one.As our Senior Data Engineer at Protein Works, you will be the person who owns the pipelines, the warehouse, and the data infrastructure that the rest of the business quietly depends on every single day. Not for the sake of a tidy architecture diagram, and not to build something impressive that nobody queries. For leverage: making decision-making across marketing, trading, operations and finance faster, more trustworthy, and more commercially effective by building infrastructure the business actually relies on.This role sits inside a growing and highly capable Business Intelligence team, at the heart of Protein Works'' AI transition. That means you will be laying clean, well-governed foundations that let AI workflows, agents, and analytical tooling deliver real value, not inheriting someone else''s half-finished setup. You will work across our Google Cloud data stack, connect APIs and pipelines into coherent systems, and take ownership of the full journey from initial brief through to a pipeline run...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>