I applied online, and the process took 3 weeks. Overall, I am very happy with the interview process, and I strongly believe other companies should follow the approach. I applied directly to the careers site, and a couple of days later I had a short 20-minute phone call with the HR, where I learned more about the role and was asked a lot of questions about my current situation and why I wanted to join. Then I was sent a technical test, where I had to develop an amortization calculator within a week.
Several people complain on Glassdoor about how hard this step is, or that the values, e.g., total repayment of the example, are wrong. I found the test to be a good introduction to how the company is calculating the loan quotes. Initial logic took me around 40 minutes, and I completed the refactoring, structure, plumbing, and unit or integration tests within a day (Saturday). Their engineers had reviewed the test within a couple of hours, and I was invited for a 60-minute technical phone interview with one of their senior software engineers. The interview was quite interesting. It felt like a natural and friendly two-way chat where I was asked a series of questions about my opinion on technologies, approaches, methodologies, and principles that revealed my current level of experience.
The next stage was a two-phase interview in their offices in London Bridge. The first phase was a 45-minute pairing exercise, followed by a 45-minute competency-based questions interview. For the pairing exercise, I worked with another senior developer where I had to extend my technical test to cover a new scenario. I really enjoyed working with Chris, definitely someone I would like to work with, and he was very friendly, very good at explaining the problem, and guiding me through the process. The 45-minute competency-based questions were a typical interview with a very senior board of two where I was asked many questions or given scenarios, and I had to use the STAR technique to give precise answers that would help them assess my experience and compare it with their values. Again, both interviews were very nice and friendly, which made me relax and perform even better. I was told that this part of the process was very new.
I hadn't heard back from them for almost a week. Finally, I was invited for a final 30-minute phone call with the CTO. I was really impressed with the company and their CTO at this point. I informed them before the interview that I accepted another offer, and they were eager to proceed and meet me. So I was invited for a final interview with the CTO and their senior recruiter in their offices. The recruiter handled the whole process and was very professional and friendly. He was quite new to the company and gave me a better insight into the company and their culture, which made me want to be a Zopian. I really enjoyed the final phase. I liked how the CTO was thinking; his time was very limited, but he asked me so many questions and finally offered me a very tempting counteroffer. Overall, I am very happy with the interview process, and I strongly believe other companies should follow the approach.
Why do you want to join ZOPA?
What do you know about ZOPA?
What is your opinion about the SOLID principles?
The following metrics were computed from 1 interview experience for the Zopa Senior Software Engineer C# role in London, England.
Zopa's interview process for their Senior Software Engineer C# roles in London, England is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Zopa's Senior Software Engineer C# interview process in London, England.