I recently went through Splunk’s interview process and was quite disappointed with how it was handled.
Instead of a recruiter call or initial conversation, I was directly invited to an interview with Karat. The Karat interview felt highly automated, with strict time constraints that didn’t allow for a proper evaluation of my skills.
Even though I performed well in the coding round, the overall process felt rushed and impersonal. The interviewer frequently interrupted, cutting me off mid-explanation to move to the next question. There was no real engagement or attempt to understand my problem-solving approach.
Additionally, feedback was vague and unhelpful, leaving me with no clear understanding of how my performance was assessed. Overall, the process felt like a waste of time—more like a box-checking exercise than a serious effort to find the right candidates.
Splunk should consider improving their interview process by offering a more structured and meaningful evaluation, rather than relying on rigid third-party assessments that fail to capture a candidate's true potential.
The following metrics were computed from 93 interview experiences for the Splunk Software Engineer role in United States.
Splunk's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Splunk's Software Engineer interview process in United States.