I applied online. The process took two weeks.
After the initial call, I was asked to write a small Android application as a coding assignment. The assignment was very close to a real work situation where you inherit a half-done project from some other developer that is full of bugs and crashes and a design that is nowhere near finished. Your job is to fix the project and work your way towards the requested specs. You don't have a specific time deadline, and you can work on it up to four hours.
The on-site interview consisted of three one-hour-long interviews with different groups of the company. There is an Android, a Computer Science, and a Product section in this. The Android one asks some way of how you would implement a specific spec, and some RxJava questions. The team works very closely with RxJava, and even though it is not clear on the job description, you will be asked and scored on questions about the said framework. Focus on RxJava and talks the team has done in the past, and you'll be fine.
What is wrong in this RxJava pipeline?
The following metrics were computed from 2 interview experiences for the Monzo Android Engineer role in London, United Kingdom.
Monzo's interview process for their Android Engineer roles in London, the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Monzo's Android Engineer interview process in London, United Kingdom.