I applied through an employee referral. The process took 2 weeks.
I had an initial call with an internal recruiter, followed by a first-round interview with a backend engineer. Unfortunately, the engineer seemed largely disinterested from the start. He remarked that he "hoped I prepared" for the interview, asked that I keep my questions at the end to a minimum due to time constraints, and requested that I focus on just one project from my previous experience for all parts of the interview to save time. Thankfully, as I began discussing my experience, the tone of the conversation shifted and the interaction became more pleasant. That said, the interviewer still posed a few puzzling questions—such as asking, "Wouldn’t you prefer to write real code?"—in reference to work I had done using Temporal.
Ultimately, I was not selected to move on to the next round. The feedback I received indicated that the project I spoke about did not demonstrate the specific experience the role required, despite it being within the financial services domain. In hindsight, I should have pushed to highlight a second project that may have aligned more closely with the expectations, though it felt as though a decision may have already been made.
Talk about a recent project you've worked on.
The following metrics were computed from 25 interview experiences for the Monzo Backend Engineer role in London, United Kingdom.
Monzo's interview process for their Backend Engineer roles in London, the United Kingdom is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Monzo's Backend Engineer interview process in London, United Kingdom.