@@ -41,13 +41,12 @@ While maturing a decision or assessing options, the below steps can help you thr
The Solutions Architecture promotion process augments the [People Group Promotion Process](/handbook/people-group/promotions-transfers/) with the following:
1. The Planning stage of the calibration process [here](/handbook/people-group/promotions-transfers/#twice-per-year-promotion-calibration-process--timeline) typically means the SA leaders have completed all the required set of approvals including the VP of Customer Success.
1. Before the SA Manager starts the [Promotion Approval Process](/handbook/people-group/promotions-transfers/#processing-a-promotion), the manager will inform the Director/VP of Solutions Architecture that the justification document is ready for review, typically during a 1 on 1 weekly meeting.
- For Staff and Principal level promotions, the promotion justification document must be completed 2 quarters prior to promotion date and submitted to the Sr Director of SA for review. The Sr Director of SA will in turn review the justification with the VP of Customer Success.
- For Staff and Principal level promotions, the promotion candidate's manager will consult with the SA leadership team, typically during a weekly team meeting. This is to ensure continuous calibration for Staff and above-level roles that have lower representation amongst the SA organization. This must occur 2 quarters before the expected promotion quarter. For example, for a Q1 promotion, the calibration should occur in Q3 of the prior FY.
- For Staff level promotions, the promotion candidate's manager will consult with existing Staff and Principal level SAs for peer-level review and feedback while taking detailed notes.
- For Principal level promotions, the Principal candidates will prepare and present their accomplishments and their vision for improving GitLab and the SA organization to a panel of SA leaders and Principal level SAs after calibration has occurred.
- The Principal promotion panel will then meet to discuss the candidate's suitability for the Principal SA role.
1. The Planning stage of the calibration process [here](/handbook/people-group/promotions-transfers/#twice-per-year-promotion-calibration-process--timeline) typically means the SA leaders have forecasted the promotion candidates at least 2 quarters ahead of the promotion cycle.
1. For Staff and Principal level promotions, the promotion justification document must be completed 2 quarters prior to promotion date and submitted to the VP of SA for review.
1. For Staff and Principal level promotions, the promotion candidate's manager will consult with the SA leadership team, typically during a weekly team meeting. This is to ensure continuous calibration for Staff and above-level roles that have lower representation amongst the SA organization. This must occur 2 quarters before the expected promotion quarter. For example, for a Q1 promotion, the calibration should occur in Q3 of the prior FY.
1. For Staff level promotions, the promotion candidate's manager will consult with existing Staff and Principal level SAs for peer-level review and feedback while taking detailed notes to be reviewed with SA leadership.
1. For Principal level promotions, the Principal candidates will prepare and present their accomplishments and their vision for improving GitLab and the SA organization to a panel of SA leaders and Principal level SAs after the review with SA leadership (2 quarters prior to the promotion cycle). This happens before the standard promotion cycle calibrations.
1. The Principal promotion panel will then meet to discuss the candidate's suitability for the Principal SA role.
1. After reviewing and providing feedback, the VP of Solutions Architecture will inform the Manager or Director of his/her approval.
1. At this point, the standard quarterly promotion process is followed