The interview process included an initial hiring manager screening, followed by a live coding assessment. While the structure of the process seemed standard, the conduct during the coding session was a cause for concern.
At times, the interviewers came across as unprofessional and appeared to lack the technical depth typically expected in such assessments. After I made changes or implemented new logic in my code, one of the interviewers would copy the entire code. I could literally see them selecting everything in the shared editor.
On one occasion, they even left the entire code highlighted, which made it harder for me to focus and read my own work. I politely asked if they could unselect it, trying not to sound confrontational, but the selection remained.
Shortly after these instances, feedback would be provided that felt generic and disconnected from the context of the discussion, as if it had been generated externally rather than based on a genuine review of my approach. This behavior undermined the credibility of the evaluation and made it difficult to take the technical assessment seriously. It gave the impression that the interviewers were not confident in reviewing code themselves, which detracted from both the fairness and professionalism of the experience.
Based on this experience, I would be hesitant to recommend applying to Wise, especially for technical roles where deeper engagement and thoughtful evaluation are expected.
CV-related questions and easy-to-medium HackerRank code.
The following metrics were computed from 1 interview experience for the Wise ML Engineer role in London, undefined.
Wise's interview process for their ML Engineer roles in London, undefined is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Wise's ML Engineer interview process in London, undefined.