Software Engineer Interview Experience - San Francisco, California
March 1, 2011
Negative ExperienceNo Offer
Process
Splunk personnel are not organized. They do not know what they need from a candidate.
Even though they knew that I did not have the skills they were looking for, they called me for a personal interview and wasted my entire day.
Beware of this and make sure your skillset matches before going for an interview. Otherwise, you will waste your time.
Questions
Sorting algorithms Performance Scalability Unix and Linux
Was this helpful?
Interview Statistics
The following metrics were computed from 16 interview experiences for the Splunk Software Engineer role in San Francisco, California.
Success Rate
25%
Pass Rate
Splunk's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Experience Rating
Positive38%
Neutral19%
Negative44%
Candidates reported having mixed feelings for Splunk's Software Engineer interview process in San Francisco, California.
Splunk Work Experiences
4.0
Fast Pace, Good People, Micro-managers
Software Engineer • Former Employee
San Francisco, California, United States
July 17, 2024
Pros: Fast pace, good benefits, good people.
Cons: Some managers like to micromanage.
4.0
Good choice overall
Software Engineer • Current Employee
San Francisco, California, United States
June 28, 2022
Pros: Nice people and strong backend coding gurus.
Cons: Top talent leaves faster than before.
2.0
A shadow of its former self
Software Engineer • Former Employee
San Francisco, California, United States
February 12, 2017
Pros: Very useful product, customers legitimately get a lot of value even with high prices. Fair amount of different technology problems to interact with. Individual contributors are often helpful. Overall, this is about as good as you can imagine a mid-size enterprise software shop could be. There's a dream that it's still a fun company, but it's just a company, which isn't a bad thing.
Cons: No longer able to hear the needs of customers, who want usability and reliability. A dysfunctional waterfall process produces poorly integrated features instead. Industry best practices on scope management and quality are given lip service, but not actually followed. Technical debt is fairly high.
New projects often struggle with politics and process.
- 4.0Fast Pace, Good People, Micro-managersSoftware Engineer • Former EmployeeSan Francisco, California, United StatesJuly 17, 2024Pros: Fast pace, good benefits, good people.Cons: Some managers like to micromanage.
- 4.0Good choice overallSoftware Engineer • Current EmployeeSan Francisco, California, United StatesJune 28, 2022Pros: Nice people and strong backend coding gurus.Cons: Top talent leaves faster than before.
- 2.0A shadow of its former selfSoftware Engineer • Former EmployeeSan Francisco, California, United StatesFebruary 12, 2017Pros: Very useful product, customers legitimately get a lot of value even with high prices. Fair amount of different technology problems to interact with. Individual contributors are often helpful. Overall, this is about as good as you can imagine a mid-size enterprise software shop could be. There's a dream that it's still a fun company, but it's just a company, which isn't a bad thing.Cons: No longer able to hear the needs of customers, who want usability and reliability. A dysfunctional waterfall process produces poorly integrated features instead. Industry best practices on scope management and quality are given lip service, but not actually followed. Technical debt is fairly high. New projects often struggle with politics and process.
Splunk Interview Questions
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences
