Candidate Experience Specialist Responsibilities

1. You are here:
2. Hiring
3. Talent Acquisition Process Framework
4. Candidate Experience Specialist Responsibilities

On this page

• Candidate Experience Specialist Responsibilities
  • Best Practices
    • How the CES Team will run the Service Desk
  • Screening
  • Team Interviews
    • Technical Interview Scheduling
    • Executive Interview Scheduling
    • CES Slack Channel
    • Prelude
  • Zoom troubleshooting using Prelude when there is a zoom link error
    • Resource - Candidate Guide
    • If a Candidate Withdraws from the Hiring Process
  • Non-Disclosure Agreements
  • Background Checks
    • Initiating a Background Check through Greenhouse
    • Initiating a Background Check through Sterling Talent Solutions
  • Reference Check Forms
  • Send contract
  • Next Steps
  • Interview Reimbursement Process
  • Employment Offboarding

Candidate Experience Specialist Responsibilities

The CES team utilizes GitLab Service Desk to track all incoming requests to the CES team. If you are a GitLab team member and you have a request or question for the Candidate Experience team, email ces@gitlab.com and a ticket will automatically be created within the CES Service Desk. Please see the alignment page to learn more about which CES team member will be working on your requests.

Best Practices

• The CES team focuses their attention on incoming requests in the following order: CES Service Desk, individual emails, @ces Slack pings, and lastly Slack direct messages.
• You can find the priority list based on the type of request below:
  • 0 - Contracts
  • 1 - Candidate emails
  • 2 - Reschedules
  • 3 - Schedule Interviews
  • 4 - Offboarding
• The CES team utilizes a program called Guide to enhance the candidate experience and create a more transparent view into the talent acquisition processes. This program also allows us to rename interview subject lines to make them more candidate-friendly and succinct.

How the CES Team will run the Service Desk

1. Under this CES Service Desk Project set up the proper notifications
   • Click on the bell icon on the top right next to Star and Clone
   • Go to Custom Settings
   • Check "New issue"
   • Close out the window
2. On the left-side menu bar click Issues
   • This is where all our incoming CES emails will create an issue. You'll get an alert when someone sends an email to the CES email alias. Any "emails" that need to be addressed will be an open issue listed within this project.
3. Each CES will begin their workday by triaging issues within the Service Desk based on the identified priority list by adding the appropriate label to the issue and then will begin working on Level 0 priority requests and so on.
   1. Click on the new Issue
   2. Assign it to yourself on the right-side toolbar
   3. Read the Issue message
   4. If you need to respond to the "email" by adding comments to the issue, be sure to enter comments as you would an email to the candidate. Always assume that a candidate could be included in any email.
   5. If no action is needed and the issue has been solved, you may close it. Do not close issues until you have resolved the problem you are solving.

Screening

No action is needed by the CES team on this step. For additional information:

• Once a candidate is moved into the Screening stage, the candidate is automatically sent the GSIS.
• When scheduling a candidate for a screening call with a recruiter, the Calendly link is to be used. We will no longer use the "Request Availability" option for screening calls as this creates unnecessary manual work
  • If the candidate is sourced, the sourcer should send the Calendly
  • If it's an agency candidate or a referral where the recruiter may see the candidate first, the recruiter should send their Calendly link

Team Interviews

• When a candidate is ready for a team interview, the recruiter will request availability in Greenhouse using the email address of the CES team member they partner with. They will then click "Email the Team" on the right side of the candidate's Greenhouse page and send CES* the "CES Scheduling Request form".
  • If there are shorter timelines for roles as defined by the hiring team, CES needs to be made aware of those timelines for when interviews need to be scheduled. We will default to scheduling interviews at a minimum of 48 hours out to leave time for interviewer prep.
  • Reminder: When tagging @ces in Greenhouse, do not tag anyone other than the team in the same ping as it will add those users to the Service Desk project.
