I applied online. The process took two weeks.
It was the industry-usual process. First there was the phone screen, then a 1:1 over Hangouts, and then an onsite with a panel. The office location is nice, and the people were nice and friendly. They advertised for an analyst, but they are mostly looking for a lead role for a new team that they are building from scratch. The interview process is not in line with the job description in the ad. The ad asked for beginner to moderate coding skills, however, the type of questions and the emphasis on coding during interviews say otherwise. Moreover, this is a back-end API testing-related position with no UI, but the ad does not make a mention of such.
Several real-life scenarios were given, and I was required to develop test scenarios out of them.
Basic programming questions were asked, and I had to provide logic for the approach, as they use C#.
I was given a coding problem to remove all if/switch case conditions by refactoring it to make it polymorphic.
I was asked to write a unit test for existing code.
The onsite interview had a 50/50 ratio of technical coding and testing questions, with very few personal or behavioral questions.
The following metrics were computed from 1 interview experience for the Xero QA Analyst role in San Francisco, California.
Xero's interview process for their QA Analyst roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Xero's QA Analyst interview process in San Francisco, California.