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

      Aha!

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Aha! | Offres d’emploi chez Aha! | Salaires chez Aha! | Avantages sociaux chez Aha!
      Entretiens chez Aha!Entretiens d’embauche pour Devops Engineer chez Aha!Entretien chez Aha!


      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 Devops Engineer

      20 juil. 2018
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Aha!

      Entretien

      First interview with a security engineer went OK? A little condescending but ... OK... I get it, security is not a fun field to be in these days. I got the thumbs up to proceed to the next interview, this is when the fun starts. My second interviewer was ~15 mins late... when he finally gets there, interview went well... bumped up to the next round, CTO. This is when it gets really crazy, 3 interviews all going over an hr of the scheduled times, most of them he was late to. Overall, he is a very knowledgable engineer, but wow... The questions were pretty ridiculous for a DevOps Engineer role, he was asking what kind of binary trees are implemented in MySQL, how hash tables work, and other awesome data structure related trivia I hadn't seen since my Comp Sci courses 10+ years ago...what? Who cares? I mean not everyone is a PhD or has the daily/weekly refreshers on this stuff. Somehow he is convinced you need to know this to be an effective DevOps Engineer. Power to them, the vast majority of us out there - please don't waste your time.

      Questions d'entretien [2]

      Question 1

      How do hash tables work?
      Répondre à cette question

      Question 2

      What data structures does MySQL implement? i.e. why does indexing help?
      Répondre à cette question
      2
      avatar
      Réponse de Aha!
      7y
      Thanks for the feedback. We do our best to make the interviewing process as candidate-oriented as possible, but we do not always get it right. We have discussed your comments with the interviewing team. I also want to share a bit more info on the DevOps role. It is definitely a unique position. We are looking for someone to implement and automate operational tasks and have deep knowledge of the systems we use (operating systems, databases, application framework) to help the engineering team respond to, understand and troubleshoot production issues. Deep knowledge of how the operating system and database work under the hood helps immensely when architecting the infrastructure, or solving an issue. We use Ruby for both our application code and our automation infrastructure and we expect DevOps engineers to work side-by-side with the rest of the engineering team, following the same processes for their development too.