• If no response within 48 hours, CES will send a follow up request for availability and set the due date of the issue to 24 hours after the next email to check for availability again.
  • After the 2nd email to candidate with no response, the CES will make the Recruiter aware of the no response and no longer attempt to receive availability. They can close the issue temporarily, and reopen if the Recruiter receives a response from the candidate.
• After availability is received, CES will schedule interviews based on the interview plans in Greenhouse and will track preferences within the CES Service Desk repo.
  • CES will be using the Zoom integration with Prelude for interviews
  • After the candidate has provided the availability, as an optional step the CES team members can send the Candidate First Touch Email from Greenhouse if there are scheduling challenges and are pausing on sending the Guide for 24 hours.
• This email is sent to inform the candidates that their interview scheduling is in the process and to ensure better engagement with the candidates.
• If CES sees an alert to merge applicant profiles, and those profiles are a match (candidates' email address, phone number, or resume matches), they will merge the applicant profiles. Visit People Technology and Operations page for instructions.
• CES will send interview confirmations via Guide
• CES will not automatically schedule next interviews based off of scorecards
  • The Recruiter or Hiring Manager will need to follow the same scheduling procedures as above in Greenhouse to request scheduling assistance on the next round of interviews.
  • Any candidates who receive a no or definitely not scorecard should be discussed with the Recruiter and the Hiring Manager before declining.

Technical Interview Scheduling

Certain positions require technical interviews (i.e. Ruby on Rails, Golang, Frontend, etc) where candidates are asked to demonstrate their knowledge and skills. Technical interview requests can be identified within the schedule request ticket as recruiters will utilize the following format: "Technical Interview, type of interview - 90 minutes".

Important to Note:

• These interviews are 90 minutes in duration
• Candidates must submit a GitLab username before CES can schedule their interview
• Interviewers and candidates need time to prepare prior to the interview, therefore interviews will be scheduled 4-5 business days out as the merge request will be sent by the interviewer 2-3 business days out.

To schedule a technical interview, CES should follow the process outlined below:

• When a candidate successfully reaches the Team Interview stage the recruiter will send the availability request email to the candidate.
  • If the candidate did not submit a GitLab username during the application or screening stage, the recruiter will also send the GitLab Username Form (this will be found in the Team Interview Stage or Evergreen stage). This generates an email to the candidate requesting they fill out the form with their GitLab Username.
• CES will receive two separate tickets to the CES service desk:
  • CES will immediately receive the scheduling request from the recruiter, and;
  • The completed GitLab Username form. This will only come into the service desk once the candidate replies to the email, and the username will automatically be added to the Details tab of the candidate's profile under Details > Other. CES should check that the GL username is valid and ensure that the GL username is in a URL format.
• Once CES has received and confirmed that the candidate’s GL username is valid, the CES team member can proceed with scheduling the interview in Prelude. Prelude processes can be found here.
  • Note: CES has specific “pools” of interviewers to use in Prelude when scheduling technical interviews. Unless advised otherwise by the recruiter, please use “ruby on rails”, “frontend” and “golang” pools when selecting an interviewer for these specific interviews.
• CES will then open the Guide extension in Greenhouse
  • Under Guide Process click Team Interview. Then click the interview you just scheduled. You will see a section to “add a description”. CES will insert the appropriate text expander snippet here. This provides the candidate with additional information about what they can expect for their technical interview.
• CES will proceed with sending the Guide. Guide processes can be found here.

Executive Interview Scheduling

The process for scheduling executive interviews should always be followed from here.

If you have any questions about the process, please post in #eba-team Slack channel and @ mention the correct EBA. You should include a link to the #eba-team Slack channel thread in your issue so you know where to find updates.

CES Slack Channel

TA/CES will be using a custom slack channel to consolidate all requests directed towards CES from GitLab Team Members who participate in interviews.

Slack Channel: #interview-help-ta

IMPORTANT: Please DO NOT use candidates full names in the channel. Instead, please use their initials and/or link to their GH profile when communicating.

This channel will be monitored by CES team members on a rotating schedule to accommodate varying timezones.

How Gitlab Team Members will utilize the Workflow within #interview-help-ta

• Open slack channel #interview-help-ta
• Click Shortcuts button in the bottom left corner (looks like a lightning bolt)
• Click “CES HelpDesk”
• Click “Request Category” drop down and choose category pertaining to specific request
• Click “Urgency of your Request” drop down to let CES know the importance of your request.
• In “Details” box please provide CES details on what you need. IMPORTANT: please do NOT write candidates name. Instead use initials and link the candidates GH profile.
• Requests sent to CES that include a candidates name will be removed.
• Click “Submit”

CES team members will respond to Gitlab Team Member workflow requests in the channel directly themselves and/or ping the designated CES to assist. Once the request is handled, the CES team member will mark the workflow with a green check mark indicating that the request was actioned and resolved.

The purpose of this private Slack Channel is to:

• Condense hiring slack channels that CES has to monitor.
• Urgent situations will be handled quickly as CES will alternate times to monitor channel.
• One channel for all GL team members to reach CES
• Allows contract team members access to all pings for CES
• Will help distribute workload for CES pings between all of CES

This will allow:

• Quicker response time to requests from GitLab Team Members which will assist in improving interviewer experience.
• Streamline process for CES to receive and action Urgent requests from GitLab Team Members.
• Provide a more accessible point of contact for CES rather than an email.
• Will assist in providing coverage for when CES members are offline or on PTO.

Prelude

Please ensure you have the Prelude Chrome Extension installed on your Chrome Browser.

Prelude processes can be found here.

Zoom troubleshooting using Prelude when there is a zoom link error

When a candidate or an interviewer reaches out to CES via slack / email / Guide chat with a zoom link error, the CES can follow the below steps to create a new zoom link through Prelude in under 2 minutes.

1. Open Prelude, go to the interviews tab, search for the candidates name.
2. Click on the candidate’s name and interview title. This would open up a smaller tab with a pencil icon on the right hand side.
3. Once you click on the pencil icon, a new pop up window will appear with the interview details. Delete the zoom link and password from the body of the email and the drop down bar.
4. Click Add zoom meeting and Choose “other” as a reason for updating this interview. Apply the changes and send the updated invite. This will send a new calendar invite to the interviewers.
5. Go to the GH profile; click “ Email Candidate”. Choose the template - “ Zoom Link Troubleshooting” and send the email to the candidate. The interview details with the new zoom link will be auto populated. Please be sure to delete any other interviews listed in the email other than the one with zoom link error. All this can be done under 2 minutes with practice!!

Resource - Candidate Guide

Please ensure you have the guide Chrome extension installed on your Chrome Browser.

Guide processes can be found here.

If a Candidate Withdraws from the Hiring Process

If a candidate emails the CES Service Desk stating they would like to withdraw from the interview process, the CES should respond to the candidate's email (not the Service Desk ticket) and cc the recruiter (if the recruiter isn't already on the email). The CES response should not say anything definite as there may be a chance for the recruiter to reel the candidate back in. A basic response is below:

