<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Product Owner - Head Resourcing RSS Feed</title>
    <link>https://jobs.co.uk/job/product-owner-head-resourcing--6e15e8fc-8b47-4cdd-b716-2a9ca9372b65</link>
    <description>RSS feed for Product Owner at Head Resourcing.</description>
    <language>en-gb</language>
    <lastBuildDate>Wed, 29 Apr 2026 22:56:04 GMT</lastBuildDate>
    <item>
      <title>Product Owner - Head Resourcing</title>
      <link>https://jobs.co.uk/job/product-owner-head-resourcing--6e15e8fc-8b47-4cdd-b716-2a9ca9372b65</link>
      <guid>https://jobs.co.uk/job/product-owner-head-resourcing--6e15e8fc-8b47-4cdd-b716-2a9ca9372b65</guid>
      <pubDate>Tue, 21 Apr 2026 23:00:00 GMT</pubDate>
      <description>Location: Edinburgh | Salary: &amp;pound;55000 - &amp;pound;65000/annum Amazing package | Type: Permanent | Product Owner - Rewards, Fulfilment &amp; Core Platform    Edinburgh (onsite 3 days)   No sponsorship provided sadly   I''m recruiting for a  purpose?driven tech?for?good  local Edinburgh organisation with truly Global impact using technology to create genuine social impact at scale. This is a brilliant opportunity for a  Product Owner who loves complex back?end platforms  and wants their work to  mean something .  This role sits at the heart of a mission?led product organisation, owning the  systems that power prize catalogues, fulfilment and end?to?end operational journeys . The technology matters - but so does the outcome.   The opportunity    This is a  proper platform Product Owner role . You''ll take ownership of the  back?end prize catalogue and fulfilment capability  that underpins how rewards are created, managed, distributed and fulfilled - end to end.  You''ll be trusted to solve real operational problems, design scalable systems, and ensure complex journeys work reliably for customers, partners and internal teams alike.  If you enjoy making  messy, real?world processes elegant and robust , you''ll feel at home here.   What you''ll be responsible for    Owning the  back?end ...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>