Skip to content

Updating "Top 10 reasons to work for GitLab" on GitLab Culture

Sarah Bailey requested to merge sbailey1-master-patch-90525 into master

Why is this change being made?

This MR updates "Top 10 reasons to work for GitLab" section of the GitLab Culture handbook under Advantages. This updated list was provided by Sid.

Sid requested we update old 10 reasons to new version:

  • Update version - Details below
  • Check Grammarly for issues.
  • Investigate YouTube Boat video. Does it need to private/available on site? Current link -> https://youtu.be/4TnKmrpiSgQ

Details:

LINK: Old list of 10 reasons

Suggested List from the meeting with Sid:

  • Mission: Everyone can contribute

  • Results: Fast growth, product (great net retention), ambitious vision

  • Transparency: 2000 page handbook, GitLab Unfiltered

  • Iteration: empower people to be effective, MR rate, everyone using the product, DRI, have an impact

  • Efficient: meetings start and end on time, no presenting in meetings, speedy meetings, clear proposals, async when possible

  • DIB: high percentage of women, TMRGs, other initiatives

  • Collaboration: saying thanks stats, intentionally organize informal communication, no ego

  • Compensation: pay at x percentile, stock options, equipment, office if you want it, else

  • Live work harmony:  don't compete on hours worked, flexible workday, F&F days

  • Remote done right: all remote, largest before pandemic, most prolific inventor of best practices

Author Checklist

https://gitlab.com/gitlab-com/ceo-shadow/tasks/-/issues/214

  • 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.
Edited by Sarah Bailey

Merge request reports