Add "Strategy and Operations (Handbook)" specialty role
Why is this change being made?
Fixes Product#3417 (closed). This role was originally planned to live under PeopleOps, but we have decided to take it on under the Chief of Staff team instead for the time being.
Here is the original doc: https://docs.google.com/document/d/131fveFnU3TwyvisoI0evTQKMIskv16rSUYGUZJK9vTA/edit#
Current plan is that I will act as interim DRI for the content sites and the team member(s) in this role will report to me. Initially plan to hire just one engineer in this new role, but we expect the Content Sites team to eventually expand to two engineers.
Note that despite being listed under the Strategy and Operations job family, the role is defined as a Fullstack Engineer. The main differentiator is that we expect this team member to be a bit more cross-functional within the organization along the lines of other Strategy and Operations specialist.
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
-
Assign reviewers for this change to the correct DRI(s) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR. - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.