Skip to content

Move Contributor Success Job Family to Marketing

Nick Veenhof requested to merge move-cs-job-family into master

Why is this change being made?

Due to recent restructuring, the Contributor Success team is now reporting into Community Relations, Marketing. This is a subset of the change that was started in !119677 (closed)

This change only contains a move of Job Families. No content changes were made.

See Move Contributor Success Performance Indicators... (!120120 - merged) & Move Contributor Success handbook into Communit... (!120124 - merged) for related MRs

the merge request must follow this approval flow:

  • Your manager: Your direct manager is responsible for clarifying the scope of responsibilities and level of roles, checking responsibilities and requirements and ensuring the job family follows the template logic and has all of the required areas. Any review after this should be quick so the manager is the gatekeeper.
  • Your executive leader: Your executive leader is responsible for confirming the role is in plan and review of department/division structure and levels.
  • Your People Business Partner Who will review and typically notify Total Rewards
  • Total Rewards: The Total Rewards Team, @gl-total-rewards, is the final approver for job families on the merge request ensuring.:
    • There is a business need for the level within the job family.
    • The level is common in the market based on survey data.
    • All components of the job family are populated.
    • A benchmark is set to add to the Compensation Calculator.
    • A Job Title is created within Workday.
  • To create more visibility for the Merge Request, send a note to the #job-family slack channel

Author Checklist

  • Provided a concise title for this Merge Request (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, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • 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 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
    • The when to get approval handbook section explains the workflow in more detail
  • 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.

Edited by Sandra Choi

Merge request reports