I applied online. The process took 4 weeks. I was really eager and excited to join Monzo after applying. I felt confident as my current role is very similar, as we use almost the exact same stack, we share similar employee benefits, and we work under agile methodologies. However, after getting the rejection email after only the phone screening process, now I feel shocked, my confidence is now shaken, and I just feel really low. The process took just over a month. Yes, over a month just to get a rejection email after the first hurdle, which was the screening interview. Their slow responses didn't bother me at the time. However, with hindsight, knowing the process was fruitless and that I didn't get the chance to prove myself with the technical test, it does leave me with a bitter taste in the mouth.

A few days before the video call, I was informed that the original role that I applied for had been taken down and instead they offered me an almost identical role or a senior vacancy. I chose the mid vacancy as I thought this would give me the best chance of getting the job. So this confirms that my interview was the sole reason why I didn't proceed further in the process, as initially they felt my skillset was also suited to senior roles. After selecting an interview slot, they emailed me with a few tips for the upcoming interview call. These were red herrings. They told me to make sure my CV was up-to-date as they were going to ask me questions regarding it. This was not true. Not one item on my CV was discussed apart from my current employer, which I brought up in conversation—not the interviewer—in relation to one of the technical questions. They also recommended that I look at their 2019 roadmap and their blog, both of which never came up in conversation.

My advice would be to revise your core JavaScript knowledge. All of their questions revolved around this. The interviewer style would be to ask you a question, await the answer, and then delve deeper and deeper until you hit a brick wall and cannot answer any longer. This happened twice in the 45-minute call. It happened once when we got to the point where we were talking about the JavaScript life cycle, which I thought I recovered well as I gave an example about how setTimeout isn't always accurate because of how the life cycle works. It happened another time with a security question that I did answer but in the wrong way. I gave examples of SQL injection and DDoS, however the interviewer was looking to talk about script injections in form submissions.

Overall, the conversation flowed well, and I'd like to think that I came across as confident. I was rather shocked when I got the rejection email a few days later. It's frustrating to not even get the chance to attempt the technical test. The only feedback I received was that the topics covered in the call were not at the level of experience they were looking for. I have nine years of engineering experience. One can only wonder what is asked and deemed satisfactory answers for the senior role. Perhaps the process of how JavaScript is compiled down to binary?

What disadvantages do you get when using styled components instead of SASS? There was one answer.

Can you give me an example of a security attack that a user might perform? There was one answer.