The process was fairly disorganized.
My initial phone screen had to be rescheduled after they missed the first time slot, and that rescheduling process took weeks.
After the on-site interview, I received a verbal offer. When asked if I had other offers, I informed them I had one more verbal offer.
They then stalled on providing a written offer, stating they wanted to know the value of my other offer first.
When I finally received the numbers for both offers, Splunk's was lower and did not include a starting bonus.
I inquired if they would match my other offer, and they agreed to match the salary.
When I asked if the starting bonus could also be matched, the recruiter said she would check.
The next day, I received a call informing me they were retracting the offer because I was "too focused on the money and not enough on the opportunity."
Basic Git Procedures
Lots of fairly specific Python syntax and operational questions. This part was pretty fun, since the interviewer clearly knew a lot about Python and the problems were fairly unique. He was fine with me but knowing everything up front with them.
The following metrics were computed from 3 interview experiences for the Splunk Software Engineer (Internship) role in San Francisco, California.
Splunk's interview process for their Software Engineer (Internship) roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Splunk's Software Engineer (Internship) interview process in San Francisco, California.