Performance Engineer Interview Experience - San Francisco, California
Process
Was contacted by a recruiter about a week after the application. The recruiter called to go over the process (two or three rounds: first round with one coding challenge, second round as a panel interview). The coding challenge was a little hard, but they try to help you think it out!
Questions
Difference between multiprocessing vs. multithreading.
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Splunk Performance Engineer role in San Francisco, California.
Success Rate
Splunk's interview process for their Performance Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very negative feelings for Splunk's Performance Engineer interview process in San Francisco, California.
Splunk Work Experiences
- 4.0Good Pay, Talent DrainingPerformance Engineer • Current EmployeeSan Jose, California, United StatesOctober 15, 2021Pros: My coworkers were mostly great. The company treats employees very well, and I think it’s apparent in the salary and benefits choices. Some devs are very competent! I feel like I have learned a decent amount here. A lot of room for promotion on my team.Cons: All employees with real talent seem to be leaving. There is not a lot of hope in the company right now, a lot of gloom because the stock price has been sinking, and there are many failed products.
- 4.0Good place to workSoftware Engineer Intern • Former EmployeeSan Francisco, California, United StatesNovember 9, 2025Pros: People were very helpful, and everyone was very welcoming and kind.Cons: Extra work depending on the project you get assigned.
- 4.0Good Benefits, Growing PainsSoftware Engineer • Current EmployeeSan Francisco, California, United StatesOctober 7, 2025Pros: Good benefits and collaborative environmentCons: Turning into a large company
Splunk Interview Questions