Hi Candidate Name, thank you for your email. I have cc'd your recruiter in this email and if there are any additional questions, they will be in touch.

The CES should also tag the Recruiter in the Greenhouse profile of the candidate who withdrew.

The only exception to this should be for executive roles. Please just forward the withdrawal email to the Executive Recruiter and they will handle any follow-up.

Non-Disclosure Agreements

To send a Non-Disclosure Agreement (NDA) to a candidate, Recruiters should ping @ces in Greenhouse. CES can then log into Docusign, select "start" and "use a template", and then access shared templates. Once the NDA has been returned, upload the document in the "details" section of Greenhouse. Download this document from DocuSign as separate files, and only use the NDA itself (the summary is not necessary).

Background Checks

GitLab will obtain references and complete a criminal background check with employment verifications.

• If the candidate is located in Belgium and the role is not Grade 9 or higher, the CES or Recruiter (whoever kicks off the reference check process) should send the job requisition to the legal team via the #legal Slack channel during Reference/Background check phase to determine whether or not the role is a position of trust.
• The recruiter should select "Email the team" and send the "CES Start Contract Request" email to CES* to initiate the offer letter and background check processes after the verbal offer has been made.
• The Candidate Experience Specialist will initiate a background check and start the contract process for the candidate.
• Background check results will be received by the Senior Background Check Specialist and escalated to Team Member Relations and Legal where appropriate

