Software Engineer In Test Interview Experience - San Francisco, California
Process
Applied online and then got an invitation for a video screen a few days later.
Completed the 45-minute video screen on CoderPad.
After a few weeks, they invited me to an on-site interview.
They kept changing the on-site interview date. At one point, they had purchased a plane ticket for me and then cancelled it after 23 hours. Finally got a date pinned down with 6 back-to-back interviews.
The lunch interviewer was nice, but it was a little awkward because he had already eaten lunch earlier. So, it was 40 minutes of me eating while he sat there and made conversation with me. Then, he asked me a whiteboard coding question during the remaining 20 minutes of my lunch hour.
The interview with the hiring manager was horrible. She was looking at her phone the whole time and did not seem interested in the least. She hurriedly gave me the coding question and then went back to looking at her phone. I literally had to clear my throat loudly to get her attention.
It took them 6+ weeks to send a rejection email.
Questions
Zig-zag traversal of an array
LeetCode style questions
Was this helpful?
Interview Statistics
The following metrics were computed from 3 interview experiences for the Splunk Software Engineer In Test role in San Francisco, California.
Success Rate
Splunk's interview process for their Software Engineer In Test 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 Software Engineer In Test interview process in San Francisco, California.
Splunk Work Experiences
- 5.0Great place to work; engineers' input mattersSoftware Engineer In Test • Former EmployeeSan Francisco, California, United StatesSeptember 17, 2024Pros: The work-life balance felt great. There were times, like in any company, where deadlines required more work, but in general, it was a very great balance. It felt like everyone's input was taken into account as well during project meetings, and leaders would make sure you knew you were heard.Cons: Towards the end of my tenure at Splunk, I felt like the growth was too quick for the company to handle. Meetings, projects, and deadlines felt a bit chaotic.
- 4.0Smart Team, Intense MomentsSoftware Engineer In Test • Former EmployeeSeattle, Washington, United StatesFebruary 21, 2016Pros: Lots of really well-respected tech folks work here in the Seattle office; they can be great resources. Getting software for development purposes was made easy through their IT ticketing system. Cool software to work on, C++ codebase fully available with DVCS, in addition to SDKs and other items. View of the Space Needle! Atlassian is great for agile, and they use it.Cons: Some people are a bit intense: "OMG, you don't know exactly everything about this monolithic idea I've been inventing over the past 3 months?" A lot of distributed system problems are coming up, but it's actually a plus because internet infrastructure is something we must all continue to remind ourselves of.
- 5.0Great Balance And Culture!Software Engineer In Test • Current EmployeeShanghai, Shanghai, ChinaNovember 14, 2020Pros: Work-life balance and good cultureCons: I am not very sure about this.
Splunk Interview Questions
