Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Monzo Bank nel mese di lug 2019
Colloquio
Interview process:
1. An informal phone call with one of their recruiter to get to know each other, background, experience and motivations. Some useful information about the company, team and the interview process.
2. Code challenge. I was given a project partially implemented, with few bugs and some functional requirements. The goal is to take ownership of the project.
3. Phone call with one of their Android Engineer for a technical discussion about your project, decisions, improvements. Exchange of ideas or point of views on how to do things.
4. The final stage is an in-office interview in 3rounds of 1h each.
- technical android interview with 2 devs (question about real-world use cases and implementation details)
- product interview with UI/UX team
- general computer science knowledge with 2 backend engineers
Even if I didn't get an offer, the whole process was smooth and quick. The experience with the interviewers was professional but friendly and nice, never felt under pressure.
I had a final call with their recruiter to have feedback and have an opportunity to share thoughts about it. That was really appreciated. It doesn't happen so often to have such detailed discussion and feedback after so much time spent to get the job. A good sign Monzo is a good company to work for.
Ho presentato la mia candidatura online. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Monzo Bank
Colloquio
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 two 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.
Ho presentato la mia candidatura online. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Monzo Bank (Londra, Inghilterra) nel mese di set 2023
Colloquio
Excessively long process. A conding challenge with a very restrict timelime, two different techincal interviews and another "behavior" interview with some managers. Totaling 8 hours of interview. The techincal interviews went all right, the interviewers seemed focused, had good questions to make and provided valued feedback. The interview with the managers was terrible. Both seemed bored when I was talking and kept interruptming me. Usually this kind of non-techincal interview should fell like a conversation. The go/no-go was quickly given.
Domande di colloquio [1]
Domanda 1
The coding challenge is about fixing a project that has some unfinished features and bugs. The techincal interviews, the first is like a code view session. The second one they will ask you to draw an architecture of a feature, explaining how you would make some things work.
