<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Lead Architect - Project People RSS Feed</title>
    <link>https://jobs.co.uk/job/lead-architect-project-people--a7e91b09-2f83-40d0-a079-49c3355a961b</link>
    <description>RSS feed for Lead Architect at Project People.</description>
    <language>en-gb</language>
    <lastBuildDate>Sun, 26 Apr 2026 02:57:16 GMT</lastBuildDate>
    <item>
      <title>Lead Architect - Project People</title>
      <link>https://jobs.co.uk/job/lead-architect-project-people--a7e91b09-2f83-40d0-a079-49c3355a961b</link>
      <guid>https://jobs.co.uk/job/lead-architect-project-people--a7e91b09-2f83-40d0-a079-49c3355a961b</guid>
      <pubDate>Thu, 02 Apr 2026 23:00:00 GMT</pubDate>
      <description>Location: Reading | Salary: Negotiable | Type: Permanent | Lead Architect    Reading - Hybrid working    Perm      The Lead Architect sits at the centre of MBNL''s technology ecosystem, providing architectural direction across business, enterprise, data, and technology domains. Reporting into the Head of Technology &amp; Information, this role ensures that MBNL''s systems and platforms are secure, compliant, future-ready, and aligned to business strategy.     Operating at senior level, you''ll influence investment choices, guide complex supplier-led delivery, and promote innovation across MBNL and its shareholder ecosystem-balancing today''s operational needs with tomorrow''s growth.      Why this role matters   Every major business outcome depends on technology working together, not in silos. This role ensures MBNL''s technology landscape remains coherent, resilient, and adaptable-supporting regulatory compliance today while enabling innovation tomorrow.  You''ll shape how choices are made, how suppliers deliver, and how technology investments translate into real business value for shareholders and customers alike.        What you''ll be here to do   You''ll be the architectural authority across MBNL-setting direction, enabling delivery, and ...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>