About this guide
 
Get Hired
Inside Scoop
  • Employees really enjoy working with their teammates, who are passionate and intelligent
  • Good opportunity to work with cutting edge software
  • Incredibly focused on culture and values
 
Interview
Interview Process

The interview process for a software engineer can take 2-3 weeks

Stage 1: Technical assignment
Stage 2: Phone screen with recruiter
Stage 3: Phone interview with team lead
Stage 4: Open source work done to their product

There is no data about the interview process for a data scientist at GitLab.

The interview process for a product/experience/UX UI designer can take 2-3 weeks

Stage 1: Phone screen with recruiter
Stage 2: Interview with product designer
Stage 3: Interview with UX Manager
Stage 4: Interview with UX Director
Stage 5: Interview with product manager
Stage 6: Onsite interview

The interview process for a product manager can take 3-6 weeks

Stage 1: Technical assignment
Stage 2: Phone screen with recruiter
Stage 3: Phone interview with Head of Product
Stage 4: Phone or onsite interview with engineering manager

 
Interview
Interview Questions
  • Describe MVC
  • 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.
  • How would you determine whether some kind of logic belongs in the controller, the model, or a concern or service?
  • Do you have an open source project that you own or contributed to that you feel particularly proud about? Could you provide a link to it or send a code sample?
  • How does a request travel through the browser?

There is no data about interview questions for a data scientist at GitLab.

  • How would you relate information architecture, usability, and interaction design?
  • Design and develop a static landing page for an upcoming webcast. The only requirement is to have a registration form so that users can receive reminders, and follow up emails after the webcast; the rest is up to you.
  • Have you read the handbook? Explain the part you liked the most about it.
  • Tell us about your experience with coding developer tools, personal or professional.
  • What is the minimum bar for releasing to production quickly without sacrificing quality?
  • How would you convince someone to use Kubernetes?
  • How would you handle breaking down a large product feature?
  • What are you favorite CI/CD tools?
 
Culture
About GitLab

Mission

To deliver value to all customers by engaging in a consistent, repeatable, scalable way across defined segments so that customers see the value in their investment with GitLab, and we retain and drive growth in our within our enterprise customers.

Vision

Our vision is to replace disparate DevOps toolchains with a single application that is pre-configured to work by default across the entire DevOps lifecycle.

Recruiting

Want to reach out to Gitlab recruiters? Read our guide and download our list of recruiter email addresses.

  • Collaboration
  • Results
  • Efficiency
  • Diversity
  • Iteration
  • Transparency
 
Company
Hiring Categories

No data available

 
Company
Revenue

No data available

   
Team
Demographics

No data available

 
Locations
Office Locations
  • San Francisco: 268 Bush St, San Francisco
 
Photos
Office Photos