For additional information on reviewing Background checks see this page.

Initiating a Background Check through Greenhouse

1. Log in to Greenhouse and go to the candidate's profile.
2. Click the Private tab.
3. Click Export to Sterling.
4. Click Complete Report, which will redirect you to the Sterling website.
5. Click Invite, and then follow the steps below starting at the second step.
6. If the candidate is located in New York City and you have already initiated Step 1, please order NYC Step 2 instead of a traditional US check.

Initiating a Background Check through Sterling Talent Solutions

1. Log in to Sterling and E-invite the candidate by inputting their email address.
2. Under "Applicant Information" enter in the candidate's first and last name, as well as their email address to confirm.
3. Next, select "GitLab" from the "Job Position" drop down menu.
4. Next, select the name of the country where the candidate is located. If the candidate is located in the US, the package will be called Comprehensive Criminal with Employment. If the country is not listed, choose Global Screening
5. If the candidate is in Finance or Accounting, and are not located in Japan, Germany, Ireland, Spain, or Russia (which already include this check), you should also select "A La Carte" from the "Screening Packing" and choose Extended Global Sanctions. Then click "Add".
6. Finally, scroll to the bottom of the page and click "Send"
7. Make a note in the Greenhouse profile that the Background Check has been started

Reference Check Forms

Prior to giving an offer, Recruiters are required to request references and other offer-related information by sending a form in the Reference Check stage. There are a few versions of this form available on every job based on the country where the candidate is located. When CES receives a form in the Service Desk, there are 3-4 fields to look at: NYC status, PIAA (Employee Invention Assignment Agreement), Outside Work disclosure, and TMRG requests.

NYC Location

USA Reference Check forms only: It's important to note that the USA Reference Check form should be sent to the candidate and Step 1 should be completed before creating an offer. If the candidate selects “Yes” to indicate that they are located in NYC, you will need to complete a two-step background check process:

1. CES service desk receives a ticket indicating that the candidate has submitted Reference Check Process Information - USA form. CES notes that the candidate has selected “Yes” for the NYC location question.

2. CES will add the text expander snippet refchecktodo into the ticket to help guide them through the process. CES will add the “NYC BGC” label.

3. CES will go to https://sterlingcheck.app/dashboard/#/dashboard/. It is important to use this version of Sterling because it allows us to edit the email template that is delivered with the check.
   • Select NYC Step 1 screening package. You will need to fill out the Location of Employment field as San Francisco, and the Projected Salary field with the candidate's salary (this range can be found in the “Approvals” tab of the candidate’s GH profile). Click “next”.
   • On the next page, under "Email Content", in the drop down, select "NYC Step 1" template.
   • Scroll to the bottom of the page and input the candidate’s full name and email address. Send Invite.
4. CES will add the “Pending” label and due date on the ticket. Create a follow-up reminder in Greenhouse 1 business day out to check if there is an ETA.
   • Once an ETA is set in Sterling, create another follow up reminder in greenhouse for that ETA date. Please note that the results may come in earlier than the ETA.
   • Please contact the Senior Background Check Specialist for any BGC escalations. e.g "Status: Unperformable" or "Status: Consider"
5. This process has been added due to NYC law, which separates the employment verification from the criminal check. Keep an eye on the status of the Step 1 screening results in Sterling. While we are waiting for Step 1 to be cleared, the recruiter can provide the candidate the verbal offer, begin creating the offer in Greenhouse and going through the approval stages. Recruiters can send the contract request ticket to CES when they are ready, although, CES cannot send a written contract to the candidate until Step 1 has been cleared.

Tip: when the CES desk receives the contract ticket, add the NYC BGC label immediately to remind yourself and your team members that this candidate is undergoing the NYC two-step background check process.

