Your Executive Team member must escalate and obtain authorization for any new job positions/searches if they are not part of the Hiring Forecast. Note: Must have a GitLab email to view. Roles listed on the Hiring Forecast will have a status of Open, Closed, Filled, Draining, or Pending Approval which are defined below:
Open - vacancy is open and we are actively sourcing and hiring for the role
Closed - no vacancy, not actively sourcing or hiring for the role
Filled - vacancy has been filled by internal or external candidate
Draining - vacancy is closed, no longer accepting new applicants, but will review existing candidates through the hiring process and fill the role if a qualified candidate is identified from existing applicants
Pending Approval - vacancy has been suggested by executive team member and is pending board, CEO, or CFO approval.
Hiring manager identifies the need for a new or replacement team member and contacts the People Ops Generalist to review their strategic hiring plan. If the role is deemed necessary, the team will follow the following steps to open the vacancy for applicants.
If a description of the role does not already exist, the hiring manager will create a vacancy description and assign the MR to the People Ops Generalist and tag the Recruiter.
Create the relevant page in https://about.gitlab.com/jobs/[name-of-job], being sure to use only lower case in naming your directory if it doesn't already exist. If the location of the applicant is important, then the location and a compensation range corresponding to that location can be provided as part of the vacancy posting.
A Recruiter will use a this gender decoder to ensure that the language and structure of the vacancy description is gender neutral. The recruiter will make necessary edits to the vacancy description to create a neutral description.
Once a vacancy description exists, hiring managers should update the Vacancy Requisition Document with the proposed vacancy. Once every column is completed for the role, assign the line item to your People Ops Business Partner (either Generalist or Sr. Director of People Ops) through the comments. If the role is not already in the hiring forecast, the Business Partner will assign the line item to the CFO/CEO for final approval.
After final approval, the People Ops Generalist pings the People Ops Specialist to propose an appropriate NYC benchmark compensation for the role, and they submit the proposal to the compensation committee for approval.
For any position, filling in the NYC benchmark salary in the jobs.yml file will automatically cause the Compensation Calculator to show at the bottom of the position description page.
For some positions, it may be possible or desirable to exclusively seek candidates outside of higher cost regions. This is a role by role decision between the Hiring Manager and People Operations. If it is decided to seek candidates outside of higher cost regions, then that needs to be explicitly communicated on the position description page in order to set fair expectations for candidates and recruiters alike. Sample text to consider placing on the position description page: "Globally, xx % of people live in metro areas with a rent index greater than yy, while at GitLab, this is zz % of people in this role currently. Therefore, in line with our value of staying frugal, we are now focusing on only hiring in metro areas with a rent index lower than yy. Please bear this in mind when using the compensation calculator below." (obviously, fill in the missing numbers).
Once the salary benchmark has been determined and posting have been approved, a Recruiter will create the position in Workable, using the exact same job title. If this step is completed out of order, people are able to apply even though the position posting may not have been approved yet.
For location, select "Telecommute".
For the description, write For the job description, see [URL of relevant jobs page on about.gitlab.com]
Indicate what applicants need to provide with their application. By default, this will include their resumé, a cover letter, but it may also include qualifying questions such as "What timezone are you in?".
Get one of the admins (People Ops and CEO) to "Publish" the position, and follow the links to the application form (you will need this URL).
Add the URL to the application form into the merge request for the data/jobs.yml file.
In the data/jobs.yml file, open the position or add a new entry for it. Roles are automatically sorted alphabetically by title on the jobs page. When someone views the vacancy description page, an "Apply" button will be shown for that position if we're currently hiring for it.
Adding a new role: add an entry with the following format:
Opening an existing position: If the position is already listed in the jobs.yml file but not "open", simply change open: false to open: true to have the position appear on the listings.
Closing an existing position: If we're no longer hiring for a particular position change open: true to open: false for that position to hide it from the listings.
Note: You can leave the apply workable link blank until you have created it (see instructions below).
As soon as the posting is live on our website, People Ops will announce it on the next team call, post it in the #general chat channel and on Twitter. Also consider the additional advertising methods below as a means to communicate the open position to a desired audience.
All job openings must be posted on our careers page for at least 5 business days before we can make an offer; this includes all new positions and promotions.
Publicize the job
The manager should always ask the team for passive referrals for open positions. GitLab team members can refer candidates through our referral program
The employment team will always publicize the job through the following means:
Announce it on team call and on the #general chat channel.
Tweet the new job post with the help of the content marketing manager and team.
Request "soft” referrals by encouraging all GitLab team members to post links to the jobs site on their LinkedIn profiles.
Note: The employment team will advertise the job through the following sites:
PowerToFly Helping us connect with 100k+ women in tech
Hacker News Who's Hiring: On the first of the month, include a note for GitLab in the Hacker News thread of "Who's Hiring" . Template text: REMOTE ONLY GitLab - We're hiring production engineers, developers, designers, and more, see https://about.gitlab.com/jobs/ We're a remote only company so everyone can participate and contribute equally. GitLab Community Edition is an open-source Ruby on Rails project with over 1000 contributors.
Hacker News Jobs as a Y Combinator alumni we can post directly to the front page. The EA vault has credentials so ask an EA to post. Template text: GitLab (YC W15) is hiring XXX and more - Remote Only
On difficult or hard-to-fill positions, the employment team will use available tools to source for additional candidates. Please communicate with the employment team if sourcing is needed for a strategic, specialized, or difficult to fill position.
Closing a vacancy
To close a vacancy:
The employment team will clear the pipeline of candidates in all stages of application. Consider adding tags to candidates who were interesting but were passed over in this hiring process. Adding tags makes it easier to find them in Workable later on if you are recruiting for the same or a similar position.
Ask a Workable admin (People Ops) to close the position in Workable. People Ops: consider archiving the job posting to reduce number of positions GitLab is charged for by Workable.
The employment team will create a merge request, in which you remove the application URL for Workable, and set the listing flag in the jobs.yml file to open: false. See "vacancy creation process" for reference).
If the position was posted on any job site (i.e. Stack Overflow, PowerToFly) the employment team will email the partner or remove the position from that site.