Once a candidate has provided their availability in Greenhouse, the Candidate Experience Specialist will utilize the internal hiring processes repository to determine scheduling needs. If the repo is outdated or you are unsure of the interview process, reach out to the recruiter.
Once a candidate has provided their availability in Greenhouse for the next step in the interview process, the Candidate Experience Specialist will utilize the internal hiring processes repository and schedule all interviews in accordance with the interview plan. The candidate is moved to the next step in the interview plan by a yes or strong yes scorecard. When scheduling multiple interviews, in the confirmation email screen, click on each calendar invite and edit the text to read: "Interview with (insert name of interviewer) at GitLab".
The Candidate Experience Specialist should be sure to inform the candidate that each subsequent interview is contingent on the success of the prior interview.
Any candidates who receive a no or definitely not scorecard should be discussed with the Recruiter and the Hiring Manager before declining.
For Directors and above with Executive Business Admins:
For the VP of Alliances, VP of Commercial Sales, VP of Customer Success, VP of Enterprise Sales, VP of Field Operations and the VP of Worldwide Channels:
If you have any questions about the process, please post in #eba-team slack channel and @ mention the EBA to the CEO.
Please ensure you have the guide chrome extension installed on your computer.
Preparing interviewers on Guide website
How to send out a Guide to a candidate for the first time via Greenhouse
How to send out an updated Guide if there was a change/reschedule
The CES team utilizes GitLab Service Desk to track incoming emails to the CES email alias.
There may be situations where the CES email is used to thank the team or to send a follow-up note. In those cases, we would copy the text of the issue to forward to the appropriate parties through a greenhouse profile at mention.
Once notified by the recruiter, the Candidate Experience Specialist will initiate a background check for the candidate. The Candidate Experience Specialist will continue to monitor the background check until finalized, utlizing the follow-up feature in Greenhouse to ensure the background check is complete and uploaded into BambooHR if hired.
For guidance on reviewing Background checks see this page.
US Candidates Only
US Candidates Only
Non-US Candidates Only
Our hiring process includes an optional step where candidates can request to meet with an TMRG team member. Candidates can request this at any time throughout the process, we will also proactively offer this to a candidate when they reach the reference check stage. Whether or not the candidate decides to take us up on this offer will have no impact on our overall hiring decision.
When a candidate requests to meet with an TMRG team member, their Candidate Experience Specialist will do the following:
As a GitLab team member taking part in these calls, we advise you to start with a short introduction to you and your role here at GitLab. From here, we advise you to let the candidate lead the conversation as the goal is for you to answer their questions and offer insight into how we work.
These calls don’t require you to submit a scorecard in Greenhouse. If a candidate mentions something that you see as a red flag (e.g. they outline a past action of theirs that goes against our values) or share something that would help us set them up for success, we advise you to share the details of this with the hiring manager for the role they’re interviewing for. It will be the responsibility of the Hiring Manager to review this and decide whether we need to alter the hiring or offer process for the candidate.
One person from the recruiting team (typically the Candidate Experience Specialists) will prepare the contract. While the Candidate Experience Specialist will prioritize a contract above other tasks, the expected turn around on the task is 1 business day. If the contract is time-sensitive, ping the CES team on the candidate's Greenhouse profile and provide context for the rush. If the Candidate Experience Specialist cannot meet the 1 business day they will inform the recruiter via Greenhouse and will provide context.
Yesand the specific details or
None. (Its important that it is not just a GitLab or Github link and more specific info.) - If the candidate has specified a
Yesand the specific details, make the People Experience team aware in our private group slack channel to kick off approval process.
Source & Responsibilitysection of the candidate's profile is correct to ensure accuracy in reporting.
people-exp_ces. The Contract, Greenhouse and BambooHR should reflect the same start date regardless of the actual onboarding date. However the GitLab Onboarding Tracker should reflect the actual onboarding date.
It is important that the Candidate Experience Specialist CES notifies the People Experience Team of any important changes regarding the new team member, which also ensures the new team members are handed off properly to the People Experience Team.
The Candidate Experience Specialist will set up a delay send email using the "GitLab Helpful Links - Checking In" email template in GreenHouse. The delay should be set up for halfway between the contract being signed and the start date.
If necessary you may cancel the email, which is now showing under the Email Candidate option.
People Experience Associate will create the onboarding issue and start the onboarding tasks no later than one week before the new team member joins. Should a contract not be signed prior to 4 working days from the start date, a new start date will be required.
For questions about the new team member's onboarding status, you can @mention them in the
#peopleops-confidential Slack channel.
For questions about the new team member's laptop, ping IT Ops in Slack. If the questions arise through email, forward the email to firstname.lastname@example.org and ping IT Ops in #it-ops Slack, and @it-ops-team too due to volume.
For candidates requesting interview reimbursment the CES team will partner with the Account Payable (AP) team to ensure requests are processed confidentially and in a timely manner. AP and the CES team utilize GitLab Service Desk to track incoming emails to the Interviews@gitlab.com email.
Under the Interview Reimbursement Service Desk set up the proper notifications
Additional process details can be found on the project README page.