• When checking BGCs in Sterling initiated by other team members, be sure to select "Entire Organization" in the top left section of the Sterling dashboard.

1. Once the recruiter has sent CES a contract ticket, CES will then complete NYC Step 2 of the background check through the Greenhouse integration. Once in Sterling, select the NYC Step 2 screening package and send. Note: if it is a Finance position, you will also need to add the A La Carte - Extended Global Sanctions check.

Troubleshooting Tip: If you receive an "expired" error when initiating Step 2 through the Greenhouse Sterling integration, you can navigate to the Sterling Direct dashboard. On the right hand side, under "E-Invite Applicant to Background Check", enter in the candidate's email address and select "Invite".

• Fill in the applicant's information
• Under "Order Information", select Gitlab as the Job Position and under "Screening Package" select NYC Step 2.
• Then scroll to the bottom right of the page and select Send.

PIAA

In the form, you'll find a question that informs the candidate that they will be required to sign an Employee Invention Assignment Agreement. They are asked for invention disclosures. If they state "none" or "n/a", you can skip this step. If the candidate discloses any outside activities, CES will take the following steps:

1. Email the Team through Greenhouse using the template CES - PIAA Disclosed.
2. Fill out the email template with the hiring managers name and a screen shot of the disclosed information. This email will be sent to the People Connect Team at people-connect@gitlab.com. Please rember to put the name of the candidate in the email subject line. People Connect will follow our standard process per the internal handbook. Reach out to legal_employment@gitlab.com with any questions about things written in a PIAA.

Outside Work

If the candidate writes "none" or "n/a", you can skip this step. If a candidate discloses any outside activities, CES will need to take the following steps:

1. In the ticket issue use "refchecktodo" text expander snippet to track progress and add the "Outside Work Disclosure" label.
2. Email the Team through Greenhouse using the template CES - Outside Work Email, you can either copy and paste what the candidate has disclosed or you can attach a screenshot of the "outside work" section of the form. Send this email to the Hiring Manager. The Recruiter, Coordinator, and Team Member Relations will automatically be CC'ed.
3. Await approval from the Hiring Manager and/or TMR. Once you have approval, take a screenshot of the email conversation (make sure to capture both the work disclosed and the approval from the HM and/or TMR). Save screenshots to a folder on your desktop.
4. Once the candidate has been marked as hired and their profile has been created, CES will need to upload the approval screenshots to WorkDay. In WorkDay, search the candidate's name then navigate to the "Personal" tab. Click on "Documents" and then "Add". Upload the correct screenshots, under the "Document Category" drop down, select "Contract & Changes - Confidential (No Employee View), click "Upload".

See more information about this process here.

TMRG Conversations

Our hiring process includes an optional step where candidates can request to meet with a TMRG team member. We will offer this to a candidate when they complete their interview process before an offer is made. Whether or not the candidate decides to take us up on this offer will have no impact on our overall hiring decision.

All current TMRGs have agreed to take part in this process. You can find the group list here.

When a candidate requests to meet with a TMRG team member via the Reference Check Form, the Candidate Experience Specialist will do the following:

1. Reach out to TMRG volunteers for this call in the dedicated #candidate_tmrg-call slack channel.
   • Select Shortcuts button - looks like a plus sign with lightening bolt
   • Fill in appropriate details
     • Which TMRG would this canidate like to speak with?
     • Where is the candidate located?
     • What role is this candidate interviewing for
     • Click Submit

2. Once submitted, the request will ask volunteers to reply with their Calendly link and LinkedIN Profile (optional) for us to share with the candidate.

3. Once a volunteer has been found the Candidate Experience Specialist will email the candidate the 'TMRG Opportunity' email template in Greenhouse. The CES will update the template with the Team Members name, Calendly Link and LinkedIN profile if provided and then send to candidate.

4. If a volunteer has not been found within 24 hours the CES team member will reach out to the TMRG in their dedicated TMRG Slack Channel.

5. If a volunteer still has not been found within 24 hours of the second request, the CES will reach out to the TMRG lead(s) and request assistance with scheduling. If a volunteer has not been found within 3 business days of the request, the CES will ask the TMRG lead to take part in the conversation.

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 shares 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.

Send contract

See Candidate Experience Specialist Contract Processes section of the handbook

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, please provide context for the rush. If the Candidate Experience Specialist cannot meet the 1 business day they will inform the recruiter and CES manager via Greenhouse and will provide context.

Recruiters should make themselves familiar with the basic knowledge of the contract processes that can be found on the CES Contract Processes page and the Contracts, Probation Periods & PIAA page, as well as the Employment Contracts page in the internal handbook.

1. Check all aspects of the offer:
   • Do we have the new team members' legal name in their profile?
     • _It is extremely important to enter the team member's full legal name (as much as it is known before visually seeing a legal ID). Full legal name should be provided for the background check process. It is important to be as accurate as possible, including the person's full legal name as well as any accents used for their name.
   • Is the new team members' address listed on the details page?
   • What contract type and entity are required based upon location and offer details?
   • Is all necessary information (start date, salary, location, etc.) up to date?
   • Is the start date one that is not a "no start date" and provides an adequate amount of time for People Connect and IT to have sufficient notice? Ideally, we are providing 10 days notice, but the teams can work with less if we let them know.
   • Has the signatory been determined by the Candidate Experience Specialist and updated?
   • Has the Entity been selected based on the New Hire's location? If the job title has Federal or PubSec included, please check with the Recruiter if they set up the contract as Inc rather than Federal LLC to confirm.
2. Generate the contract within Greenhouse using a template based on the details found in the offer package.
3. Contact the recruiter or new team member to gather any missing pieces of information (note: the address can be found on the background check information page).
4. If the contract was created outside of Greenhouse, ensure that the contract has been reviewed and approved by a member of the Legal team.
5. Stage the contract in DocuSign from within Greenhouse, which emails the contract to the signing parties, with the recruiter, talent acquisition manager, and the hiring manager cc'd. It will be sent to the designated signatory as previously determined in Offer Details.
6. Before marking the candidate as hired the Candidate Experience Specialist will reject the candidate from any other active roles including roles for which they are a prospect (without sending a rejection email). NOTE: If this step is skipped, the profile will not be exported to Workday when the candidate is marked as hired.
7. Before marking the candidate as hired on all candidates, the CES will make sure that the profiles were merged (for internal candidates, this will be indicated if the candidate shows their original Hired inactive role). View candidate merge instructions. NOTE: If this step is skipped, it will create a duplicate profile exported to Workday when the candidate is marked as hired.
8. Before marking the candidate as hired the CES will ping the recruiter and give them 24 hours to contact/reject all other active candidates. Once this is complete, the CES can proceed with hiring in GH (if candidates are still present in req, select the "keep open" option when setting candidate to hired. This will trigger a new opening to ensure candidates are still present in req)
9. Before marking the candidate as hired the CES will verify if the listed Recruiter and Coordinator in the Details > Source & Responsibility section of the candidate's profile is correct to ensure accuracy in reporting.
10. The CES will mark the candidate as "Hired" in Greenhouse: when prompted, select the option to close the req. Please note, the new hire's Workday profile will be generated automatically.
11. For internal hires ONLY - the CES will send the automated email template labeled "Internal Hiring Survey". You can also cancel the survey that will appear automatically when the candidate is marked as hired.
12. The Candidate Experience Specialist will email the new team member the Welcome Email from Greenhouse with a cc to IT Ops, the Hiring Manager and the Recruiter. For new team members in USA, use 'GitLab Welcome - US only' template. For team members located outside the US, use 'GitLab Welcome - non US' template
    • Instructions on the Notebook Ordering Process are included with this email.
13. Should the start date change after the welcome email is sent please see the required steps here.
14. Exception to the start date and onboarding date alignment: If a new team member requires a specific start date for legal reasons (cannot have break in employment) but onboarding on that specific day is restricted (because of Public Holiday, Family & Friends Day, etc.), the Candidate Experience Specialist can notify the People Connect Team in the private Slack channel people-connect_ces. The Contract, Greenhouse and Workday should reflect the same start date regardless of the actual onboarding date.  

