Taro Logo

Principal Software Engineer Interview Experience

November 16, 2020
Negative ExperienceNo Offer

Process

My onsite interview felt less like an interview and more like an interrogation.

The first interviewer talked extensively and jumped between topics, making a simple problem sound complex and confusing. He spoke for about 90% of the time during what seemed to be a half-design, half-coding interview, hardly giving me a chance to speak, process, or analyze the problem. Asking a simple clarifying question would lead to a long-winded, five-to-six-minute lecture that jumped all over the place.

The rest of the interviewers seemed more coherent. However, each session involved an interviewer coming online and rapidly bombarding me with question after question, in a manner that felt more like an interrogation and less like an interview.

The interviews were set up via email without speaking to the recruiter once. After the interviews, there was no response from the recruiter. Weeks later, I received an automated rejection email.

Going by the interview process, I highly doubt whether Splunk is a good place to work.

Questions

Interrogation-style interview.

Most questions had multiple parts.

Was this helpful?

Interview Statistics

The following metrics were computed from 12 interview experiences for the Splunk Principal Software Engineer role in United States.

Success Rate

8%
Pass Rate

Splunk's interview process for their Principal Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive33%
Neutral0%
Negative67%

Candidates reported having very negative feelings for Splunk's Principal Software Engineer interview process in United States.

Splunk Work Experiences