I applied online. The process took two weeks.
There is a code test which involves inheriting a codebase full of bugs and issues to fix. It includes a design spec. You have two hours to fix bugs and implement a feature, nowhere near enough time to get anything done. I checkpointed my work at two hours and wrote out my rationale in the README, but continued to work on the project after that to finish implementing a feature.
During the interview to go over the code test, the interviewer was not happy in the slightest that I went over the two-hour time limit, even though I mentioned I'd checkpointed the commit in the README, and described all my decisions along with it up until that point. I had to explain twice that I wanted to show them the full feature implementation, as I had spent the two-hour time limit fixing bugs and improving the codebase.
I also noticed that the interviewer really did not want to be there, which felt quite anti-climactic to me for a company that I had admired as a customer for years. I was not given any feedback.
The questions included the internal behaviour of RecyclerView LayoutManagers and architectural questions. There were also questions such as: "What should your tests include?", "What would you do if you only had 10 hours to ship the whole product?", and "If you were a product manager, what should go into an MVP?"
The following metrics were computed from 1 interview experience for the Monzo Senior Android Engineer role in London, England.
Monzo's interview process for their Senior Android Engineer roles in London, England is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Monzo's Senior Android Engineer interview process in London, England.