I applied online.
Two to three weeks after applying, I received an email saying that I would be a great fit for the role and was invited to a thirty-minute screening video call, which went well. After the screening interview, I received a take-home test to do, which was to write a web crawler in any language and with unlimited time. Given that I was unemployed, I spent a considerable amount of time on this to ensure it was perfect.
Next, I had a video call to go over my solution. It generally felt like a positive call, with the interviewer suggesting I had gone above what most candidates submit. A few days later, I received an email saying that I was not a good fit for the role, which was completely contradictory to my initial email. I asked for more feedback, and they said that I did not have the experience that they were looking for at this time. I am quite disappointed that they could not have figured this out from an initial CV screening and saved me the time and effort.
Don't waste your time applying if you don't have experience with at least a few of the technologies listed in the job description, as my background was in C.
The coding challenge was to write a Web Crawler in a language of your choice.
The following metrics were computed from 45 interview experiences for the Monzo Backend Engineer role.
Monzo's interview process for their Backend Engineer roles is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Monzo's Backend Engineer interview process.