The People Group Engineering team aims to reduce as much manual work as possible. One of the areas we have done this, is everything related to the employment automation flow.
Note: this section only discusses items in the offboarding where People Engineering was involved. You can read more about promotions and transfers at GitLab on this handbook page
Once a People Connect Team member runs the career mobility command through Slack, this triggers a pipeline in the employment project, which will run the job transition, and reply with a link to the newly created Career Mobility issue.
The issue will be automatically assigned to the following people:
This issue is then added to the team member's epic.
Sometimes, issues are created by humans instead of a bot, in this case they can forget to mark the issue as confidential. We run a daily pipeline to mark issues as confidential in the training project. This includes manager and interview training issues as the employment project is internal to GitLab team members anyway.
This is the same as the manager an interview training issues we create for onboarding. Except that for onboarding we only create it after day 7 and for career mobility we create it at the same time as the career mobility issue.
Read here
A job is scheduled to run once per day to look for career mobility issues that have been opened for 5 days. If the team member for whom a career mobility issue was opened has not been mentioned in any access requests since their career mobility issue was opened, an note is created on the career mobility issue to remind the participants to create the necessary access requests.
