Wise's interview process and salary bands are made transparent.

The interview was practical in nature; it featured no LeetCode-style questions but rather a case of, "Here is a real problem, now write code to solve it." Ensure it's readable and uses best SWE practices (e.g., DRY).

Now for the bad part. You have a fixed time to solve the problem. However, you may also need to contend with (in my case) a language barrier. In a real-world scenario where the time constraint is not so limited, I have no problem with that. However, in this case, where I confirmed with you 10 minutes ago that I made X assumptions (which I got an "mhmm" and a head nod for) and now you are asking me about that code again, the plot was already lost. Not to mention the number of times one or the other person needed to repeat the question or answer.

I will not say I am blameless, because I think I know exactly where I messed up. BUT, if this was supposed to be a pair-coding exercise under time, don't turn it into a language-deciphering exercise as well.