Applied via recruiter and was sent a Codility test. There appear to be some bugs with the Marshall Wace Codility notification system. First the recruiter told me I'd failed before I'd even taken the Codility test. Then, I was told I'd failed after I'd taken the Codility test. Then the recruiter said there was a mistake and I'd passed the Codility test. I then had a HR round where they decided not to proceed due to lack of fit. I have had far better experiences with FAANG and other HFs/HFTS and would otherwise have marked this a negative experience, but at least responses were very fast on their side.
Codility is 2 hours, 3 questions. LeetCode easy-medium difficulty but not really testing DSA, rather just your ability to write reliable and reasonably efficient code. The main 'gotcha' with Codility is that they have a ton of hidden test cases they don't show you, but fortunately the questions are pretty well-defined.
I finished the Codility in half the time and spent the rest of the time quadruple-checking my answers. HR round was just asking about my prior experiences. Interviewer was nice enough but seemed a bit lofty. I said I was interested in both the quant and engineering sides, but they said their engineers just stick to building pipelines and stay in their own lane. I myself don't like to be so abstracted away from the business so it was a lack of fit.
The following metrics were computed from 8 interview experiences for the Marshall Wace Data Engineer role in United Kingdom.
Marshall Wace's interview process for their Data Engineer roles in the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Marshall Wace's Data Engineer interview process in United Kingdom.