Splunk · Primly Community

Splunk onsite / final round, how it really goes from someone who just did it

market_realist · 6 replies

Did the Splunk onsite about six weeks ago for a senior SWE (L5 equivalent) on a platform team. The whole thing was virtual, four back-to-back 55-minute rounds with a short break in the middle. Here's the breakdown.

Round 1: Coding (with interviewer live) This wasn't a leetcode grind. The problem was more of a "implement a feature in a system you're building" style. I got a prompt involving parsing and aggregating structured data. Medium difficulty, but they expected clean, readable, production-ish code. They asked me to talk through my approach before coding and checked in twice during. Very collaborative, almost like pairing.

Round 2: System Design Log/event pipeline design, which I'd prepped specifically. See the other thread I saw on here about this. The key for me: I drove the design proactively and asked clarifying questions upfront instead of waiting for hints. They pushed on consistency tradeoffs and multi-tenant isolation. I felt solid here but the interview ran a few minutes long which I thought was a bad sign. It wasn't.

Round 3: Behavioral with EM Star-method questions. Conflict resolution, technical disagreement, ambiguous project. Pretty warm interviewer. I was tired by this point (third straight 55-minute session) and I think my answers got a bit looser. Recommend front-loading your sharpest stories.

Round 4: Hiring manager conversation This was less structured. More of a "let's see if this makes sense" conversation. They walked through my background, asked what kind of problems I like working on, and talked about what the team is actually building. This is where you ask your own questions. Have real ones.

Timeline from onsite to verbal offer: nine days. Not bad.

Total loop from OA to offer: about 5 weeks.

One thing I'll add: Splunk interviewers in my experience were genuinely interested in how I think, not in catching me out. If you mess up a step and course-correct, they note the correction as a positive signal, not the mistake.

6 replies

visa_vik

Five weeks total is honestly pretty fast these days. Did they tell you at any point during the loop that they needed to do sponsorship verification or ask about visa status? I'm H1B and that's always the wildcard.

qa_quinn

I'm GC so that didn't come up for me. Worth asking the recruiter directly during the phone screen, they're usually straightforward about sponsorship policy.

hardware_hugo

Nine days to verbal from onsite is actually tight on the Splunk side. Most enterprise companies take 2 weeks+ for the debrief and leveling discussion alone. Either your loop was very clean or that team was motivated to close.

consultant_cam

I got the sense the team had been looking for a while. One of the interviewers mentioned they'd had an HC fall through earlier. Makes the timeline make more sense.

mobile_mara

The "round four is basically a conversation" structure is common at Splunk from what I've heard. Some people find it relaxing, others find the ambiguity stressful because you don't know what they're evaluating. Did you feel like they were still scoring you or was it genuinely casual?

ops_omar

Somewhere in between. They were clearly still paying attention to what I said, but it felt less like a rubric-driven interview and more like a sanity check that I'm a real human they'd want to work with. I still prepared thoughtful questions. Don't go in cold on that round.