I applied through a recruiter. The process took 5 weeks.The initial interview was a phone call with a talent acquisition manager to understand the applicant and their experience. The second interview is a coding challenge on HackerRank. The challenge itself is about 45 minutes with 15 minutes left for discussion. The problems given are typically Data Structures and Algorithms (arrays, strings, and possibly pointers). Prepare for a few time and space complexity questions about your solution (big O notation). The third round is a system design interview. You're expected to design a system (ex: ticket booking system) at a high level and discuss why you made certain decisions. The next stage is the Loop Interviews. You'll basically be interviewed by the actual team that you'll be working with if you're selected. Prepare for behavioural and scenario-based questions on leadership.Overall, everyone was friendly and professional. I didn't feel nervous during the coding challenge because I was constantly reminded that it doesn't need to be a complete solution. Mind your time in the system design interview and make sure you get to the core problem and discuss that as the main talking point.
How would you handle a team member who is underperforming?
Explain a situation where you had to learn something completely new to accomplish a given task.
The following metrics were computed from 2 interview experiences for the Xero Lead Engineer role in Melbourne, Victoria.
Xero's interview process for their Lead Engineer roles in Melbourne, Victoria is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Xero's Lead Engineer interview process in Melbourne, Victoria.