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
About the team
We are a mobile-first bank, and our iOS app is a critical part of how customers experience Zopa.
Having recently completed our migration to fully native mobile, we are now focused on making our iOS platform exceptional: fast, reliable, accessible and easy for engineers to build on.
You’ll join our Mobile Platform team, which owns the shared capabilities that underpin the app, including architecture, shared modules, design system, observability, developer tooling and CI/CD.
The team’s role is not to own all technical decisions. It is to help shape the direction of mobile engineering at Zopa, create great developer experiences for our product teams, and make it easier for engineers to focus on customer problems rather than underlying technical complexity.
You’ll also be part of a strong iOS engineering community, contributing to standards, sharing knowledge and helping us continue to mature our native engineering practice.
A Day in the life:
Partner closely with the Engineering Manager, Principal Mobile Engineer and Head of Mobile Engineering to deliver Zopa’s mobile strategy.
Help shape the technical direction and standards for iOS across Zopa.
Design and evolve shared modules, APIs, architecture and developer tooling that enable multiple teams to build and ship with confidence.
Identify technical risks early, using data, profiling and observability to improve performance, reliability and developer experience.
Stay highly hands-on, delivering production-quality Swift and SwiftUI code across platform and customer-facing product work.
Raise the capability of other engineers through pairing, code reviews, technical discussions and knowledge sharing.
Work closely with Product, Design, Backend and Android colleagues to make well-rounded decisions, influence direction and respect each discipline’s expertise.
About you:
Strong experience building and maintaining customer-facing iOS applications using Swift and SwiftUI.
Deep knowledge of iOS development, including concurrency, performance, memory management, testing, accessibility and security.
Sound architectural and API-design judgement, with a focus on simple, maintainable solutions and an excellent developer experience.
A proactive engineer who identifies problems, shapes practical solutions and influences improvements beyond their immediate team.
A collaborative teammate who raises the capability of others through coaching, pairing and knowledge sharing.
Comfortable constructively challenging ideas, while remaining open-minded and willing to change course when better evidence emerges.
Genuine curiosity about mobile engineering and the evolving iOS platform.
Added bonus:
Background in fintech, banking or another regulated, high-trust environment where reliability and customer confidence matter.
A track record of building shared libraries, platform capabilities or design systems that help engineering teams move faster.
Strong hands-on knowledge of UIKit and its place within modern iOS development.
Proven impact improving mobile CI/CD pipelines, release processes and developer tooling.
Confidence using AI-assisted development tools thoughtfully to improve productivity and code quality.
#LI-IB1
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.
