Taro Logo

Principal Software Engineer Interview Experience - San Francisco, California

August 1, 2019
Negative ExperienceNo Offer

Process

The interview process was standard: a one-hour phone screen followed by an on-site interview.

I was initially skeptical when I read Glassdoor reviews, but almost all of them are true about recruiter ghosting. Their recruitment process is extremely broken.

Recruiters would not respond to your emails for a month after the on-site. If you managed to get hold of them over the phone, they would promise to call you back before 5 PM with an update, and then ghost you again for a week.

In my case, the recruiter called me after my on-site to tell me that he would like to invite me on-site. Really? Can you at least check your records properly before calling a candidate? I was given a time and then left stranded for a call by this recruiter!

Anyway, after I had made sure that the on-site had gone nicely and I had not made any mistakes, with code written to completion, the recruiter called me to tell me that they were still looking and could not tell me why I was passed over.

From the kind of answers they gave, I was able to figure out that they themselves don't know what the expectation is.

Do not waste time, money, and energy with people like these who do not value their word or your time.

Questions

1DP 1 String processing 1 design

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Splunk Principal Software Engineer role in San Francisco, California.

Success Rate

0%
Pass Rate

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

Experience Rating

Positive50%
Neutral0%
Negative50%

Candidates reported having mixed feelings for Splunk's Principal Software Engineer interview process in San Francisco, California.

Splunk Work Experiences