The speed with which we can grow our team is dependent on the rate at which we find qualified candidates, and the purpose of sourcing is to generate a large list of qualified potential candidates for our open roles.
Sourcing has proved itself to be a great channel for attracting the best talent. It allows us to grow GitLab and build an even more diverse team in the most efficient way possible, while also sustaining our culture.
Sourced - a candidate who is IQA (Interested, Qualifed, Available). This candidate has shown interest and is scheduled to speak with someone (Recruiter/Hiring Manager) at GitLab.
Prospect - a candidate that looks good based on the information we have available (LinkedIn, Blogs, Conference Talks, etc.). The candidate has been approached by the Recruiting team (but we do not have any response or anything scheduled with them) or has joined our Talent Community.
"Sourcing", in general, means that you don't know and would not be able to speak about the candidate confidently in a professional sense with GitLab. At best, your sentiment might be, "They seem qualified". If you'd like to start contributing to our sourcing efffort - we recommend you going through our internal Sourcing Guide, that contains a lot of useful sourcing tips & tricks and gathers together our team resources.
Note: If you know a candidate from school, previous companies, seminars… even among your neighbors or family members - please refer them by creating an
Issue in the Referrals Project
More information about the Referrals can be found on the Referral Process page.
For anyone that you do not have a personal relationship with, please add them as a Prospect in Greenhouse and keep in mind that Greenhouse is our single source of truth. Here's how to do that:
Step by step example: I've found someone who might be suitable for our Backend Engineer role, simply use their name or email address to check on Greenhouse to see their status –> Add them as a prospect on Greenhouse –> Once they replied with interests, please convert them into Candidates on the Greenhouse! You can also check out our Greenhouse Tips and Tricks document to find more information on Greenhouse usage.
About Sourcing Channels
The most efficient way to source candidates for any vacancy is to search through a professional network, such as LinkedIn, AngelList, etc. Professional networks make it easy to scan a person's skill set and professional background quickly and efficiently and are designed to present their best impression to potential employers.
We encourage our team members to think out of the box and source creatively! For some positions, other networks may prove useful as well - for example, we are looking for someone who has public speaking experience combined with specific tech expertise. Sourcer can go on Youtube and search for candidates who have spoken at the seminars or professional conferences before and try to search for the person's name and suitable ways to contact them.
About Reaching Out to Candidates
When you have identified someone as a good potential candidate, send their profile along with any requested information to a Sourcer so they can reach out to the candidate and add them to Greenhouse. You can check the Sourcer alignment here.
If you want to reach out to a sourced candidate directly you can refer to our internal Reach out Templates deck, check out the internal Sourcing emails repo or create your own message. Kindly discuss your communication strategy with your Sourcing partner to avoid duplication and poor candidate experience.
Take a look at these talent brand resources for the latest team member count, employer awards, blog posts, and more facts about working at GitLab. These resources are meant to help guide your outreach to potential candidates.
Engagement of Candidates within the Recruiting Team
The process of contacting the candidates are as per the following scenarios:
Diversity - In accordance to our values of diversity, inclusion and belonging, and to build teams as diverse as our users, Recruiting provides a collection of diversity sourcing tools here to expand our hiring teams’ candidate pipelines. If you have any questions on how to implement these resources into your current sourcing strategy or have suggestions for new tools, please reach out to the Recruiting team.
We're eager to provide hiring managers and all hiring team members with a LinkedIn Recruiter seat.
To upgrade your seat, please add your GitLab email to your LinkedIn profile, then submit an Access Request Issue using the
LinkedIn Access Request template within the Recruiting Operations project.
To integrate your LinkedIn account with Greenhouse, please refer to the Enabling LinkedIn Recruiter System Connect section on the Greenhouse page.
You can request one of the following seats (we recommend requesting a Recruiter seat):
Based on LinkedIn's research, passive candidates are more likely to respond to direct outreach from the hiring team member than from a recruiting team. That's why we're encouraging greater adoption and use of LinkedIn Recruiter company-wide.
New to LinkedIn? Use LinkedIn Boolean hacks spreadsheet. Follow the instruction on the sheet, discuss with your Sourcing partner the keywords.
Please reach out to your recruiter for tips on how to improve your LinkedIn profile, write an InMail, and use Projects.
To note, we won't be able to reimburse any LinkedIn seats purchased at your own expense.
Sourcing Session is a required step of the recruiting process for every role at GitLab. These sessions help us to ensure that we look for outbound talent and leverage our sourcing effort for all the roles we’re hiring for.
Once a new role is opened, Sourcer assigned to the role will discuss with Recruiter and Hiring Manager who should participate in the Sourcing session and schedule it within 5 business days after the kickoff call.
You can find more information about Sourcing Sessions on the Recruiting Process page.
As our company continues to see rapid growth, we need to aim to hire the best talent out there and we want all GitLab team members to partner with the Recruiting team on building the greatest GitLab crew! We ask you all to contribute by digging into LinkedIn or your favorite social media space and add candidates to the spreadsheet or LinkedIn project. By doing this, we are reaching out to people that are very closely aligned with the team’s needs and finding better-suited candidates.
Save the sourcing strings for future reference to the project to help generate new strings from different perspectives.
When you source a candidate and provide their information to our sourcing team, you can expect that they will receive an email or inmail asking them if they’re interested in talking about an opportunity to discuss the position. The sourcer will then upload their profile from LinkedIn to our applicant tracking system and tag their name as sourcer to follow their candidacy through the process.
We do try to personalize these emails or inmails as much as feasibly possible so that they are not impersonal or "spammy," and we rely on the team sourcing to identify relevant and qualified candidates to ensure these messages are as meaningful as possible.
How to source through LinkedIn our Greenhouse database
Simply add all your filters as described above in the LinkedIn Recruiter sourcing section. After setting up your search paramenters add one extra: “In ATS” - here add Greenhouse. This will show you all the people who match your search and are in our database AND also have a LinkedIn! Please note this will not show you absolutely everybody in Greenhouse.
Bonus Greenhouse sourcing tip You can download in bulk in an XLS file several profiles and you can run your searches in the spreadsheet. For this click on the blue “Export” button on the top of your search results in the “All candidates” section of a search result tab.
Teams might have different hiring criterias depending on technology, field, product area etc. This can also change with time. Sometimes we might need a candidate who needs a clearance or has multiple endorsements for Ruby, tenure at established/strong Rails companies, startup/product experience or has to meet our longevity requirements. To make sure you search is aligned with the specifics of that role/team check the kickoff meeting details of that role.
Here's an example workflow for sourcing Product Design candidates:
PROJECTSfrom the top banner. Here you will need to either start a new project by naming it
Product Designer - stage group, or open an existing project if the Recruiter has already shared one with you.
job titlesearch box on the left of the interface. You can input
Product Designerto search for anyone who has held this title in their current or past role. If you're following a tree ring strategy, you should select current from the dropdown. In an exisiting project, you can delete all the information as this will be saved by the Recruiter. You can then start your search using the
current companysearch box. Here, you can input the names of organizations you noted at the start of this process.
currentjob title, you may also wish to broaden the search by selecting
current or pastin the job title search field.
Visual Designer, or
Interaction Designer, if you believe someone with that title will be relevant for the role you're sourcing for.
Saving your search
If you're looking to come back to the same search at a later date, you can save the search string by selecting the
save icon. This is found next to
showing results for at the top of the search box.
When you wish to come back to the saved search, you can find it by opening
search history and alerts. Again, this is at the top of the search box on the left side of the screen.
Some things to keep in mind when sourcing Product Designers:
portfolioon their profile, it can found below their profile header, and above their background summary.
Enterpriseis a powerful boolean search modifier when sourcing for GitLab. Many product design candidates who have the type of experience we look for will list enterprise software, enterprise teams, enterprise products, or enterprise applications within their online profile.
Portfolio (insert candidate name)can successfully bring up the candidate's online work. However, this work may be out of date, not representative of the Product Designer's current skill set, or the work of somebody else (this is especially common when a Product Designer has a commonly held name).