It is important that the Candidate Experience Specialist notifies the People Connect Team of any important changes regarding the new team member, which also ensures the new team members are handed off properly to the People Connect Team.

Next Steps

People Connect Specialist will create the onboarding issue and start the onboarding tasks no later than two weeks before the new team member joins. Should a contract not be signed prior to 10 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 #people-connect-ces 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 itops@gitlab.com and ping IT Ops in #it-ops Slack, and @it-ops-team too due to volume.

Interview Reimbursement Process

For candidates requesting interview reimbursment the CES team will partner with the Accounts 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

• Click on the bell icon on the top right next to Star and Clone
• Go to Custom Settings
• Check "New issue"
• Closeout the window

Additional process details can be found on the project README page.

Employment Offboarding

When team members depart Gitlab, People Connect will create an offboarding issue. The CES team is responsible for completing tasks under the "@gitlab-com/gl-ces" section. Please note that offboarding issues are time sensitive and should be completed by the due date set on the issue. Completion of these tasks also ensure Gitlab remains compliant.

1. Go to Employment Issues where the offboarding issues can be found. In the search bar, filter issues by the "CES: To Do" label and work on the issues by due date. Once you open up an offboarding issue, navigate to the "@gitlab-com/gl-ces" section and complete the following steps.

2. Open Google calendar, select the "Interview Calendar", and type in the team member's name in the search bar at the top. Ensure the team member offboarding isn't in any active interviews. If applicable, post in the ces-team slack channel the departing team member's name and list the interviews they are currently scheduled for. Advise the CES team member to work with their recruiters to review any other interview plans and update accordingly. Any interviews that have been grayed out on the calendar, have passed already.

3. Check any interview plans and reqs that the team member might be on by searching the team member's name under Users in Greenhouse. When searching the team member's name, select the profile with the team member's GitLab email address; this will navigate to their Greenhouse profile settings.

Under "Permissions" check what the team member's permission level is. If permissions are anything other than "Job Admin: Hiring Manager" (i.e. "Basic" or "Job Approver") you can skip to step 4.

If the permission is listed as "Job Admin: Hiring Manager", check if the job req title has "Closed", "Draft", or "Template" in it. If so,you can skip to step 4.

Please note you may encounter a "Job Admin: Hiring Manager" who has both "closed" and active job reqs. If there are active job reqs you must take the following steps:

• Copy and paste the job req title into a new Greenhouse window and search
• Select the correct job req by ensuring the req#s match (i.e. 7458)
• Select Job Set up and navigate to the Hiring Team section
• Please ensure that the hiring manager position has been filled by another team member. If the hiring manager section is empty or still shows the team member who is offboarding, reach out to the CES coordinator listed and advise the CES team member to work with the recruiter to find a replacement hiring manager & update interview plans.

1. If the team member offboarding is listed under an Engineering department (highlighted in yellow), you will need to search the hiring repo and update (if applicable). This usually pertains to any team members who were a part of interviewer pools (e.g Ruby on Rails, Frontend technical, Backend and etc.) Please note that only the backend and frontend hiring repos list technical interviewers.

• While in the Engineering hiring repos, select Backend / Interviewers.md / search the team member's name using their gitlab username (i.e Eric Johnson = ejohnson). If they do not show up, there is no further action needed.

• Next, navigate back the Engineering hiring repo and select Frontend / 3- Technical Interview / Interviewers.md / search the team member's name using their first and last names. If they are not listed, there is no further action needed.

If the team member is listed in any of the engineering hiring repos, remove their name from the hiring repo and submit changes through a merge request e.g "Removed John Doe from list of ruby on rails technical interviewers".

1. Once all steps have been completed, navigate to the right hand side of the offboarding issue, remove the "CES: To Do" label, disable notifications, and leave a comment/ notify "Recruiting Ops". (e.g @ destinyreyes ces tasks done)