At Monzo we aim to build the best current account in the world. We are always keen to hear from capable, creative engineers who want to help us accomplish that goal.

Our backend engineers have a variety of different backgrounds: we have several non-graduates; only some of us studied Computer Science; one of the team has a degree in Marketing; some of us have worked in huge companies; some have only ever worked in startups; others are former consultants. As long as you enjoy learning new things, we’d love to talk to you.

We work in project-based sprints in interdisciplinary teams - as an engineer here you'd be able to work directly with anyone across the company, from customer support to compliance, product to financial crime, and we run regular knowledge-sharing sessions so you’ll learn heaps about everything from how banks work to effective communication.

We encourage an open and transparent working environment. You can get involved in any aspect of the business you are interested in and, following Stripe’s example, all emails in the company are visible in an email archive. We regularly run hackathons in which people build things on our third party API and we contribute to open source software as much as possible. We’ve also made our product roadmap public and give sneak peeks of features in our community forum.

If you’re unsure about applying or have any questions about the role or team, please don’t hesitate to email Ella directly 😊. We're very open about what we do in general, so our blog is a good place to learn more about what we do.

Our technology stack

At Monzo you will get to work with a lot of exciting new technology. We rely heavily on the following tools and technologies:

You should apply if:

  • the work we’re doing sounds exciting!
  • you want to be involved in building a product that you and everyone you know uses literally every day
  • you’re keen to learn more about new technologies and the arcane inner workings of the financial industry
  • you’re comfortable working in a team that deals with ambiguity every day
  • you’re interested in distributed systems and writing resilient software
  • you have some experience with strongly-typed languages (e.g. Go, Java, C, Scala…)

Teams at Monzo

We’re still a relatively small company, with around 50 engineers out of 210 people in total - and we have big ambitions. This means you'll be working on things that are central to our goals. There are many interesting challenges ahead, and we're happy for people to move between teams or to specialise, whatever you prefer. Monzo is organised into small, interdisciplinary teams (drawing heavy inspiration from how Spotify set up their teams), each able to independently solve the problems within their domain. At the moment, the following teams are looking for backend engineers:

Scaling Customer Operations

Monzo is a customer service company. In order to scale our current level of service to a billion users and beyond, we are investing heavily in building a state of the art workflow management system for all manual work in the company. We consider this to be our secret competitive advantage that is not really visible outside the company. You can read more about this team in this blog post (it is slightly out of date - the team making these tools used to be called "Internal Product")


Help us take Monzo’s data capabilities to the next level by building systems which allow us to explore massive data sets interactively and run machine learning models in real time on event streams, all whilst maintaining strong data integrity. If you are interested in how we think about data and analytics and would like to read more, take a look at this blog post.


Help us build a state-of-the-art microservices platform based on the learnings of Netflix, Twitter, and Google. We're investing a lot of up-front effort in building a scalable, secure, and extensible architecture. We've posted a good overview of our platform on our blog.


Help us write code that moves money. Between integrating with crufty old payment schemes, connecting to legacy systems from the 1970s, and designing our own core banking ledger, at Monzo we get to see how the financial sausage is made! If you were ever curious about how money flows through the financial systems or wanted to write code to move money in a safe way, this is your chance.


Over the first 9 months of 2017, we organically grew our userbase almost 5% week-over-week. This growth was the result of several new features we introduced under the umbrella of "Monzo with friends". The Growth team is a full-stack product engineering team that is responsible for building product features that drive growth.


Help us build product features such as spending reports, budgeting, receipt scanning, or targets that make the Monzo app more useful. Over 55% of people that sign up for a Monzo account still use it for financial transactions three months later. This number is what the Retention team is optimizing.


Our long term goal is to be more than just a bank - we want to become each user's financial control centre. The partnerships team is building integrations and product features that help our users save money or otherwise optimize their financial life. It is also the team that builds our third party developer API.


Help us build fair and transparent lending products. In the short term, our primary revenue stream comes from lending. We have written a blog post to give you an idea of what that looks like.

Financial Crime and Security

We do a lot of work around fraud and electronic crime, using a mix of machine learning models, discrete rules, human review, and clever product features to fight back. We've written about how we do that on our blog. You’d work closely with our Risk and Compliance team, analytics, customer support, and fraud investigators to make sure we’re doing everything we can to fight against financial crime.


We can help you relocate to London, we can sponsor visas, and we're open to remote working as long as you can spend around 20% of your time in London.  

We care deeply about inclusive working practices and diverse teams. If you’d prefer to work part-time or as a job-share, we’ll facilitate this wherever we can - whether to help you meet other commitments or to help you strike a great work-life balance.

Our interview process consists of an initial phone screen, a take-home code test, and a half-day on-site interview. We promise not to ask you any brain teasers or trick questions, and we won't make you code on a whiteboard!

We are continually looking for new backend engineers, but prefer to batch interviews when possible. If you are under time pressure to change jobs soon, please let us know by when you need a decision in your application.


Apply for this Job
* Required
File   X
File   X

Share this job: