The phone screen wasn't technical at all, just the usual get-to-know-you call.
Onsite was very unusual. It was two hours of back-to-back interviews asking mostly about my experience, so I just expanded on my resume. There was ever only one fairly short technical conversation for the entire process.
Coding question:
This sounds simple enough, but the interviewer doesn't seem to know how to conduct the interview.
As soon as I started writing something resembling a real, usable promise, he would stop me and ask for something quite irrelevant and often just flat-out wrong. He didn't seem to know the difference between a function call's return value and a function value passed into then(). As soon as I mentioned that a promise is useless unless you know it's resolved or lift a resolved value out, he interrupted and started asking for details that just won't result in a working, usable promise implementation.
If this is how they conduct technical conversations day-to-day, I wouldn't want to work with them either.
The following metrics were computed from 1 interview experience for the Wise Frontend Engineer role in London, England.
Wise's interview process for their Frontend Engineer roles in London, England is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Wise's Frontend Engineer interview process in London, England.