Marshall Wace Software Engineer Interview Questions
& Process

You start with an application and CV screen where they check your grades, tech experience, and projects. Then, there's an online coding test, usually on Codility, that looks at problem-solving, data structures, efficiency, and clean code. The next step is a first-round interview, which is HR/behavioral, and it's a video call about your motivation, communication, teamwork, and if you're a culture fit. They might ask things like 'Why Marshall Wace?', 'Why fintech / hedge funds?', and about an engineering challenge you faced. After that, there's a technical interview or lab-style assessment where you do a hands-on coding or debugging task in a controlled setting, potentially with Python, Java, or similar languages, and questions about systems and data handling, possibly reviewing or adding to existing code. Then, you'll have a project presentation interview where you showcase a coding project you're proud of, explaining your thought process, design choices, architecture, and trade-offs, aiming for clarity, structure, and insight into teamwork. The final round is on-site in Hong Kong with senior engineers, including a culture fit chat. There might be some logic/technical questions, but the main focus is on collaboration, ownership, and your ability to make an impact quickly. If you're a top performer, you might get a return offer for the graduate program.

The interview process had three stages. The first two went fine, but the third stage, which was technical, didn't go so well. I was told in the second round that the job mainly used two specific technologies, so I only prepared for those. However, I wasn't asked any questions about them. The questions asked were vague and confusing, and it felt like the interviewer was deliberately trying to confuse me, which was unpleasant. One question I could have solved using one of my prepared technologies, but when I suggested that approach, the interviewer rejected it while still referencing the technology multiple times. This was very confusing. The interviewer also wasn't very personable, so I doubt I could have built a good relationship with them. I did, however, really like the manager of the team, so it's a shame I won't be able to work with them.

Went through the whole loop in their Trading Tech team. It's a pretty standard hedge fund interview process, but they make you do a HackerRank with 3 questions before any human interaction. Be warned, they require C++14, not C++20, which was almost a dealbreaker for me as I had to rewrite my C++20 code. Later, I had several Zoom 1-on-1s with developers and HR, covering live coding, design, and behavioral topics. Then came the on-site interview, which was quite rough. Some interviewers were confrontational, asking difficult design questions with little time left, or making assumptions about me creating issues if I were to join. I wanted to leave immediately, sensing something was off. A week later, I received completely inaccurate feedback. While I accept personal dislikes happen, a simple ghosting or standard rejection would have been better than fake feedback. Overall, the company seems mediocre, struggling with balancing off-the-shelf vs custom solutions and potentially rejecting many candidates to maintain perceived value.