Most unpleasant experience with a recruiter.
Note: The position is based in Canberra.
The first interaction with the recruiter was via email. The recruiter sent an email asking for my availability for the interview, without providing any information regarding the form or content of the interview. After I asked for more details via email, the recruiter stated the interview would be on Zoom, but did not provide a link. I was expecting the link to be provided closer to the interview.
On the day of the interview, I did not receive an email with further instructions. I called the recruiter's phone number five minutes after the scheduled interview time. After introducing my past work experience, the recruiter decided I was technically incapable of working with microservices, despite my past experience in that area. I repeatedly stressed that it is hard to evaluate my technical suitability without knowing more details about Splunk's architecture, and that the question should better be asked by an engineer. However, the recruiter insisted that I "touched the red line" and was not accepted by "the company's value" based on her "gut feeling," and was unwilling to continue the interview.
During the interview, I asked the recruiter if she could provide any information about service discovery at Splunk, but she was unwilling to answer because "it is not her job."
Describe your past work experiences.
Do you know about microservices architecture?
The following metrics were computed from 1 interview experience for the Splunk Software Engineer In Test role in Australia.
Splunk's interview process for their Software Engineer In Test roles in Australia is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Splunk's Software Engineer In Test interview process in Australia.