I applied through an employee referral. The process took four weeks.
The process was quite long and lasted around four weeks. There were multiple stages along the way:
The first step was the pair programming part. I had to make a change in the code that I wrote in the previous stage of the interview process. This part was a bit of a joke as the person who interviewed me was not prepared properly. For some reason, he could not import my Maven project correctly, which caused IntelliJ to complain about all imports in the code. Literally every line of code was red, which obfuscated the code and made working with the code much more difficult. Also, the guy said that he never saw my code before, which was a bit weird. If I made a week's worth of effort to apply for the job, the other side could at least spend several minutes skimming through the code. A bit of advice for the future: I could bring my own laptop, and this part could be performed on it. This would solve two problems: a misconfigured workspace, and me working on a MacBook for the first time in my life.
The second step was the technical interview. After a short introduction, we jumped into my CV, and I was asked some questions about the projects I've been involved in.
The third step was the interview with a project manager and product manager. There were some questions about me working with people in my previous role, e.g., have you ever disagreed with your colleague about a work-related task, how did you present your opinion, and more.
What do you know about the Java garbage collector? Does Java pass by reference or pass by value?
The following metrics were computed from 16 interview experiences for the Zopa Software Engineer role in London, England.
Zopa's interview process for their Software Engineer roles in London, England is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Zopa's Software Engineer interview process in London, England.