Senior Software Development Engineer

GoCardless
London, UK£102k – £152kPosted 21 February 2026

Job Description

<div class="content-intro"><h3><strong>About Us at GoCardless</strong></h3> <p>GoCardless is a <strong>global bank payment</strong> company. Over <strong>100,000 businesses</strong>, from start-ups to household names, use GoCardless to collect and send payments through direct debit, real-time payments and open banking. </p> <p>GoCardless processes <strong>US$130bn+</strong> of payments annually, across <strong>30+ countries</strong>; helping customers collect and send both <strong>recurring</strong> and <strong>one-off payments</strong>, without the chasing, stress or expensive fees. We use AI-powered solutions to improve payment success and reduce fraud. And, with open banking connectivity to over <strong>2,500 banks</strong>, we help our customers make faster, more informed decisions.</p> <p>We are headquartered in the<strong> UK</strong> with offices in <strong>London</strong> and <strong>Leeds</strong>, and additional locations in <strong>Australia, France, Ireland, Latvia, Portugal</strong> and the <strong>United States.</strong></p> <p>At GoCardless, we're all about <strong>supporting you</strong>! We’re committed to making our hiring process <strong>inclusive</strong> and <strong>accessible</strong>. If you need extra support or adjustments, reach out to your <strong>Talent Partner</strong> — we’re here to help! </p> <p>And remember: we don’t expect you to meet every single requirement. If you’re excited by this role, <strong>we encourage you to apply!</strong></p></div><h3><strong>Engineering at GoCardless </strong></h3> <p>The technical challenges of building GoCardless span from simplifying building banking schemes to optimising the time to render the dashboard. </p> <p>You will enjoy being a software engineer at GoCardless if:</p> <ul> <li>You’re looking to champion a great engineering culture within GC and in the wider engineering community; </li> <li>You enjoy collaborating and learning from people from various backgrounds and experiences; </li> <li>You want to feel proud of the work you’re doing and its impact on real customers.</li> </ul> <p>Our engineers contribute to the engineering culture within and outside of GoCardless: they contribute to Open Source Software projects (see our<a href="http://github.com/gocardless"> Github</a>), and share learnings in<a href="https://gocardless.com/blog/service-outage-on-6-april-2018-post-mortem-results/"> post-mortems</a>, conferences and on<a href="https://gocardless.com/blog/debugging-the-postgres-query-planner/"> our blog</a>.</p> <p>Our technologies: We endeavour to build simple, reliable systems and we believe in using the best technologies for each task. Technologies we use across GoCardless include: Ruby on Rails, Golang, Python, JavaScript, TypeScript, React, Postgres, BigQuery, Kubernetes, Elasticsearch, Prometheus, Google Cloud (GCP).</p> <p>You’re not expected to have expertise in all these technologies. Members of our team have picked up the tools once they’ve started working with the team. If you’re unsure, please apply.</p> <p> </p> <h3><strong>About Payer Proposition</strong></h3> <p>We are a small, mighty and growing team that is responsible for developing GoCardless’ payer proposition, where we want to build and generate value from payer networks. </p> <p>GoCardless is used by tens of millions of payers each year, but so far we have done little to engage and build a relationship with them. Most still use our services without knowing. </p> <p>We want GoCardless to become the easiest, and most rewarding way for payers to pay. In turn we want to use the relationship we build with our payers to enhance our service for our merchants. This means you’ll be exploring areas as varied as whether we can improve our paying experience, to whether we should offer rewards and incentives for paying with GoCardless. </p> <p>This is a greenfield area for GoCardless, and will involve a high level of ambiguity, experimentation and cross-functional collaboration as we go on th ... (truncated, view full listing at source)