
Splunk Site Reliability Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Splunk.
Senior Site Reliability Engineer
I had a screening call with a recruiter, then a coding round, and finally a system design interview. Overall, it was a good experience, except for the system design part where the interviewer seemed uninterested in my approach and possibly had a specific solution in mind. The coding round was straightforward, starting with a basic problem and then adding a few extra conditions.
- Could you design a monitoring system for metrics?
Site Reliability Engineer
Applied via careers portal and then got a call from the recruiter. He emailed me the process and told me the first round would be a scripting round focusing on log slicing, not DSA. However, the first round was a KARAT interview, which unexpectedly included two medium LeetCode-style coding questions. I tried contacting the recruiter about this discrepancy, but he didn't answer and later messaged that I didn't qualify for the next round, without addressing the situation.
- Were asked some situation based questions and shown some graphs to figure out the potential reasons for certain events.
- Asked a typical LeetCode style 2D array question that involved searching.
Site Reliability Engineer
First, there was a recruiter call to go over the basics of the job and my background. Then, I had two calls with SREs based in London. These weren't technical, mostly discussing what they do, what I do, and any questions I had. The next step was an on-site interview in San Francisco, for which they covered flight and hotel, and I expensed food. There was a mix-up with the date, but HR sorted it out. I met with 7 people, including engineers, PMs, a manager, and a director. Everyone was friendly and answered my questions. No technical questions were asked, possibly because the date change caught them off guard. It was mostly behavioral and situational questions. The office seemed nice with a good vibe. After the on-site, my recruiter gave me positive feedback and said there were three possibilities: offer, no-offer, or more interviews. I was told there would be more interviews, leading to a month-long wait. I received another offer during this time. Eventually, they informed me about position shuffling and a different role for me. Since I didn't want to wait any longer, I declined. Overall, it was a good experience, but I wished they had been quicker to make a decision.
- If a customer reports they can't access a webpage, what's your troubleshooting approach?
- How would you troubleshoot a webpage accessibility issue reported by a customer?
Splunk Site Reliability Engineer Interview Questions
Quoted word for word from Splunk interview reports.
“Can you explain basic Linux commands, such as 'ps -ef'?”
Read reports →“If a customer reports they can't access a webpage, what's your troubleshooting approach?”
Read reports →“How would you troubleshoot a webpage accessibility issue reported by a customer?”
Read reports →“Can you explain Splunk to someone?”
Read reports →“Could you design a monitoring system for metrics?”
Read report →“What is your proudest accomplishment?”
Read report →“How would you approach a troubleshooting scenario? Knowledge of K8s is a plus, but you will receive guidance.”
Read report →“Describe your approach to system design, considering aspects like AWS, GCP, security, and monitoring.”
Read report →“Could you describe your experience with Object-Oriented Programming modeling?”
Read report →Formats, difficulty and experience
Across all 13 Splunk interview reports.