Phone interview scheduled in the evenings after 8 PM.
It was generic and open-ended. The interviewer seemed unsure of what to ask. It was 8 PM, so we both seemed annoyed at the timing. I'm not sure why she wanted to interview so late.
It didn't seem like the team knew what type of candidate they were looking for. The job description should have said: "Jack of all traits." (They wanted a developer who wants to be a Scrum Master, run manual test cases, and automate test cases.)
The interview was generic and open-ended. The interviewer seemed unsure of what to ask. It was 8 PM, so it appeared we were both annoyed at the timing. I'm not sure why she wanted to interview so late. It didn't seem like the team knew what type of candidate they were looking for. The job description should have stated: Jack of all traits. (They wanted a developer who wants to be a Scrum Master and run and automate test cases.)
The following metrics were computed from 1 interview experience for the Splunk QA Engineer role in San Francisco, California.
Splunk's interview process for their QA Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Splunk's QA Engineer interview process in San Francisco, California.