Please note: we get lots of successful applications for Backend Engineer, so there could be a delay in scheduling interviews from the initial stage right up until the final interviews. If you're invited to interview and you have any immediate time pressures, please let us know, as we'll always do our best to speed things up for you 😊
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 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 ourproduct roadmap public and give sneak peeks of features in our community forum. Our blog is a good place to learn even more about what we do!
Monzo works in project-based sprints in small, interdisciplinary teams
We’re still a relatively small company, with around 60 engineers out of roughly 300 people in total - and we have big ambitions. There are many interesting challenges ahead, and we're happy for people to move between teams or to specialise, whatever you prefer. As an engineer here you'd be able to work directly with anyone across the company, and we run regular knowledge-sharing sessions so you’ll learn heaps about everything from how banks work to effective communication.
At Monzo you will get to work with a lot of exciting new technology.
We rely heavily on the following tools and technologies:
Go to write our application code (there’s an excellent interactive Go tutorial here)
Cassandra for most persistent data storage
Kafka for our asynchronous message queue
Kubernetes and Docker to schedule and run our services (Oliver,our Head of Engineering, gave a great talk at KubeCon on how we use these technologies)
AWS for most of our infrastructure
React for internal web dashboards
We also have two physical datacenter sites with actual cables to connect to various third parties 
You should apply if:
the work we’re doing sounds exciting!
you want to be involved in building a product that you (andeveryone you know) use 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
you’re interested in distributed systems and writing resilient software
you have some experience with strongly-typed languages (Go,Java, C, Scala etc.).