Skip to content

Clarify that hiring nice-to-haves are role-specific

Dan Jensen requested to merge djensen-clarify-hiring-justification-nice-to-haves into master

Why is this change being made?

New hires are required to satisfy 5 of 9 "nice to have" requirements. However, there could be confusion about what those requirements are, because the list that appears in Greenhouse scorecards is not the same as the role-specific lists that appear in the Job Families documentation. This modifies the hiring documentation to clarify that we should use the role-specific lists (and adds a link to them).

Greenhouse scorecard list (generic)

This is the generic list of questions that currently appears in Greenhouse scorecards:

  1. ASKING GREAT QUESTIONS
  2. STARTUP EXPERIENCE
  3. USER OF GITLAB
  4. PRODUCT COMPANY EXPERIENCE
  5. MASSIVE SCALE
  6. DEVELOPER TOOL/PLATFORM INDUSTRY EXPERIENCE
  7. GLOBAL EXPERIENCE
  8. PERSEVERANCE
  9. OPEN SOURCE

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.
Edited by Dan Jensen

Merge request reports