This page is for information regarding the “backend” of the Referral Process.
People Connect will review the following guidelines to ensure the correct amount is being awarded with the One Time Payment in Workday.
Job
> Application Review
> Applied On YYYY-MMM-DD
Per the current Referral Submission Process, Team Members will submit referrals through Greenhouse if the vacancy is posted externally and via Issues if the vacancy is only open internally. When a new Issue appears, please do the following:
Confidential
.
+
> Add a Referral
.Required
Required
Required
Required
Required
Family Relationship
field on the Additional Details tab.Required
Required
Add this referral
to submit them.Details
tab, and scroll down to the Source & Responsibility section.Pencil
icon, then edit Who Gets Credit
with the name of the Referrer and click Update Source
.Email REFERRAL_NAME
in the right column and select the Default Referral Confirmation Receipt email template.
no-reply@gitlab
alias.CC
field.Send Email
.Our Inbound Sourcing team runs point on responding to questions related to referrals in the #talent-acquisition slack channel and ensures that the referrer is credited as the source of a referred candidate.
The Talent Acquisition Team uses the GitLab Service Desk to track incoming emails to the referral@gitlab
email. These emails will, in turn, show up as Issues
.
To set-up notifications for the Referral Service Desk Project, please do the following:
Bell
icon in the upper right corner (next to Star
and Clone
).Custom Settings
.New Issue
.To take action on Issues in that project:
Issues
in the left menu bar.
referral@
emails will be; any open Issues here will need to be addressed.Issue
.@RECRUITER
is responsible for this role and they’ll provide the candidate with an update soon."@RECRUITER
is responsible for this role and will provide you with an update soon."@-mention
the responsible Recruiter so that they’re aware an update is being requested.Our Talent Acquisition 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.
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 hiring efforts in your area.
A Talent Acquisition 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 ELF
template.Thank you again for submitting
CANDIDATE_FIRST_NAME
to theREQUISITION_TITLE
role.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 > Talent Acquisition 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_NAME
has 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 Talent Acquisition Operations & Insights Team Member will check to make sure that all submitted referral Issues are marked as Confidential
.
To do that, please take the following steps:
Closed
Issues.Confidential = No
and run the search.Confidentiality
section in the right column.