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

      Infoblox

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Infoblox | Offres d’emploi chez Infoblox | Salaires chez Infoblox | Avantages sociaux chez Infoblox
      Entretiens chez InfobloxEntretiens d’embauche pour Senior Staff Software Engineer chez InfobloxEntretien chez Infoblox


      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 Staff Software Engineer

      22 déc. 2023
      Candidat à l'entretien anonyme
      Vancouver, BC
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Infoblox (Vancouver, BC) en déc. 2023

      Entretien

      Around October, an Infoblox recruiter approached me on LinkedIn, mentioning they had job openings. I thought of giving it a try, and today, I just finished the onsite interview, only to receive a rejection email an hour later. Let me share my experience from both the interview and recruiting perspectives. Recruiting: 1) Firstly, this is quite an unusual company, and their recruiters seem to lack some intelligence. Recruiters don't send emails; they directly call you! It doesn't matter if you're busy or not; if they can't find you, they will reach out to you via LinkedIn messages or emails instead. 2) It is OK for the lack of proper training for the recruiters. However, what baffles me is their coordinator. The invites they sent lack calendar invites. Not only that, for three onsite rounds, they send three separate emails, and you have to confirm each one of them. Each email contains a completely different Zoom link. Why it is so hard to consolidate these meeting invites into one zoom meeting? Even if you can't, at least send them in a summarized email for a candidate to keep an eye on. Why can't they even manage the most basic organizational tasks? 3) No context is provided about what each round will entail. I went through 5 rounds, and not once did they inform me in advance whether it would be a coding or system design round. Basic online IDEs weren't provided, neither for the whiteboard tool. Interview Loop: 1) First Round: Had a Behavioral Question (BQ) session with a Director. Standard and nothing special. 2) HR Round: Yes, the HR round comes after the first one. Mainly, HR introduced how great Infoblox is, emphasizing its strong culture, compensation, and low turnover rate. 3) Logical Personality Test: Tests leadership potential and personality traits. You have to schedule a meeting with the coordinator for this, under her supervision. 4) Technical Round: I originally thought this was an onsite round, but it's an additional round. Discussed projects, implemented an LRU cache, looked at my side project, and asked why I hadn't found a job since the layoff. Asked questions that seemed unprofessional. Onsite: 5.1) After the fourth round, no communication. When I followed up, I found out the last interviewer took sick leave. Be professional and at least give feedback before the leave or it will block the interview loop. 5.2) First onsite round: The manager, previously from Amazon, told me they decided to change the role for the interview without informing me in advance. Asked system design questions related to log event collection and persistence in different clusters. Require you to make sure all data will be persistent into same cluster and at the same time to make sure no data skew issue. 5.3) Second onsite round: Data engineer. Discussed a system design problem involving two events (one for device and location information, the other one is for collecting fdqn which is like a click event). I challenged why the two events couldn't be merged and we get all information when it is emitted from the client. He said you could not do that, seems this question was asked for the sake of questions. After the System design was completed, followed by a coding test (Two Sum). Follow up with a 3 sum, and finished them in around 10 mins. 5.4) Third onsite round: Another manager. Asked how to differentiate events with numbers and words to be sent to different queues. Proposed a solution involving adding tags to events. Asked to implement it, At the very beginning, I thought this was another system design. Do I need to implement infra as code and some implementation to call the SQS? Turned out this was a coding question, to check the valid the number, but he was trying his best to trick you by making the question very unclear. This is a question to check a valid number in leetcode, but I can tell he did not have a full understanding on the question, and this is a really bad question to be asked. It only tests nothing except for how you cannot be tricked by the interview. Of course, the interviewer should know the question very well at least before the coding. 5.5) An hour after finishing on-site: Received rejection. Asked for feedback or data points, and they only told me no feedback and good luck. I cannot image how unprofessional this company can do to their interview loop. They made decisions by their feelings or subjects without evaluating the data points. In summary, the interview experience was poor. The company did not have training for their employees to interview the candidates, they don't even know which part they should cover in the loop and that's why mixed questions will be asked. The interviewer did not know what information they should collect to make the decision and just on their feelings. I highly doubt their cultures, The so-called friendly culture makes them weak, and don't welcome leadership from someone more capable than themselves.

      Questions d'entretien [1]

      Question 1

      1) LRU cache 2) Design a system to collect event logs, requiring all logs from the same client should be persistent in the same cluster and no data skew issue at the same time 3) Two events will be sent out from client, one will have deviceId and location information, the other one will have fdqn, timeStamp, deviceId. Collect those two events and present to a FE dashboard. 4) two sum and 3 sum 5) check a valid number from leetcode
      Répondre à cette question