This page is for information regarding the “backend” of the Referral Process.
During the onboarding process, a People Experience Associate will complete the following steps if a new team member was referred by current team member.
Applied On YYYY-MMM-DD
90 day + Hire Date
Bonus Amount: Review above
Bonus Type: Referral Bonus
Bonus Comment: "Referred (New Team Members) - submitted on (submit date) and add if location factor or underrepresented group"
Per the current Referral Submission Process, Team Members will submit their referrals via Issues. When a new Issue appears, please do the following:
Add a Referral.
Add this referralto submit them.
Detailstab, and scroll down to the Source & Responsibility section.
Pencilicon, then edit
Who Gets Creditwith the name of the Referrer and click
REFERRER_NAMEfor Req #
@-mentionthe requisition's Recruiter.
Email REFERRAL_NAMEin the right column and select the Default Referral Confirmation Receipt email template.
The Recruiting Team uses the GitLab Service Desk to track incoming emails to the
referral@gitlab email. These emails will, in turn, show up as
To set-up notifications for the Referral Service Desk Project, please do the following:
Bellicon in the upper right corner (next to
To take action on Issues in that project:
Issuesin the left menu bar.
referral@emails will be; any open Issues here will need to be addressed.
@RECRUITERis responsible for this role and they’ll provide the candidate with an update soon."
@RECRUITERis responsible for this role and will provide you with an update soon."
@-mentionthe responsible Recruiter so that they’re aware an update is being requested.
Our Recruiting Team occasionally organizes Referral Roundup Sessions.
The objective of theses sessions are to gather referrals, region-specific information about where you're based, and teach you skills related to sourcing and Greenhouse.
We'll invite Team Members who are based in areas with a location factor less than or equal to
.58 to theses sessions.
Each session will have a corresponding Issue linked and in that, we ask that you please add information regarding appropriate companies to source from, local meet-up groups, conferences, job boards to advertise on, and any other information you believe will be beneficial to our recruiting efforts in your area.
A Recruiting Team Member will attend these sessions, so they be able to address any questions that arise on sourcing, LinkedIn, or Greenhouse.
In the event that a Referral is rejected based on their location factor the following steps will need to be taken by the requisition's Recruiter:
Referral Declined - Not ELFtemplate.
Thank you again for submitting
Unfortunately, we’re unable to move forward with
CANDIDATE_FIRST_NAME’s candidacy right now because they are located in a higher location factor area. With our outbound hiring model, the > Recruiting team is focused on building a more diverse team in the most efficient way. This allows us to support our all-remote vision: to spread opportunity to underserved locales, and to influence the increase of wages for remote work outside of metro areas.
CANDIDATE_FIRST_NAMEhas received an email from our team explaining this. We’ve also added some clarity about this in the Referral Submission Issue Template now to be sure team members consider this before they submit their referral.
We appreciate your understanding and hope you’ll continue to refer talented people to GitLab!
Once a week, a Recruiting Operations & Insights Team Member will check to make sure that all submitted referral Issues are marked as
To do that, please take the following steps:
Confidential = Noand run the search.
Confidentialitysection in the right column.