Senior C# Software Engineer – London

Our Story Hello there. We’re Zopa. We started our journey back in 2005, building the first ever peer-to-peer lending company. Fast forward to 2020 and we launched Zopa Bank. A bank that listens to what our customers don’t like about finance and does the opposite. We’re redefining what it feels like to work in finance. Our vision for a new era of banking puts people front and centre — we’ve built a business that empowers everyone to aim high, every day, to move finance forward. Find out more about our fantastic offerings at Zopa.com ! We’re incredibly proud of our achievements and none of it would be possible without the amazing team here. It’s not just industry awards we’re winning, we’ve also been named in the top three UK’s Most Loved Workplaces. If you embrace unconventional challenges, are unafraid to think differently and are driven to make an outsized impact, you’ll thrive here at Zopa, so join us, and make it count. Want to see us in action? Follow us on Instagram @zopalife The engineering challenge You will design and evolve the services that power core banking products. The systems you help build process thousands of financial transactions every day. They must be scalable, resilient and secure. When money moves, it has to work. Every time. But this role goes beyond implementation. You will shape technical direction. Influence cross-team initiatives. Own complex, high-impact work from concept through to production. You will help decide not just how we build, but what we build and why. This is senior in impact, not just title. We’re growing across several of our product-engineering tribes at Zopa, with current opportunities in Current Accounts, Lending, Credit Cards and Product Enablement . We care deeply about great engineering, which is why our core stack is Kotlin, running on a modern platform with Kafka, Kubernetes, Docker and AWS Aurora Postgres. But great engineers aren’t defined by a single language which is why we are agnostic with our hiring. We want the right people, not the 'right' language, so if you come from a C#/.NET background, bring solid fundamentals, and have an appetite for learning something new, we’ll invest in you, help you grow your skills and confidently step into our Kotlin ecosystem. Your impact: Owning complex initiatives end to end, from idea to measurable outcome Designing scalable backend systems that stand up to real-world scale and complexity Making architectural decisions that balance immediate delivery with long-term sustainability Bringing structure and clarity to ambiguous problems Influencing prioritisation and trade-offs across teams Raising the bar for engineering quality, reliability and accountability Mentoring engineers and strengthening overall team capability Driving continuous improvement in how we build and operate systems Your toolkit: You'll work with C#, Kafka, Kubernetes, Docker, AWS Aurora Postgres, and other modern technologies. If you haven't worked with all of these, we value skilled engineers with a willingness to learn. A track record of delivering high-impact, complex systems in production environments Strong testing discipline, with a commitment to strictly following Test-Driven Development (TDD) Strong systems thinking and architectural judgement The ability to navigate ambiguity and turn complexity into clear, actionable plans Confidence making data-informed technical decisions with long-term consequences in mind Experience influencing beyond your immediate team A deep customer focus and a bias toward measurable outcomes Experience mentoring others and amplifying team impact Ownership beyond your own output We’ll support your transition and cross-training into a JVM/Kotlin environment. What matters most to us is how you think, how you approach problem-solving, and the scale and impact of what you’ve built. Our engineering culture: Customer impact over unnecessary complexity Team success over individual heroics Operational ownership, not just feature delivery Continuous improvement through honest feedback Added bonus: Experience with fintech or banking is a plus, but we value problem-solvers from all backgrounds At Zopa we value flexible ways of working. We value face-to-face collaboration and a good work-life balance. This hybrid role requires you to come to our London office 2-3 days a week. You'll also have the option of working from abroad for up to 120 days a year!* But no matter where you are, we’ll make sure you’ve got everything you need to thrive, both in your work and home life, from day one. *Subject to having the right to work in the country of choice Diversity Statement Zopa is proud to offer a workplace free from discrimination. Diversity of experience, perspectives, and backgrounds leads to better products for our customers and a unique company culture for our people. We are made up of nearly 50 nationalities, have a DE&I forum made up of Zopians wanting to make a difference and we are proud of our culture where everyone can bring their full self to work. Our approach to DE&I is reflected in our hiring process so please let us know if you require any reasonable adjustments. Our approach to AI in interviews At Zopa, AI isn't something we're testing out — it's part of how we work every day. As a proud partner of Jobs 2030 , we're committed to building AI fluency across our workforce, and we expect Zopians to use AI as part of how they do their jobs. Because of that, we want to be transparent about how we think about AI use during our hiring process. Behavioural and competency-based interviews : please don't use AI . These conversations are designed to understand you — your experiences, your judgment, and how you've approached real situations. An AI-generated answer can't tell us that. What it can do is get in the way of us finding out whether we're the right fit for each other. Technical interviews: it depends on the role. Some technical stages actively welcome AI use, others don't. Your Talent Partner will let you know what's expected at each stage. Where AI is part of the assessment, we'll be interested not just in the outcome, but in how you used it – the tools you chose, your reasoning, and the decisions you made along the way.