Candidates applying for Data Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Marshall Wace overall takes an average of 21 days.
Here are the most commonly searched roles for interview reports -
Very long interview process with a long wait time between. Some stages were interesting and interviewers were kind, attentive , bright and unerstanding . No attempt to unsettle and mostly aimed at looking for good fit after the technical rounds
Interview questions [1]
Question 1
Leetcode questions, techincal interview and behavavior
I applied through a staffing agency. The process took 1 day. I interviewed at Marshall Wace (London, England)
Interview
I had not experienced such poor manners from a hiring manager, ever, this is in their London office.
I initially was reluctant to proceed with them because another recruiter in the past forwarded my CV but heard nothing back, however this recruiter was very keen because of the good fit of profile.
After investing 2 hours in a timed Codility test, and providing a very clean solution that passes the tests, I was told that I am rejected because I 'Did not meet standard in Codility test'.
I asked a couple of times for more detail and to double-check in case there was some issue on Codility; was told that hiring manager 'is too busy'. I was concerned that perhaps because I did the coding in my IDE, and copy-pasted the solution into Codility, it could have flagged up a plagiarism check. I still don't know what the issue was, even if it's a mistake on my part, other companies have sent me at least a bit of feedback before, so I was not so upset.
Do not recommend this company. Thinking about them still leaves me with a bitter feeling.
Interview questions [1]
Question 1
Find distance between two tallest blocks; count number of unique ranks.
We are very sorry to hear that you've had a negative experience in our process. For background, we have have hundreds of candidates taking these Codility coding tests and it acts as our first stage of screening candidates. Whilst you may see that your code passes the tests made available on the platform, when you submit your solution Codility runs many more tests on your code behind the scenes in order to 'grade' the level of robustness of your code (and subjecting it to a number of edge cases in terms of input). When a candidate's submission fails the robustness tests to a level below our minimum code quality standards, we inform the recruiters that the submission fell short. We never give recruiters detailed feedback on Codility tests in order to protect the integrity of the test for future candidates.
Candidate experience is very important to us at Marshall Wace. We apologize if all of this wasn't made clear to you from the recruiter managing your process.
I applied through a recruiter. The process took 4 weeks. I interviewed at Marshall Wace (London, England) in Feb 2021
Interview
They initially sent me a coding challenge online. In relation to Leetcode difficulties, this would be one Easy and two Mediums. I then talked to the hiring manager about my goals and why I wanted to join Marshall Wace, followed by two group interviews with folks from the team. I had an interview with the team lead before speaking with someone from HR, then someone from senior management. After that, they extended an offer.
Interview questions [1]
Question 1
What technologies are you interested in working with?
What are your experiences with working on data pipelines?