Referrals - handling the volume
Referrals are a great thing! With that said, there has been an increased number of referrals as the number of roles we have open increase, the number of internal employees increase and the excitement of GitLab spreads! With this increase, means there are an increase of referrals to review for recruiters and an increase of employees reaching out to recruiters, CES and/or Sourcers to get updates or feedback on the referrals they submitted. @gl-recruiting would like to brainstorm on some ideas to make this process more efficient and less time consuming for the recruiting team.
- create a queue that internal employees can reach out to for updates @SVBarry
- Adding the handbook link to templates
- Update handbook with updated expectations (Important to have SLAs for referrals - ex: we will give them an update on their application within 7 days. If no update, provide a single place to follow-up - ex: Slack channel, email distro, etc. - 1-2 people manage this to ensure consistent responses and to make updates to handbook based on common questions, etc) @cwalsh11
- Pay more for "hot jobs" @cwalsh11
- Providing Feedback to Referrals
- Create a referral specific Slack channel @susanhill
- GitLab Service Desk I actually think creating a GitLab Service Desk may be better: @Ahoffbauer
- Allows us to work async
- Allows for confidentiality so we don't have to have them DM us the candidate's name and then just say please DM this person.
- Allows us to track people who request updates more often...
- Can create labels to track the reason why people are reaching out to track trends...
- Set up notifications for referrals so that it notifies recruiters to respond within a given timeframe @simon_poon