Software Engineer Interview Experience - Berkeley, California
Process
They sent an email linking to a coding challenge (Codility).
It took 30 minutes to complete, although one hour was given. They suggested it should only take about 30 minutes.
The challenge involved easy Python tasks, and Python was the required language.
This was followed by a phone interview.
I applied online via LinkedIn and heard back relatively quickly.
Questions
Reverse string elements in an array
Was this helpful?
Interview Statistics
The following metrics were computed from 3 interview experiences for the Splunk Software Engineer role in Berkeley, California.
Success Rate
Splunk's interview process for their Software Engineer roles in Berkeley, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Splunk's Software Engineer interview process in Berkeley, California.
Splunk Work Experiences
- 3.0Busy Work, Unstable StocksSoftware Engineer • Current EmployeeSan Jose, California, United StatesJanuary 22, 2022Pros: Fast-paced. Good amount of work to do.Cons: Reorgs happen a lot. Stocks aren't that stable right now.
- 2.0Good Stock, Bad HrSoftware Engineer • Current EmployeeSan Francisco, California, United StatesAugust 11, 2015Pros: Good stock compensation for early employees, good core product, good name, SF, good benefits.Cons: Incompetent HR. Promotions are about who you know. People are hired often who are not great fits but connected. There's a lack of development for management. Working with the recruiting team on hiring for my team was a joke. The engineering community reminds me of a frat house at times. I feel Splunk could have a discrimination lawsuit coming any day based on hiring practices and what is "acceptable". Senior engineers don't have a place here.
- 4.0Good Balance, No IssuesSoftware Engineer • Current EmployeeJuly 13, 2022Pros: Work-life balance is good.Cons: Nothing I can think of!
Splunk Interview Questions
