Splunk Interview Questions

Initial 15 minute screening with human resources. This meeting was followed by another call with the human resources manager, and then four Zoom meetings with managers and directors in the organization.

The process was straightforward and well-communicated. Recruiters were transparent about process and next steps. Clear instructions were given at every stage which made the process easy to follow. Interviewers were happy to answer any questions during process.

Applied online and contacted by a recruiter for an initial phone interview. The initial interview was short and was with an adjacent member of the team. Got asked some SQL questions to test knowledge.

Fairly average except point towards a 30 something profile type. "High Energy". "Work Hard Play Hard" environment. Used Diversity as a key word drop only. Identified needed background, but LinkedIn profiles speak differently.

45min plus 45min process with design questions and a med leetcode question with two separate engineers. Some behavioral question scattered throughout as well. Process was pretty chill, it's the standard developer interview.

I was contacted by a sourcer who forwarded my resume to a recruiter, and they arranged an interview for me to speak with a large group. Unfortunately, the entire experience was pretty disappointing. The first interview was supposed to be with the hiring manager, but I was informed with a very short notice that the hiring manager asked to reschedule and one of his subordinates would be substituting for him. That interview went well, but the next two technical interviews with their two senior engineers were very frustrating. The first interviewer of the two technical interviews was a weak communicator, and it was quite challenging to get him to understand a number of simple and concise answers. Additionally, his technical skills were pretty low, and I didn't feel like the interviewer was qualified for the interview. The second interviewer was even worse. He spent at least 10 minutes talking about his own career plan in the company, which was frustrating because a big chunk of my interview time was wasted. The interviewer only asked two questions, and the first question was a coding question which I answered well. However, he then asked some obscure Python questions until I couldn't answer them. This left me feeling that the interviewer was very unprofessional and that the interview missed the mark as they didn't ask truly important questions.

Initially, the HR team seemed enthusiastic about my candidacy, expeditiously progressing me through a three-stage interview process within five days. However, despite communicating my ongoing pursuit of other opportunities, I remained committed to joining the Splunk team and was promised prompt feedback within two business days. Regrettably, after waiting three days without hearing anything, I had to initiate a follow-up. Unfortunately, I was informed that my application was unsuccessful due to an unexpected internal hire. This outcome was particularly frustrating given the time and energy I invested in the process, forgoing other opportunities based on assurances that were ultimately proven to be unfounded. Furthermore, the lack of transparency following the final interview was disappointing and undermined confidence in Splunk's commitment to open communication.

There were four rounds of interviews. Spoke with a recruiter, hiring manager, engineering manager, and product manager. Interviews were easy. Just make sure you know what the job is entailed and how your background fits the job description.

First with TA team then hiring manager. Interview with TA was postponed a few times. With hiring manager went for about 40 min. After that no further communication from Splunk!

1 - Meeting with recruiter was pretty standard 2 - Online coding assessment and case study. Both were reasonable with difficulty and time. 3 - Met with members of the team I would be working with

First round was a behavioral/conversational interview with the hiring manager about my experience and interests. Second round consisted of a presentation to the new team, 30 minute technical presentation on any topic and involved q and a. Yeah