Real, anonymous reports from people who interviewed for Software Engineer at Xero, newest first and distilled into what to expect across the loop.
I went through a multi-stage Software Engineer loop that balanced manager/design conversations with coding, and I ended up not getting to a stable close.
I attempted to interview for the Software Engineer role, but the process was so opaque that I was rejected without meaningful visibility.
The interview process typically includes an initial recruiter screen, followed by technical assessments (coding and system design), and behavioral interviews, often culminating in a team fit discussion or a 'Grad Day' event.
Candidates can expect a mix of live coding challenges on platforms like HackerRank, focusing on algorithms and data structures, as well as system design discussions that require high-level architectural thinking.
Behavioral interviews assess cultural fit and working style, often involving discussions with team members or non-engineers, which can vary in intensity and focus depending on the interviewers.
Candidates reported varying experiences with communication quality, including delays in scheduling, unclear feedback, and a lack of transparency throughout the process, which can impact overall candidate experience.
The outcome of interviews can be unpredictable, with reports of roles being paused or canceled, and candidates often not receiving clear reasons for rejections, contributing to a sense of frustration.
Candidates suggested focusing on coding speed and familiarity with the specific programming language used in assessments, as well as preparing for behavioral questions that align with company values.
