Updated Talent Acquisition Landing Page.md

Jessica Dallmarrequested to merge
jdallmar-main-patch-3398 into main

This merge request reorganizes and simplifies GitLab's hiring handbook page. The main changes include:

Removed content:

  • The "Talent Acquisition Vision Statement" section was completely deleted
  • Detailed definitions for hiring terminology (Job, Opening, GHPiD) were removed
  • Extensive global hiring resources and country-specific PEO onboarding timelines were deleted
  • Various process links and detailed sections for different roles were streamlined

Reorganized content:

  • Restructured the page into clearer sections: "Recruiting Resources," "Candidate Resources," "Interviewer Resources," and "Hiring Manager Resources"
  • Updated the strategy document link to specify "FY26 Talent Acquisition Strategy"
  • Added a new "Talent Brand" section
  • Consolidated training and playbook links under role-specific headings

Text updates:

  • Changed references from "vision" to "mission" in the guiding principles section
  • Updated wording from "commitments and plans" to "objectives" in the predictability principle
  • Added "(Internal only)" labels to internal documents
  • Simplified the additional resources section by removing several links

Overall, this reorganization makes the handbook more focused and easier to navigate by removing detailed operational information and grouping resources by user type.

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

Removing outdated, incorrect information. Provided streamlined documentation. CHANGEME

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
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • 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
    • Division: If the update affects your division, share the MR in your division 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

Commits

  • Update file _index.md

Merge request reports