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

      GitLab

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur GitLab | Offres d’emploi chez GitLab | Salaires chez GitLab | Avantages sociaux chez GitLab
      Entretiens chez GitLabEntretiens d’embauche pour Software Engineer, Backend chez GitLabEntretien chez GitLab


      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 Software Engineer, Backend

      9 janv. 2020
      Employé (anonyme)
      Târgu-Mureş

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer, Backend chez GitLab

      Entretien pour Software Engineer, Backend

      6 mars 2020
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 3 mois. J'ai passé un entretien chez GitLab (Târgu-Mureş) en oct. 2019

      Entretien

      The interview consisted in multiple steps, starting with the first screening call with a person from HR. All the interview got easy scheduled and the communication was good and clear. Next interview was technical and the next 3 were with managers and it was a discussion about technical and work flows. The technical interview was great, I really enjoyed it, I was very nervous but the pair did a great job guiding me on what I need to do. It was a pleasant experience for me. For the next interviews it was mainly discussions about workflows and also a couple of technical questions. In this interviews I had the chance to meet the team manager.

      Questions d'entretien [1]

      Question 1

      If I had a difficult situation and production was in danger, how I reacted, what were my actions?
      Répondre à cette question
      1

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez GitLab

      Entretien

      Applied in the second week of January and didn't hear from a recruiter until end of February. The recruiter showed up 6 minutes late and did not apologize for it. For the next 15 minutes was disingenuous, disinterested and condescending. Failed to expand on the details of the position or the team. When asked further about the role, sent me a link to the GitLab CI/CD documentation. This company can't even tell a solid Software Engineer from a Rails coder. Here's a piece of advice for Gitlab: RoR IS NOT A TECH STRATEGY.

      Questions d'entretien [4]

      Question 1

      Have you used GitLab before
      1 réponse

      Question 2

      What is your Rails experience
      Répondre à cette question

      Question 3

      Have you used GitLab before
      Répondre à cette question

      Question 4

      Are you familiar with Agile
      1 réponse
      2

      Entretien pour Software Engineer, Backend

      17 janv. 2020
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez GitLab en janv. 2020

      Entretien

      All interviews took about a month. After I sent the application I was contacted by the hiring manager to organize a Zoom call. This was the general screening call, after that a technical interview followed. Before the technical interview I was sent a task, which was to review a merge request and provide comments on it. During the call I had to explain my comments and then share my screen to fix the tests in order for CI pipeline to pass. After that a behavioral interview with a team manager followed. After that the final interview, more or less the same as before was scheduled with a director of engineering. Three days after the final interview, which I thought went fine I received more or less standard email that GItlab will not be proceeding with my application. The reason was quite vague, the engineering team simply did not want to proceed. I understand that Gitlab aims for the great fit and tech skills, and almost all of the applications are rejected, but I feel like I spent 5 hours doing the interviews and double that preparing for the interviews for no reason. I would have prefer to be rejected ASAP so it would save everyone's time. The people I was interviewing were friendly, helpful and transparent. It's just that final decision was far from transparent, but that's life I guess.

      Questions d'entretien [3]

      Question 1

      How do you show your leadership skills?
      Répondre à cette question

      Question 2

      What was the time that you had to do a very complicated task, how did you do it?
      Répondre à cette question

      Question 3

      What challenges did you have working asynchronous remote work?
      Répondre à cette question
      2