I applied online. The process took two weeks.
Rigorous, thorough, open, and friendly. There was one soft intro interview. It was open and clear, and it went well. There was one technical interview with an engineer. It also went well. The technical exercise wasn't complex, and my solution could have been a little more modern. I come from a PHP background, which perhaps wasn't the best suited language for the problem, but I chose to go with it due to time constraints on my end.
There was a technical exercise review meeting. Whilst my technical exercise was strong, well-written, and well-structured, this is where I was deemed not a suitable fit. I'm okay with this. I understand their feedback and get where they're coming from. I am slightly disappointed, as what they deemed was missing is actually part of my skill set, but I'd failed to demonstrate it, which is on me.
My only feedback would be that it would be nice if the pre-technical exercise interviewer was also the one who reviewed the technical exercise and carried out the meeting. I feel the first interviewer had a better understanding of my skill set. The second perhaps didn't, as they were focused only on a task I'd done in a few hours. Feedback regarding what they felt were my shortcomings was delivered on request in a polite and respectful manner. All in all, even though I didn't get the job, it was a good process.
Describe past experiences. Describe projects you'd work on and decisions made, why and how you'd improve upon them. Explain what you'd do, given more time, to improve the tech exercise.
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.