I had two phone interviews with one manager and one software engineer.
For some reason, both interviews felt like an initial screening: I was given a coding question to work on while they observed, and asked "Why do you want to work for Splunk?"
They chose to conduct the entire process in one week, meaning they emailed me on Tuesday, and by the following Monday, they had already made their decision.
What made this experience negative was that the second interview gave me the feeling the interviewer did not care.
Each time I asked a question during the coding exercise, I had to repeat myself because he didn't seem to be listening (his microphone was also muted).
In fact, the entire second interview lasted only 20 minutes, as he appeared to be in a hurry.
Need to return the minimum value of a stack.
The following metrics were computed from 16 interview experiences for the Splunk Software Engineer role in San Francisco, California.
Splunk's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Splunk's Software Engineer interview process in San Francisco, California.