<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Senior AWS Platform Engineer (AI Platform) - Sanderson RSS Feed</title>
    <link>https://jobs.co.uk/job/senior-aws-platform-engineer-ai-platform-sanderson--1879e25c-da68-4425-bf61-9ca5474d9d91</link>
    <description>RSS feed for Senior AWS Platform Engineer (AI Platform) at Sanderson.</description>
    <language>en-gb</language>
    <lastBuildDate>Sun, 30 Aug 2026 22:59:42 GMT</lastBuildDate>
    <item>
      <title>Senior AWS Platform Engineer (AI Platform) - Sanderson</title>
      <link>https://jobs.co.uk/job/senior-aws-platform-engineer-ai-platform-sanderson--1879e25c-da68-4425-bf61-9ca5474d9d91</link>
      <guid>https://jobs.co.uk/job/senior-aws-platform-engineer-ai-platform-sanderson--1879e25c-da68-4425-bf61-9ca5474d9d91</guid>
      <pubDate>Sat, 29 Aug 2026 11:52:56 GMT</pubDate>
      <description>Location: London | Salary: 10000-500000 Annual | Type: Permanent | Outside IR35 Contract: Senior AWS Platform Engineer (AI Platform)   Day Rate: Up to £600 Outside IR35 Location / Arrangement: Up to 3 Days per Week in office - either Bristol or London office Duration: 6 Months with the intention to further extend - long term greenfield programme   Our client is a FTSE100 Investment Management firm, we are seeking a AWS Platform Engineer to support on a £ multi-million greenfield AI platform build out with the long-term goal of DevOps automation.  As a Senior Platform Engineer, you''ll own the foundations our engineering teams build on. This is a deep AWS role, you''ll be shaping the multi-account estate itself, not just deploying workloads into it and a growing part of it is building the platform capability that lets teams ship AI-enabled products safely and at scale.  About you:   Deep, hands-on AWS expertise at platform level. You''ve designed and built landing zones and multi-account environments from the ground up - account vending, SCPs, IAM/identity federation, VPC and hybrid networking, centralised logging, and guardrails - not just consumed them. For example, this role may not be suitable for someone whose AWS experience is shipping Lambda...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>