Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Splunk

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Splunk | Offres d’emploi chez Splunk | Salaires chez Splunk | Avantages sociaux chez Splunk
      Entretiens chez SplunkEntretiens d’embauche pour Senior Software Engineer chez SplunkEntretien chez Splunk


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Senior Software Engineer

      13 août 2022
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Splunk en mai 2022

      Entretien

      I applied on their career portal. They contacted me by email to setup an interview. Initially upon joining the interview, the guy was a bit standoffish and looked like he didn't like me. For context, the position was for a frontend developer job with React and Node.js, and the person giving me the interview was a Java developer, which is about the worst possible person to be giving a frontend interview. As such, the questions had nothing to do with either one, and instead asking me to implement a datastructure and solve a pretty easy problem in Javascript. I was asked to implement a Stack, which i had no experience with, because you would obviously never need to write a stack in Javascript, and if you did it would be called a queue and be used for a totally different purpose. I had to ask the interviewer to explain to me what a stack is, and then i was able to code it in a few minutes, but it had a few bugs due to type conversion which took me another few minutes to debug and fix. I was asked then if I could describe the algorithmic complexity using big O notation, which I said i could not. Then i was asked to make an optimized version of the stack. So i rewrote it slightly to reduce the complexity, to what I believed to be O(n). The interviewer gave a nod of approval but looked unimpressed. The second question was more interesting and more challenging, but i was able to solve it quickly. The task was to find the first duplicate in a sequence. For which i wrote a pretty inefficient map reduce (two loops) for. Keep in mind I am interviewing for a react position, so a map reduce would be what you would expect in react, not a while loop. In node.js i would opt for a while loop, though many Javascript people would prefer the functional style of map/reduce over the speed of the while loop. Again the interviewer asked me to describe the complexity and improve my solution if I could. To me this was the pivotal moment of the interview, and I just said "no i don't think i can". The final question was "why do you want to work here and why should we hire you", and i didn't give a meaningful answer.

      Questions d'entretien [1]

      Question 1

      1. Implement a Stack 2. Write a function to find the first duplicate in a sequence 3. Why do you want to work here 4. Why should we hire you
      Répondre à cette question
      5

      Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez Splunk

      Entretien pour Senior Software Engineer

      12 mars 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Splunk

      Entretien

      5 interviews: screening, technical screening via Karat, live coding, system design, team fit. Leetcode preparation should be enough. Karat interview can be retaken. All interviews were on point and were related to actual job afterwards.

      Questions d'entretien [1]

      Question 1

      Sliding window algorithm to scan data in realtime
      Répondre à cette question

      Entretien pour Senior Software Engineer

      17 sept. 2025
      Employé (anonyme)
      Bengaluru
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien chez Splunk (Bengaluru) en juill. 2025

      Entretien

      I recently interviewed with Splunk, Cisco, and had a very positive and professional experience. The process began with a Karat screening round, followed by multiple on-site interviews. Karat Screening Round – 3 Components: System Design: Discussed distributed systems versus dedicated servers and performed a high-level design (HLD) for a game parlour card machine. Angular: Covered dependency injection, Signals, and RxJS operators. Coding: Implemented a UI screen based on a reference image using HTML, CSS, and JavaScript. After successfully clearing the Karat round, HR collected my details and scheduled four on-site interviews: DSA Round: Solved two medium-difficulty problems on the Codility platform. Angular & DSA Round: One DSA problem plus questions on Angular and RxJS operators. System Design Round: Designed a high-level architecture for a concert booking platform. Manager Round: Discussed current project architecture, role-related behavioral aspects, and expectations from the position. The process concluded with an HR discussion regarding the offer. While there was no negotiation, the package offered was highly competitive and satisfactory.

      Questions d'entretien [1]

      Question 1

      System Design: Discussed distributed systems versus dedicated servers and performed a high-level design (HLD) for a game parlour card machine. Angular: Covered dependency injection, Signals, and RxJS operators. Coding: Implemented a UI screen based on a reference image using HTML, CSS, and JavaScript. Two medium-difficulty problems on the Codility platform. Angular and RxJS operators. high-level architecture for a concert booking platform.
      Répondre à cette question
      1

      Entretien pour Senior Software Engineer

      30 mai 2025
      Candidat à l'entretien anonyme
      Bengaluru
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Splunk (Bengaluru) en mai 2025

      Entretien

      2 rounds of Karat platform interviews focused on technology skills and DSA, Algo. 1 system design round - Focused on large scale data streaming. 1 Hiring Manager Interview. The experience was deeply disappointing and, frankly, unprofessional. Throughout the interview, the hiring manager appeared disinterested and disengaged—he yawned multiple times, which gave the impression that he was either bored or not taking the conversation seriously. This behavior was both distracting and disrespectful. Additionally, I was asked to solve a problem using Java, which I proceeded to do. However, after I completed the task, the manager abruptly stated that he had been expecting a shell script solution instead. This lack of clarity and shifting expectations during a technical interview reflects poorly on the preparation and communication standards of the team. Interviews are a two-way evaluation process, and this interaction left me questioning whether this organization values professionalism, respect, or the time of its candidates.

      Questions d'entretien [1]

      Question 1

      Parse a large text file to count different types of exceptions
      Répondre à cette question