The slowest interview process ever, so far. The recruiter had no idea about the company or the Cloud Infrastructure org. They did not reveal the hiring level throughout the process. That was the first red flag.
I cleared the phone screen interview and was invited to a one-day onsite interview at Splunk's San Jose - Santana Row office. I did pretty well in all the rounds. The interview questions were moderate, not difficult at all.
However, they replaced my managerial interview at the last moment with some other junior manager from the London office who was visiting Splunk at that time. That person had just been promoted to manager level and had no idea about how hiring works in Silicon Valley. That was the second red flag. Having said that, I did pretty well in the lunch interview with them. The last interviewer even asked me an extra credit problem from their day-to-day work, and I solved it. They told me I did very well.
The last interviewer escorted me out of the office and said the recruiter would follow up soon. I did not hear from the recruiter for two weeks. Finally, I emailed the recruiter asking about the decision. The recruiter did not even care to tell me the decision man-to-man via email. They sent me a sample system-generated email stating that they had decided to move forward with another candidate.
I have a feeling that I was overqualified for the job. I would not recommend anyone interview in their Cloud Infrastructure org. The overall process was very shady and non-transparent.
Easy - Medium Leetcode Questions
The following metrics were computed from 11 interview experiences for the Splunk Software Engineer role in San Jose, California.
Splunk's interview process for their Software Engineer roles in San Jose, California is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Splunk's Software Engineer interview process in San Jose, California.