I applied online. The process took 2 weeks.
Avoid. The recruiter maintained good communication throughout the process, but the actual interviewer left me with some doubts. During the interview, the engineer asked me detailed questions about the architecture of the app I currently work on at my company. Surprisingly, they commented that my company's app seemed over-engineered. I found this surprising because I don't believe it relates to my potential role at Monzo. The architectural design of my company's app is primarily the responsibility of our principal and lead architect. I felt like I was being evaluated for the design choices of an app that predates my current role at the company.
Additionally, the interviewer mentioned that the example I provided was not challenging enough. In that example, I discussed taking ownership of a significant task that involved creating a component that had to work on two separate apps that support multiple international languages, each of which serve millions of users, with working on the backend development in TypeScript and front-end work in Kotlin. This included collaborating with multiple teams within a tight deadline, among other responsibilities.
Discuss a technical challenge you've faced.
The following metrics were computed from 4 interview experiences for the Monzo Android Engineer role.
Monzo's interview process for their Android Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Monzo's Android Engineer interview process.