I applied online, and the process took four weeks.
The coding part involved cloning a repo in advance and then making a bug fix. The actual code change is a trivial one-liner, but they really care about doing TDD, so do not change the code first. First, write both new integration tests and unit tests which should fail for the existing code, and then do the changes, which is what I failed at as I was focused on updating the unit tests. The system design is based on making extensions to the repo you cloned, so do a quick overview of the design before the interview. Otherwise, the questions were pretty standard. Focus on high-level details, and ask clarifying questions about e.g. rate-limiting, etc.
Why do you want to work here?
The following metrics were computed from 41 interview experiences for the Zopa Software Engineer role.
Zopa's interview process for their Software Engineer roles is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Zopa's Software Engineer interview process.