Principal Engineer Interview Experience - San Francisco, California
Process
The typical software engineering round begins with an email sync with the recruiter, followed by a series of 5-6 hour-long code/design interviews. All the interviewers were quite nice, except for the last one.
The final interview was with a director who was totally rude and unprofessional. Generally, people of that category fall into the 0.01% in the IT sector. It was even difficult to talk to him, let alone work with him. He claimed to be overseeing 4-5 teams, had a shallow attitude, and was disrespectful. This was the worst interview experience, and I left midway.
It is difficult to fathom how one person's behavior could overshadow the genuineness of 6 great interviewers and a great company.
Questions
algos coding data structure system design process/thread cloud
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Splunk Principal Engineer role in San Francisco, California.
Success Rate
Splunk's interview process for their Principal Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Splunk's Principal Engineer interview process in San Francisco, California.
Splunk Work Experiences
- 5.0Making A Difference, Needs More RiskPrincipal Engineer • Current EmployeeSan Francisco, California, United StatesApril 12, 2016Pros: Customers love the product. Lots of challenging problems to work on. The security area is growing. It feels like you are making a difference.Cons: Open to new ideas. Take more technology risks. Enable more collaborations. Make it easier to share knowledge.
- 2.0It's getting a little top-heavyPrincipal Engineer • Former EmployeeSan Francisco, California, United StatesFebruary 1, 2024Pros: Core technology is still strong, amazing, and ready to handle more. Passionate, intelligent, and very approachable employees are great, although the ones who truly grasp the deep technology that makes Splunk work are unfortunately being replaced by the directed "just know enough" approach.Cons: Culture has shifted from the "Go above and beyond for Splunk" to the "Just check the boxes" approach, which stifles work enjoyment and limits innovation. Product direction is continuously changing and negatively impacting delivered quality and substance.
- 5.0Great place to workPrincipal Engineer • Current EmployeeTartu, EstoniaMay 25, 2021Pros: Despite being a large corporation, Splunk manages to stay open and offers good benefits.Cons: A bit more bureaucracy compared to a small start-up.
Splunk Interview Questions
