Technology

A good response process can mean the difference between something being resolved in minutes and an issue developing into something worse!

The technology we use to create Monzo can play a key part in our mission to make money work for everyone.

We encountered an interesting bug in our Android app notifications. Here's how we fixed it.

Click to read more

Some bank transfers aren't working. We're working on sorting it out asap.

We moved our remote procedure call (RPC) service mesh from Linkerd to Envoy to make Monzo faster.

OpenVPN is great, but there were some things we wanted to change.

We’ve built bespoke software from scratch, that helps us manage chats in the app. Here's how we implemented it on Android.

We prepared our systems for crowdfunding by shedding load, and built tools to help us monitor on the day.

More than 9,000 people opened their apps to invest in the first five minutes of crowdfunding. To make sure we were ready, we ran tests to simulate the extra load and upgraded our platform to cope with it.

We architected and built a scalable backend to support 36,000 investments.

We held an internal hackathon to improve some of the oldest code in the bank! Here’s why that’s good for our engineers and our customers.

A team of engineers are available 24/7/365 to respond when things go wrong. For other companies thinking about how to approach incidents, here’s how we do on-call at Monzo.

We use tools to monitor all our systems to make sure everything’s working as it should. Platform team lead Chris shares a technical insight into the way we monitor Monzo.

Backend Engineer James Routley explains the technical work we do to help you send payments to your contacts on Monzo.