Real, anonymous reports from people who interviewed for Software Engineer at Wise, newest first and distilled into what to expect across the loop.
My experience went in a direction I wasn’t expecting. Early on, I felt the interviewers were relying heavily on a rigid, memorized script instead of exploring architecture and trade-offs in a real way. The session felt rushed toward completion of a skeleton task, and it didn’t leave much room for production-minded considerations like comprehensive error handling.
After a recruiter chat, my process moved into technical rounds with about an hour per stage. I ended up getting far enough that I could feel the momentum build—pair programming first, with a panel that was mostly friendly and even guided me when I felt stuck. In the pairing itself, I tried to stay collaborative and communicate my thinking clearly, and one interviewer at the end told me it had gone better than most senior IC candidates. Even so, it wasn’t enough to move me forward.
The interview process typically starts with a recruiter conversation, followed by a structured loop that includes pair programming, system design, product interviews, and behavioral assessments. Candidates noted that the flow felt organized but could vary in clarity and pacing, especially in later stages.
Candidates experienced pair programming sessions that emphasized collaboration and practical problem-solving, often involving tasks like implementing a circuit breaker. The evaluation criteria varied, with some candidates feeling penalized for asking clarifying questions or for not adhering strictly to expected behaviors.
The system design interviews often presented challenges, with candidates reporting mixed experiences regarding interviewer expectations and pacing. Some felt rushed or faced contradictory guidance, which impacted their ability to demonstrate their design thinking effectively.
Behavioral interviews focused on cultural fit and soft skills, with some candidates feeling the questions did not align with their actual experiences. The tone of these interviews varied significantly, affecting candidates' motivation and perception of the company's culture.
Candidates reported inconsistencies in communication throughout the process, with some experiencing long delays and vague feedback after interviews. Clear and timely communication was highlighted as a key factor in the overall interview experience.
The overall difficulty of the interviews was perceived as average, but candidates noted that the expectations for performance could be unclear, especially regarding how technical and behavioral aspects were weighted in the final decision-making process.