<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Tech Lead (Golang, AWS) - Partnerscale RSS Feed</title>
    <link>https://jobs.co.uk/job/tech-lead-golang-aws-partnerscale--9fa5aa99-993d-4c44-9040-64cbce273870</link>
    <description>RSS feed for Tech Lead (Golang, AWS) at Partnerscale.</description>
    <language>en-gb</language>
    <lastBuildDate>Thu, 10 Sep 2026 03:22:35 GMT</lastBuildDate>
    <item>
      <title>Tech Lead (Golang, AWS) - Partnerscale</title>
      <link>https://jobs.co.uk/job/tech-lead-golang-aws-partnerscale--9fa5aa99-993d-4c44-9040-64cbce273870</link>
      <guid>https://jobs.co.uk/job/tech-lead-golang-aws-partnerscale--9fa5aa99-993d-4c44-9040-64cbce273870</guid>
      <pubDate>Wed, 09 Sep 2026 11:54:16 GMT</pubDate>
      <description>Location: Oxford | Salary: 70000.00-70000.00 Annual | Type: Permanent | Tech Lead (Golang, AWS) Fully remote (UK based) £70,000 to £80,000 plus 15 to 20% bonus and profit share Plenty of tech lead jobs turn out to be a meeting calendar with a job title attached. This one keeps you in the codebase and hands you the architecture at the same time. Connectivity is the business, and the platform is how its partners get to it and sell it on. It is written in Go. Other companies integrate with it, run their own customers through it and build revenue on top, so the decisions you make about how it is built are commercial ones as much as technical ones. It is also the part of the estate that has to stay up. You would set the technical direction and own the architecture calls, while still writing and reviewing code every week. Around that sits the rest of it: deciding what gets automated and what gets tested, keeping the documentation useful for the people outside engineering who rely on it, being the person the wider business asks when something backend needs answering, and bringing on the developers around you. You would work closely with Product and with the people who deal with partners day to day, so you hear what is actually needed rather than reading it of...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>