Purpose: The Recruiting Process Framework for Talent Pools provides guidance on the talent pool process so the recruiting team can efficiently build a talent bench before we need it
Anyone on the Recruitment Team can provide sourcing support for talent pools. The focus should be P3 and P4 Pools. (P0, P1, and P2 are reserved for active REQs) You can review active talent pools here. You may engage with the Recruitment Leads/Managers to verify pool priorities. If the Pool is a priority, use the Hiring Repo to learn more about the Pool profile.
Recruiting Team members should add potential matches to the appropriate Talent Pool in Greenhouse and make use of the appropriate tags to ensure the ability to easily filter prospects for specific job profiles, locations, etc. By default, all new prospects will land in prospect stage “no stage specified”.
You are encouraged to find top talent using a variety of different sourcing avenues, with LinkedIn and GitLab Talent Community being the most used and efficient ones.
While LinkedIn projects can be used, all approached prospects should be added in Greenhouse as prospects. Greenhouse is the source of truth. Every sourced prospect should have the name of the person who sourced them in the Source field. If a Prospect was sourced by a Recruiting Team Member from the Talent Community, that user will need to manually update the candidate's source information.
There are multiple ways to add the candidates, as follows:
How to add prospects to Talent Pools:
If you are helping source for a talent pool please verify the prospects you find are best qualified before reaching out to them.
The assigned Recruiter(s) to the pool have a 7 day SLA to review prospects in prospect stage “no stage specified”.
Once added to the appropriate talent pool and marked as "Qualified", the Recruiting Team member who found the prospect should engage the prospect and change the prospect stage to "Contacted". The message should clearly indicate that we do not have immediate opportunities, but are looking to start a proactive relationship.
Use our reach out templates or create your own messaging for reaching out to candidates
If you are reaching out to a pool of prospects, please be sure to check for duplicate prospect profiles prior to sending out mass communications. Duplicate prospect profiles occur when candidates join the Talent Community on multiple occasions. Although duplicate prospect profiles are automatically merged by Greenhouse, if they are still being considered as a prospect for multiple submissions, they will be sent a communication for each of their submissions. Be sure to select
Stop Considering as Prospect for any duplicate prospect profiles that are identified prior to sending out mass communications.
To send out a mass communication to the general Talent Community
Update Prospect Pool and Stage
If the prospect responds with interest, the person who found them will collect the prospects email address and will update the prospect stage in Greenhouse from “Contacted” to “Nurture”.
It is required we capture the following information in Greenhouse for all prospects converted to the "Nurture" stage.
Keep in mind, Tags can take care of other key pieces of information we may want to include on a prospect's profile.
If the prospect wants to talk with someone at GitLab to learn more about future opportunities, the person who found them will send them the Calendly link of the assigned Recruiter for the Talent Pool so a brief 15-20 "career conversation" call can be set up. Not all prospects who get moved to “Nurture” have to complete a call.
The person who completes the "career conversation" call will add brief notes to the prospects profile in Greenhouse and add the tags "Check Activity Feed" and "Had Video Chat" to the prospect's profile. If the person who completes the "career conversation" call considers the prospect to be great overall match to GitLab they will add the “Top Candidate” tag as well. If the prospect should no longer be considered as a prospect after the call, select the option to “stop considering as a prospect”.
Prospects whose prospect stage in Greenhouse is “Nurture” should receive a monthly message from GitLab.