Real, anonymous reports from people who interviewed for Software Engineer at Wise. Energy, newest first and distilled into what to expect across the loop.
I had an interview journey where the vibe and fairness felt off from the start. In a technical round that involved filling in parts of a skeleton script, the session felt rushed and overly rigid, like I was being evaluated against a memorized approach rather than how I reasoned. The scope shifted at the last minute because they couldn’t clearly define what they wanted, and I also ran into a major mismatch in fundamentals—state-machine concepts weren’t handled with the depth you’d expect.
After the recruiter call, I ended up in a sequence that felt very timed and very “round-based.” Pair programming came first, framed as implementing a product feature, and it stayed fairly chill rather than turning into heavy algorithm work. Then I moved to system design, where I was asked to build something scalable for payments, and that’s where the difficulty sharpened. The system design session surprised me because it wasn’t just hard—it was also inconsistent. Two interviewers pushed in different directions: one tried to drive me toward a needlessly complex design and kept pushing me to move on when I felt I wasn’t ready, while the other was focused on meeting the requirements without extra ceremony.
The interview process typically follows a structured sequence starting with a recruiter call, followed by technical rounds that include pair programming, system design, and product discussions. However, experiences vary widely, with some candidates noting disorganization and inconsistent communication throughout the stages.
Candidates often participate in pair programming sessions that emphasize collaboration and communication, but experiences differ significantly; some found the atmosphere supportive, while others felt judged or interrupted, impacting their overall performance.
Technical interviews generally assess real-world scenarios and practical coding skills, with a mix of SQL, REST API tasks, and system design challenges. However, some candidates reported a focus on memorized patterns and a lack of clarity in expectations, leading to frustration.
Behavioral interviews often explore candidates' past experiences and how they align with the company's values, but some candidates felt that the interviewers did not fully connect the dots on their contributions, leading to unclear evaluations.
Many candidates reported inconsistent communication and feedback throughout the process, with some experiencing long wait times for responses or receiving generic rejections without clear explanations, which contributed to a sense of frustration and disorganization.
The overall difficulty of the interview process is described as average to hard, with candidates noting that the expectations can vary significantly based on the interviewers' styles and the specific rounds, leading to uncertainty about their performance and fit.