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

      12 mars 2018
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez GitLab en nov. 2016

      Entretien

      The interview process started out pretty normal. - Resume application - Technical questions via email (~2.5hr, by the time proofing etc is complete) - Recruiter conversation (0.5hr) - Team lead 1:1 (1.5hr) - Open Source work done to their (for profit) product (30+ terrible hours) Lets just get right to the technical session: I was informed that the interview would be: 1hr pairing session, with 1-2 hours after to wrap it up in a nice reviewable commit. In the 1hr pairing session, I barely got an introduction to their app. The feature requirement was poorly spec'd and the interviewer decided to make some judgement calls on what it actually entailed. After a 2 week period I had submitted a diff of: 77 changed files with 514 additions and 94 deletions This involved, learning everything about their app. Custom features, setup, fixing their terribly slow spec suite. And writing my new feature to work appropriately with every edge case, and all other possible features. This also involved them having to bring in additional code reviewers to handle questions the original interviewer did not have answers for. It involved writing documentation for unspec'd requirements- of which I was marked poorly for not having guessed the correct assumptions about unspec'd requirements. It involved managing backwards compatibility on all their API endpoints to manage this new feature. The interviewer informed me after the fact that there was a 3 review cut-off. Of which two of my reviews were done after I had pushed un-finished code (because commit early, and commit often), but had not asked for a review. So the reviewer reviewed unfinished broken code, and of course I received bad marks for that. The whole process was a complete and utter disaster. To the point I was just waiting to tell them I was pulling out of the interview process entirely. I don't believe anyone on their current team, could have done this issue in 3 hours, let alone someone who had to learn the codebase starting with no context, and sporadic support. As a matter of fact, being open source, it did actually take one of their employees an additional month+ to complete the feature as required. Do not do free work for them. In Canada this type of interview is actually illegal. Any work a company actively uses after an interview, is required to be paid for.

      Questions d'entretien [2]

      Question 1

      Being a pretty standard Rails application, GitLab is built using the MVC design pattern. Please describe in as much detail as you think is appropriate what the responsibilities of the Model, View and Controller are, both in general and in Rails specifically, and what the benefits of this separation are. Also touch on how the Concern and Service patterns fit into this.
      Répondre à cette question

      Question 2

      How would you determine whether some kind of logic belongs in the controller, the model, or a concern or service?
      Répondre à cette question
      19

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

      Entretien pour Software Developer

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

      Candidature

      J'ai passé un entretien chez GitLab

      Entretien

      The process started fine but after making the homework they've told me that the position was moved to another country, After the position apeared agian in my area I've recent my CV wanting to finish the process but they've never got back to me.
      1

      Entretien pour Software Engineer

      3 nov. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez GitLab

      Entretien

      Pretty straight forward interview which is on their handbook. Initial screening then reviewing a merge request. Technical was with hiring manager which is a mic of technical and behavioural. Practise more STAR format questions for this stage

      Questions d'entretien [1]

      Question 1

      About a time you had conflict with team member
      Répondre à cette question
      1

      Entretien pour Software Developer

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

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez GitLab en nov. 2025

      Entretien

      The frontend and backend interviews were great. The interviewers were calm and level-headed and allowed me to showcase my technical strengths. The hiring manager interviews were not as great. Different hiring managers have different ways of interviewing and you're guessing what it is they want to hear. I think GitLab needs to work on standardizing this process and training interviewers how to interview. In the first interview, the example story I gave was clearly not a fit for the interviewing. Perhaps they could have mentioned that and pivoted, or initially mentioned what they were looking for. In the second interview, I was given feedback for not mentioning things that the interviewer did not even ask. You can't have a candidate who was given incredible feedback on the technical stages (as mentioned by the recruiters and the hiring managers) and barely passing HM rounds. There's a clear mismatch here. Interviewing is a hard thing in general in the software engineering field, and it's something every IC & EM need to work on.

      Questions d'entretien [1]

      Question 1

      Vue & Rails based code review
      Répondre à cette question

      Meilleures entreprises pour « Rémunération et avantages » près de chez vous

      avatar
      SAP
      3.9★Rémunération et avantages
      avatar
      Capgemini
      3.7★Rémunération et avantages
      avatar
      Salesforce
      4.4★Rémunération et avantages
      avatar
      Rappi
      3.5★Rémunération et avantages