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

      Gorilla Nation

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Gorilla Nation | Offres d’emploi chez Gorilla Nation | Salaires chez Gorilla Nation | Avantages sociaux chez Gorilla Nation
      Entretiens chez Gorilla NationEntretiens d’embauche pour Systems Engineer/IT chez Gorilla NationEntretien chez Gorilla Nation


      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 Systems Engineer/IT

      22 août 2012
      Candidat à l'entretien anonyme
      Culver City, CA
      Aucune offre
      Expérience neutre
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Gorilla Nation (Culver City, CA) en août 2012

      Entretien

      I was approached by a recruiter for the GN job. GN read my resume provided by the recruiter and wanted to setup a phone interview. I spoke with the hiring manager on the phone for about 30min, basic intro about me and hearing how the company was setup. Was given about 10 basic SA/technical questions. About a week later was asked to come in for another interview. Upon arrival I was shuffled from the posh upstairs (3rd floor) to what felt like a basement. It was very open but I felt like it was a cubical testing facility, it was also very deep in the bowels of the earth feeling; despite it being one huge room. I met the hiring manager, a working SA and another person. They brought me into this odd shaped "office" and we danced the typical "interview questions" (ya know "tell me about your self", go). I was asked to write some "code" to output a specific range of characters based on specific conditions. I am not a coder but completed the task with pseudo syntax just to show a conceptual understanding of their problem. The second task was to solve a "typical" *nix/web issue as reported by a user. My terminal was shown on the projector, as I stepped through the system looking for the problem. After about 20min, the task was completed and the access was partially restored. Turns out the office was loaned to me for the interview and I was asked to leave after an hour. Several days go by and I was contact by my recruiter and GN told my recruiter "I was too expensive for them." All-in-all, I am not sure I would have accepted a position at GN even if I was given the option. Initially, it felt like a great place to work, but after seeing the facilities and the attitudes of the employees that interviewed, me I am happy to be "too expensive". I feel this maybe a great place to work for some, the team was fairly younger; however, a bit "green".

      Questions d'entretien [1]

      Question 1

      The "code" request, documented above.
      Répondre à cette question
      1