To note, you don't need to select an "Office," as this will limit the vacancies you're able to select.
Complete the required fields on the Referral In-Take Form.
Please provide context as to why you're referring the candidate (i.e. why would they be great addition to the GitLab team?).
If you don't have their resume, please include a link to their LinkedIn profile.
You can stay up-to-date on the status of your referral(s) in the My Referrals section of your Greenhouse dashboard. If you have any questions regarding your referral, please sent an email to the referrals@domain. Please note that the Recruiting Team is unable to provide candidate-specific feedback to Referrers (i.e you); only to the Candidate themselves. You can expect Referrals to be reviewed by the Hiring Team within 10-days of their submission.
Although we place special emphasis on Referrals, we treat Referral interviews the same as we do non-Referrals. Referral interviews should not be more or less demanding than any other interview.
To prevent wrongful hires, Referrers need to keep their bar high. Interviewers and Hiring Managers should avoid bias based on the Referrer's status. There should be no favoritism based on previous experience working with a Referral after the candidate is hired.
Referral Bonus Payout
For details regarding the Referral Bonus Payout, please visit this page.
Common Referral Situations
Your Referral already submitted an application.
In the event that your Referral already applied, please send an email to the referrals@domain. In that email, please answers all the questions outlined in the Referral In-Take Form. To reiterate, Referrals should be submitted with a personal conviction that they'll be a great addition to the GitLab team. After receiving that, the appropriate Team Member will look into updating the Candidate's source information.
Your Referral was referred by someone else.
In the event that your Referral was submitted by someone else, the first Team Member to have submitted the candidate will be considered their Referrer.
In the event of multiple Referrers claiming ownership on a similar vacancy, it will be up to the Referrers to work out how to split the Referral Bonus and inform the Recruiting Ops Team of the compromise.
A member of the Recruiting Ops Team will notify the Referrers of such a scenario in an Issue for the compromise to be made.
If you referred the candidate to dissimilar vacancy, then you would be named their Referrer for the specific vacancy.
Other scenarios to be mindful of:
If the Referrer is part of the Hiring Team they'll…
… recuse themselves from interviewing the candidate and the Hiring Manager will choose a replacement Interviewer.
When a Referral is from a Referring Manager they…
… may choose to move the candidate on in the interview process, even if the candidate received a "no" from a fellow Interviewer - we don't operate on a single-veto basis.
… will review all information and feedback about the Referral (giving both positive and negative feedback fair consideration) and will make the final hire or no hire decision.
For any additional questions, please email referrals@domain.
How to Respond to Referral Update Requests
The Recruiting team utilizes GitLab Service Desk to track incoming emails to the referral@domain email.
Click on the bell icon on the top right next to Star and Clone
Go to Custom Settings
Check "New issue"
Closeout the window
On the left-side menu bar click Issues
This is where all our incoming referral@ emails will create an issue. You'll get an alert when someone sends an email to the referral@ email. Any "emails" that need to be addressed will be an open issue listed within this project.
Click on the new Issue
Assign it to yourself on the right-side toolbar
Read the Issue message
Add the appropriate label
Look up the candidate in Greenhouse if applicable.
Include the GreenHouse profile link in the comment.
Respond to the "email" by adding comments to the issue (be sure to enter comments as you would an email to team member asking for the update, they see all communication on the issues). Example responses:
Dear x, thank you for reaching out for an update on your referral. Per our SLA please make sure you give us 10 days to review the submission. @recruiter's name is responsible for this role and will provide the candidate with an update soon. (insert Greenhouse link)
Thank you for the referral. @recruiter's name is responsible for this role and will provide you an update soon. (insert Greenhouse link)
Be sure to at mention the recruiter on the req so they are aware an update is being requested.
If this one comment address the entire message add a comment and close the issue. If the one comment does not address the entire message then only select comment.
The Recruiter would reassign the issue to themselves once they pickup the communication and add any applicable labels.
The assignee should close the issue when communication is complete.