I was contacted by a sourcer who forwarded my resume to a recruiter. They arranged an interview for me to speak with a large group.
Unfortunately, the entire experience was quite disappointing.
The first interview was supposed to be with the hiring manager, but I was informed with very short notice that the hiring manager had asked to reschedule and one of his subordinates would be substituting for him. That interview went well.
However, the next two technical interviews with their two senior engineers were very frustrating.
The first interviewer was a weak communicator, and it was challenging to get him to understand a number of simple, concise answers. Additionally, his technical skills seemed low, and I didn't feel the interviewer was qualified.
The second interviewer was even worse. He spent at least 10 minutes discussing his own career plan in the company, which was frustrating as a significant portion of my interview time was wasted. The interviewer only asked two questions. The first was a coding question, which I answered well. However, he then asked obscure Python questions until I couldn't answer them. This left me feeling the interviewer was unprofessional and that the interview missed the mark, as they didn't ask truly important questions.
Some coding questions and some obscure Python questions.
The following metrics were computed from 93 interview experiences for the Splunk Software Engineer role in United States.
Splunk's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Splunk's Software Engineer interview process in United States.