Technology

We want to explain exactly what our Senior Staff+ interview process entails to make it fair and transparent for all our applicants. This post explains what you should expect from each of our interviewing stages and how to prepare.

This blogs explains the process of building and iterating on credit insights. We give you insight into how we use research to build products that meet customer needs, both at the start of the product design process and on an ongoing basis.

Monzo Stand-in is able to process payments in the event of a major outage of the Primary Platform. Customers can continue to use their card and send or receive bank transfers as normal

At Monzo, we have a set of engineering principles which encapsulate what we value as an engineering organisation. We first wrote our engineering principles in 2018, and recently invested in updating them to better reflect where we are now

We built a completely separate backup banking infrastructure called Monzo Stand-in to add another layer of defence so customers can continue to use important services provided by us

At Monzo we’re trying to be an inclusive company that pushes boundaries in an attempt to reach our mission, to “Make money work for everyone”. We are taking steps to ensure everyone can us Monzo independently.

Monzo has a huge variety of data roles in our Borrowing team that contribute to developing our credit products. In this blog we tell you what Borrowing at Monzo is, how it fits into Monzo, what the types of roles we hire for, and how to apply.

Our Product Designer, Victoria, talks about her learnings from the course '100 Design Projects' she attended this year, including sprinkling your own personality in every project and making sure you reflect on your own creative process.

This blog explains why design and research is so impactful at Monzo. We explain how we give designers and researchers an abundance of autonomy to help make decisions, and why it makes our team an outlier for those who care about making a difference.

Monzo cares about inclusive hiring in engineering by doing things like advertising our salaries on our job ads, sharing our process transparently, and providing different options for doing different technical interview stages

We built our “unordered concurrent” subscription knowing that we could eventually extend it to support ordering in Kafka

Monzo runs almost 3,000 microservices to power everything. A core part of being able to run all these systems and features safely is rate limiting. In this blog post we describe how that gets us to doing what we call “distributed rate limiting.”

We built a system to define scheduled jobs that moves away from cron and adds support for timezones, better monitoring and a more delightful developer experience

This blog talks about how our Monzo US team revamped the signup process for customers by experimenting with signup funnel improvements, increasing the rate of completion by a massive 400%

We’ve got a lot of value from our microservices architecture (2,800 and counting!), but this architecture is not without its challenges. One of those challenges is how to make sweeping library changes across all those services.