Wise Software Engineer interview questions

Telephone interview Take home test Onsite interview Onsite interview was an open-ended system design type of interview. It all seemed to go well, we talked about my previous experience in system design, and then we designed an internet-based, scalable request-response type synchronous system. It all seemed to make sense to everyone in the interview. I was under the impression that the interview had gone quite well. However the next day I received a "no" with no explanation of what went wrong, or any useful feedback to improve upon. I was left confused.

Quite an easy interview, but communication with the other Software Engineers was very challenging. First off was the design/coding interview which was hosted by two in-house Software Engineers asking questions (sometimes in alternation which was very confusing). I was a bit taken aback by how chaotic the communication went. Jumping rapidly from one subject to another (and then back again), switching between spoken languages (me and the devs had the same native language, and I just wanted to keep it all in English when it comes to interviews, makes it all easy) and not letting me explain a solution deep enough. I kinda knew by the end of this that I didn't get the chance to explain the elevator design or the projects at my current company properly. Next was the PM interview which was really great. The PM focused a lot on how tech affects business, asked me about metrics, KPIs, we talked about a potential project (e.g. how would I improve TransferWise) and it was pretty awesome in the end! The result was negative in the end (as expected), but it was nice to have a look at the office, even though I wish I could have communicated better with the tech folks to understand more about that side of the story.