Get access to exclusive discount on Golang courses up to 25% off
Last developer joined
2-Click Apply
Upload Your CV
Go to your Inbox & Confirm Your Application
Backend Engineer, Security at Monzo - Remote / United Kingdom
Salary £40,000 to £100,000 a year Company Websitehttps://monzo.com Published December 2024 Applicants This Week 2
Job Description
At Monzo we’re aiming 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. We want our bank to be safe and secure for our customers, so security is very important to us
Security at Monzo
Monzo’s security team has a wide range of responsibilities, from infrastructure security to application security. As a bank, we are solving diverse, novel problems to ensure that our customers are safe and secure.
One of the guiding principles of security at Monzo is that security at the expense of user experience is a last resort. We aim to move mountains in the background such that we can build world-class features without compromising on security.
As a member of our security team you would be responsible for constantly improving the security of Monzo, and you would work closely with other teams to ensure that our systems are secure by design. Of course, security incidents can and do occur, and the security team is involved with many different types of incident response.
Our 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 our product 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!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. 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 have around 190 engineers out of roughly 1000 people in total - and we have big ambitions. As a security engineer here you'd be able to work directly with lots of teams 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
Linkerd/Finagle for RPC
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 (and everyone you know) use every day
you’re constantly looking for flaws in systems and can reason about how best to address them
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.).
Logistics
We can help you relocate to London, we can sponsor visas, and we're open to distributed working (as long as you can spend around 20% of your time in London).
We have payroll set up in five countries: the UK, Ireland, France, Poland and Spain. Right now, we can only hire people who work from those countries and we’ll keep this updated with new ones as we expand and are able to hire from more places 🌎
We offer competitive salaries based on skills and experience, which could be anywhere between £40,000 - £100,000 per year.
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 try our best to make this happen. Just let us know in your application so we can plan for it.
We're usually always hiring for Backend Engineers in Security, so there's no closing date for this job.
Our interview process is normally a phone interview, a coding task and call to discuss it, and 2-3 hours of onsite interviews. We promise not to ask you any brain teasers or trick questions. We might design a system together on a whiteboard, the same way we often work together, but we won’t make you write code on one
Questions about this role? Head over to our careers page to read our FAQs (www.monzo.com/careers)
Perks & Benefits
Stock Options
Salaries Reviewed every six months
Working from Home
Holiday
Unpaid holiday
Health insurance
Pensions
Maternity, Paternity and adoption leave
Catered lunch
Headspace subscription
Socials
Yoga and Pilates
Equipment
Cycle-to-work
Learning and training
Knowledge sharing
Library
Life Insurance
Interview Process
Our interview process is normally a phone interview, a coding task and call to discuss it, and 2-3 hours of onsite interviews. We promise not to ask you any brain teasers or trick questions. We might design a system together on a whiteboard, the same way we often work together, but we won’t make you write code on one