<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Backend Engineer - Gold Group RSS Feed</title>
    <link>https://jobs.co.uk/job/backend-engineer-gold-group--5d6b9e23-4387-4de6-a649-0d4d9b169004</link>
    <description>RSS feed for Backend Engineer at Gold Group.</description>
    <language>en-gb</language>
    <lastBuildDate>Mon, 10 Aug 2026 20:46:19 GMT</lastBuildDate>
    <item>
      <title>Backend Engineer - Gold Group</title>
      <link>https://jobs.co.uk/job/backend-engineer-gold-group--5d6b9e23-4387-4de6-a649-0d4d9b169004</link>
      <guid>https://jobs.co.uk/job/backend-engineer-gold-group--5d6b9e23-4387-4de6-a649-0d4d9b169004</guid>
      <pubDate>Sun, 09 Aug 2026 23:00:00 GMT</pubDate>
      <description>Location: London | Salary: &amp;pound;50000 - &amp;pound;100000/annum Share options | Type: Permanent | Backend Engineer - Java / Kotlin / Spring Boot       London - Hybrid (1 day per week)   Up to -100,000 + Share Options   Unfortunately, sponsorship cannot be provided      I''m working with a growing technology startup looking to hire a  Backend Engineer  to join its engineering team in London.     They''re looking for someone who is genuinely strong technically - not just someone who has worked with the right technologies. You''ll be joining a small, high-performing team where you''ll have significant ownership over backend systems, contribute to architectural decisions and help shape how the platform develops as the business scales.      What they''re looking for   The core requirements are:   Strong,  recent commercial Java experience   Strong,  recent commercial Kotlin experience   Strong commercial  Spring Boot experience   Ideally  2+ years within a technology startup or scale-up   Experience working in smaller engineering teams where you''ve had genuine ownership  Strong understanding of backend architecture, APIs, databases and distributed systems  Ability to discuss technical decisions, architecture and trade-offs in depth  Comfortable taking a problem from initial require...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>