Working on a promotion
Overview
This page supplements the Promotions and Transfers handbook page and documents promotions-related workflows and processes specific to the Customer Support department.
Process
The general process for promotions is:
- Support team member completes promotion document in collaboration with their
manager.
- Collaboration with direct peers can also be a great resource in moving a promotion document forward. A lot of team members find recognizing and praising their co-workers easier than doing so for themselves.
- The manager circulates the promotion document for review and feedback amongst the manager’s peers.
- Support Directs review and calibrate all proposed promotions once a quarter.
- Approved promotions proceed through the rest of the process.
Promotion Document
The promotion document template can be found in the Pillars section of the Promotions and Transfers handbook page.
Business Results and Business Justifications section should closely align with the expected competencies for the role as laid out in:
In-Progress Promotion Documents
Collaboration on promotion documents encourages transparency in the promotion process. It can motivate and inspire others to build and strengthen their promotion documents. Internally public promotion documents are part of GitLab’s Promotion Philosophy. GitLab Support team members can link their internally public promotion documents in this section. Having a public in-progress promotion document is optional. If you are open to share your in-progress promotion document with the Support team you can use the Slack channel: #support_team-chat.
If you want to list your document here, decide what level of publicity you are comfortable with. Set the appropriate access for the GitLab group in the document’s Share settings: You can keep it read-only (Viewer
), allow others to comment and suggest edits (Commenter
) – or fully open it to collaboration (Editor
).
Promotion to Senior Support Engineer
Promotion to Staff Support Engineer
7877c2be
)