Everyone at Monzo is very friendly and generally a pleasure to work with, and very willing to help others out. Something which is not necessarily the case across all tech companies.
There is overall a positive work culture, with software engineers well treated and respected.
Monzo has a very opinionated platform which is great for service uniformity and being able to dive into other teams code. It does however make the challenge of working on a product team somewhat less interesting and challenging, with many of what I would see the most interesting/challenging problems being owned by platform engineering teams. I personally really miss the 'true' full end to end ownership of services, that I experienced with previous employers.
I think Monzo as engineering organisation could do a better job of being more vocally self critical. I think this would be beneficial for Monzo and the engineering organisation itself. While pay is competitive - it doesn't match what is on offer at FAANG companies, though this is partly made up by relatively generous option grants. However, options aren't liquid unlike RSU's.
Give new joiners the choice of what team/product area they join. There should be some component of team matching - as Monzo is hiring across multiple engineering teams.
I applied online. The process took four weeks. It was a good interview process with many stages. I didn't get the final stage due to the role being filled, which is not surprising given the amount of people that apply there.
The process was long, but quite diligent, with quick communication from the recruiting team. The first was a typical recruiter screen. After that, there was a one-hour session with one of their developers, where I was asked to describe one of my pas
I applied through a recruiter. The process took four weeks. I saw a review which had the same generic rejection, so I thought I'd post. I had the initial past projects interview, and that went well with quick feedback. Then I moved on to the coding
I applied online. The process took four weeks. It was a good interview process with many stages. I didn't get the final stage due to the role being filled, which is not surprising given the amount of people that apply there.
The process was long, but quite diligent, with quick communication from the recruiting team. The first was a typical recruiter screen. After that, there was a one-hour session with one of their developers, where I was asked to describe one of my pas
I applied through a recruiter. The process took four weeks. I saw a review which had the same generic rejection, so I thought I'd post. I had the initial past projects interview, and that went well with quick feedback. Then I moved on to the coding