Zopa

• Engineering standards are generally strong across many teams, with good use of modern tools and practices.

• Kotlin usage is a genuine strength and a good environment for writing clean, expressive code.

• Engineers are trusted with real responsibility and exposure to production systems early on (mostly).

• Flexible working arrangements and reasonable benefits are offered.

The office space is genuinely nice and well designed.

There are a handful of genuinely capable, supportive individuals who care about quality and team health.

• Product direction and differentiation feel unclear, and the company’s USP appears to be losing footing in a competitive market. The product could be significantly stronger.

• A strong MVP-driven culture often prioritises speed over quality, leading to technical debt and rework.

• The environment can feel very sink-or-swim, particularly for junior engineers and associates.

• While there are positive EDI initiatives (e.g. Code First Girls, associate intakes), ongoing support, mentorship, and structured guidance are often lacking. Capable juniors can lose confidence or momentum if they land in weaker teams.

• There is noticeable variance in capability and behaviour at senior levels. Some senior engineers exhibit strong egos that are not always matched by fundamentals, technical depth, or effective leadership, which can create friction and limit learning for others.

• Team experience varies widely depending on leadership and resourcing; inconsistent management coverage can leave individuals carrying significant responsibility without adequate support or advocacy.

• There can be moments of subtle sexism or bias across the organisation, which are not always addressed directly and can impact psychological safety, particularly for women in technical roles.

• Career progression and recognition can feel opaque, especially for senior & mid-level engineers operating beyond their formal scope.