Taro Logo

Lead Engineer Interview Experience - Melbourne, Australia

September 6, 2026
Negative ExperienceNo Offer

Process

I applied online. The process took 2 days.

This is my second time interviewing with Xero. The first time was a very positive experience, even though I didn't get the offer. This time I withdrew my application since the pair programming interview was not representative of an engineering culture that I preferred. It was a very simple programming exercise: build four endpoints for an employee service. However, it came with many constraints that made life difficult. I asked to use TDD because that's how I prefer to work; they said no. I asked to comment out failing tests so I could work on passing one test at a time; they told me not to comment out existing tests. I proposed to separate out models and DTOs, but was told they don't care about separation of concerns. Overall, the test seemed to assess development speed instead of depth. This contradicts their interview pack, which says "production-minded" code is what they're assessing for.

Finally, I asked if this was representative of the engineering culture at Xero. They gave me a non-response: "We use AI for everything now." After ending the interview process, I asked for feedback, which is an opportunity for me to provide Xero my feedback as well. They scheduled a 15-minute block in my calendar, but when the day came, they stood me up.

Questions

How do you update the DELETE endpoint so it returns immediately?

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the Xero Lead Engineer role in Melbourne, Victoria.

Success Rate

0%
Pass Rate

Xero's interview process for their Lead Engineer roles in Melbourne, Victoria is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive50%
Neutral0%
Negative50%

Candidates reported having mixed feelings for Xero's Lead Engineer interview process in Melbourne, Victoria.