I applied through a recruiter, and the process took two weeks.
I was contacted by a recruiter and set up a meeting with them. It wasn't entirely clear what the role or level was in the message, but it was clarified in the call. It turned out to be a role that wasn't advertised on their website. The call with the recruiter was more informal and just about my general experience. I was put forward for what they call their initial call, which is an in-depth conversation about prior work experience with a focus on technical details. They try to build their questions around what you explained you did in your job, but they generally revolve around software engineering concepts, just as they say in their preparation guide. This guide is very helpful; it outlines what they are looking for, which is something I have been left wondering in other interviews. I was rejected after the initial call the next business day (great timeline!) and received tailored and detailed feedback.
What problems could arise with the current implementation? This question was hinting at concurrency.
The following metrics were computed from 1 interview experience for the Monzo Engineer II role in London, England.
Monzo's interview process for their Engineer II roles in London, England is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Monzo's Engineer II interview process in London, England.