Just wrapped my Splunk loop last month. Sharing what the behavioral interview questions looked like and what values they seemed to be probing, because this round surprised me more than the technical rounds.
First, the format. For the senior SWE level there were two dedicated behavioral segments: one in the phone screen and one at onsite. At onsite it was 45 minutes with an engineering manager who ran it completely STAR-style.
Questions I got or that came up in different forms: Tell me about a time you had to push back on a technical decision made by someone more senior. What happened? Describe a project where you had to collaborate across teams with competing priorities. How did you keep things moving? Tell me about a time you had to make a decision with incomplete information and something went wrong. What did you do next? Give me an example of when you had to build alignment on a technical direction you believed in. Tell me about a time you mentored someone more junior and how you measured whether it was working.
The theme I kept noticing: they want people who can operate with ambiguity, push back thoughtfully, and collaborate without requiring a manager to resolve every conflict. It tracks with their org structure, which from what I gather is fairly flat on the IC side.
They didn't ask anything that felt like a gotcha or deeply company-specific culture question. No "why Splunk" until the end as more of a formality.
The EM interviewer was warm and gave me real space to finish answers. Not a rapid-fire interrogation. If anything I had to remind myself not to rush and to be specific with outcomes.
Coming back after a career gap I was most nervous about this round, but it ended up feeling the most human of the whole loop.