Update steps in preparing offer justification to ensure detailed reasoning for past rejection is included
Why is this change being made?
While preparing an offer justification for a candidate, it is important to reach out to any interviewers (if they're still at GitLab), who had given a No
to the candidate, to gather more feedback and if possible, have the justification verified, eg; the candidate applied for a different role originally where they got rejected but their profile has now moved to a different position where they got positive feedback. The justification should be moved ahead for approval only after this step is covered by hiring manager for the role.
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.
-
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 Kushal Pandya