Splunk logo

Splunk Frontend Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 20 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Splunk.

Showing 3 of 20
Splunk logo
Splunk

Frontend Software Engineer

Engineering · a year ago

Mid Difficult Positive experience No offer 1 round
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding

The interview process is handled by Karat, an external company. An interviewer from overseas (likely Africa or South Asia) will conduct the technical and coding portions. The coding challenge involved a HackerRank question, with the first one being medium difficulty and the second one being hard, which I couldn't solve. The whole experience felt very automated, and the interviewer offered no assistance. For theory questions, if you don't respond within 5 seconds, they move on. It's not a terrible process, but you need to be well-prepared.

Confirmed questions1 question
  • Can you explain the purpose of useEffect in React?
Splunk logo
Splunk

Senior Frontend Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 7 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Behavioral Technical

The hiring process took over a month and had several steps. I had two recruiter chats, a manager call, and a take-home assignment. Then I did pair programming with a Principal and Senior Engineer, followed by Collaboration 1 with a Principal and Senior Engineer, Collaboration 2 with two Engineers, and Collaboration 3 with a Designer and PM. Things were going fine until Collaboration 1, where one engineer was super rude and seemed more interested in showing off than interviewing. Another colleague looked uncomfortable because of how this person acted. It was the only bad interaction I've had in my career. After everything, they ghosted me.

Confirmed questions4 questions
  • Why are you interested in Splunk?
  • What's the biggest challenge you're currently facing?
  • What salary range are you looking for?
Splunk logo
Splunk

Front-End Developer

Engineering

Intern Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen Background check Offer
Interview formats
Behavioral Technical

I applied in early January 2021 and heard back about a month later to set up the first interview. The first round wasn't super technical. About two weeks after the first round, I was contacted to schedule the final round. I felt like the interview went okay, but the interviewers seemed a bit unresponsive. After the final round, I reached out to my recruiter but never got a response. I tried multiple times over the next two months before giving up. The fact that I didn't even get an automated rejection email after the final round, and then was ghosted by my recruiter, was pretty harsh. I'm sure this isn't typical for the whole company since I've heard good things, but that was my experience.

Confirmed questions1 question
  • Can you elaborate on your prior internship experiences?

Splunk Frontend Engineer Interview Questions

Quoted word for word from Splunk interview reports.

How would you design a REST API, including its methods, parameters, and response format?

Read reports

Can you explain the logic for a progress bar and a to-do list, including React lifecycle methods?

Read reports

How would you approach designing a frontend interface capable of displaying a large volume of data?

Read report

Are you familiar with 10 multiple choice questions on the topic?

Read report

Describe how you'd model a UI transformation given an input and desired output, and explain your reasoning for that model.

Read report

Formats, difficulty and experience

Across all 20 Splunk interview reports.

Interview formats

Technical 35.4%
Coding 31.2%
Behavioral 22.9%
Other 4.2%
System Design 4.2%

Interview difficulty

Easy 30%
Average 60%
Difficult 10%

Candidate experience

Positive 40%
Negative 40%
Neutral 20%