Skip to content

Explain yearly refresh policy for new hires

Jonas Larsen requested to merge j_lar/clarify-yearly-grant-refresh-policy into main

Why is this change being made?

With the previously wording, Team Members who started in FY23 could expect to have a $500 budget available for FY24.

Currently, a reader of the handbook would thing that New Hires are eligible for a refresh grant, as the handbook only has this description: image

As I have learned in private emails with the Expenses team, the policy is that Team Members hired in previous fiscal year will not receive a refresh grant until the start of their second full fiscal year.

Screenshot of explanation from the Expenses team image

For example, a Team Member who started May 10, 2023 will get their first refresh amount on February 1 2025 and not in 2024.

I hope that this change will prevent that New Hires are disappointed over that the policy is less generous as it sounds.

(Notice that this MR is a recreation of gitlab-com/www-gitlab-com!130739 (closed) that was created just before the expenses page was moved to this repository)

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • 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
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Merge request reports