Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
Xero interviews FAQs
Software Engineer applicants have rated the interview process at Xero with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 82% positive. To compare, the company-average is 57.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 17 days to get hired, when considering 11 user submitted interviews for this role. To compare, the hiring process at Xero overall takes an average of 23 days.
Common stages of the interview process at Xero as a Software Engineer according to 11 Glassdoor interviews include:
Phone interview: 24%
Group panel interview: 20%
Skills test: 16%
Presentation: 12%
One on one interview: 12%
IQ intelligence test: 4%
Personality test: 4%
Drug test: 4%
Background check: 4%
Here are the most commonly searched roles for interview reports -
the interview process is straightforward. typical what you expect for a software developer interview: Initial chat, technical question and team fit. Total took around 3 weeks. they take very long to offer
I interviewed at Xero (Auckland, Auckland) in Mar 2026
Interview
The questions are difficult. Coding assessments: Can be live or take-home. pair programming with a given question. Behavioral + teamwork: how you work in teams, handle conflict, and resolve issues.
I applied online. The process took 3 weeks. I interviewed at Xero (Melbourne) in Mar 2026
Interview
It takes too long. The questions are difficult. Also there is a behavior test, not sure whether this test is useful. The technical questions are good:
Lead technical design and implementation of complex features and systems
Write high-quality, maintainable code and automated tests
Make pragmatic architectural and technical decisions that balance short-term delivery with long-term sustainability
Coding assessments: Can be live or take-home. pair programming with a given codebase.
Behavioral + teamwork: Interview with non-engineers (e.g., PMs) to probe how you work in teams, handle conflict, and resolve issues.