Hiring new Customer Support team members is a multi-department process involving talent acquisition and customer support.
Support Engineers comprise the vast majority of Customer Support. This page presents information specific to that job family. Exceptions are called out explicitly, such as in the Reviewing Assessments section.
Hiring is described on the jobs page for Support Engineers. The following are the stages carried out by Customer Support team members.
If you have open positions on your team, you should join (or arrange) a source-a-thon on a regular basis to proactively identify candidates our recruiters can reach out to. More information can be found on the general Sourcing page.
GitLab Participant: Support Engineer
The assessment questionnaire contains a number of customer scenarios and technical questions relevant to the position, including written English ability. Support engineers are responsible for reviewing the candidate responses.
GitLab Participant: Support Engineer
The technical interview for this role is conducted by support engineers. It is a practical interview that covers topical areas relevant to the position, including customer scenarios.
GitLab Participants: Support Manager and one other (Support Manager or Support Engineer). At least one interviewer will be non-male.
The behavioural interview may cover any topics of the previous interviews where there was unclear data or a need to dive deeper.
GitLab Participants: Senior Support Manager or Director, Customer Support
Candidates successful in all previous interviews may proceed to a Senior Manager or Director, Customer Support interview.
GitLab Participants: Support Manager, Senior Support Manager
Managers are invited to provide feedback on scorecards submitted by other interviewers, in order to help improve the interviewing process. This feedback should be provided directly to the individual interviewer.
If you want to be involved in the hiring process - let your manager know! The main ways you can be involved are:
Each of these have a training module. The technical assessments don't involve direct interaction with candidates, however the technical interviews do, so a component of the training module is to complete the GitLab Interview training. Have a chat with your manager, then create and complete your training issue.
Guidelines for reviewing and giving feedback on assessments for the Support Engineer role can be found in the Support-Assessment-Solutions project.
Assessments are assigned by the support aligned Recruiter in the Talent Acquisition team. These are carried out asynchronously, so you could be asked to to review assessments from candidates in all regions.
Assessments that are sent to candidates for all Support job families are available in the people-ops/hiring-processes repository.
The technical interview process is documented in the Support Team project. Follow the instructions there to conduct this interview. Take any notes in Greenhouse and make a note if you are inclined or not inclined to hire. Your role in the interview process for this candidate is complete!
Before you can do any of the above you'll need to have an open requisition and a vacancy in that requisition. You can learn more about these terms and the process at Requisitions and Vacancies in the Hiring Section of the Handbook.
The VP of Customer Support is the DRI for the hiring plan. They will ensure that headcount is allocated to regions and approximate hiring dates.
For each vacancy there should be a:
A source-a-thon is a synchronous or asynchronous activity where one or more individuals gets together to actively look for candidates. If you want to participate, make sure you upgrade your LinkedIn Account.
More general information about this activity is on the general Source-a-thon page.
On the first Monday of each month we have a Source-a-thon called the "Sip 'n Source". The position we'll be sourcing for will change depending on need, but bring a special drink, get ready for some music and get ready to source! If you can't join, that's okay, you can still participate async.
Each month, before the synchronous event: