The responsibilities of this stage are described by the Manage product category. Manage is made up of multiple groups, each with their own categories and areas of responsibility.
We use an issue board to track open Development positions within the Manage stage.
~"HM::Needs Greenhouse ID"label. If you already have the GHID for your position, add it to the issue description.
~"HM::Completed Kickoff Issue"label to signify that the position is ready to go live in Greenhouse, and reassign it to the recruiter DRI.
~"HM::Interviewing". More granular information, such as the number of screening calls or technical/behavioral interviews scheduled, can be reported weekly in 1-1's or using the issue. While many people are involved in this process, hiring managers are still the DRI for a successful hire.
~"HM::Pending Offer"label to indicate the Justification and Offer process has been started.
Note: SLO's are based on business hours
|Create kickoff issue||Hiring Manager|
|Create requisition in Greenhouse||Recruiter||48 hours||See preparations|
|Review applications for qualified -> screening||Hiring manager||36 hours||Hiring managers should determine new applications are qualified/rejected within 36 hours of submission|
|Screen candidates||Hiring manager||1 week||Screening calls should be scheduled within 1 week of moving a candidate to this stage|
|Technical interviews||Hiring manager||1 week||Technical interviews should be requested for scheduling within 1 week of moving a candidate to this stage. Process defined here|
|Final round interviews||Recruiter|
|Reference checks||Hiring manager|
|Extend an offer||Recruiter|
Hiring managers should be checking the progress of their positions on a daily basis in order to understand when an escalation may be needed. To escalate a problem or candidate:
@leifFrom here, we can pull in additional help to resolve the escalation and archive the channel.
Reminder: Please do not use a candidate's full name in a public Slack channel.
The direction and strategy for Manage is documented on https://about.gitlab.com/direction/manage/. This page (and the category direction pages under the "Categories" header) is the single source of truth on where we're going and why.
It can be hard to understand how you're doing in your role, because feedback can come off as formal (annual reviews, 360 surveys, career development conversations, goal check-ins) or casual (in Slack channels, 1-1's, MR reviews, team meetings.) We receive various kinds of feedback regularly and through different formats, so the type of feedback you're receiving is not always clear. In order to be more intentional about the types of feedback given, here is a classification chart based on three types of feedback:
|(appreciation)||I want to thank you for doing this, and please do more of it in the future||"I did not expect that you would have created a working group, because you've done so, our whole team will benefit from the results."|
|(coaching)||I'm trying to help you improve a behavior you are already exhibiting or change a behavior that you currently have||"The reports that you give me are very helpful, and in the future we can schedule them for the first of the month to be more consistent."|
|(evaluation)||Tells you where you stand according to existing standards or expectations||"My expectation was that our decision would be transparent. Since it was not, our team has forgotten the decision, so we must be sure and meet that expectation next time."|
This section lists relevant experience areas for individual contributors interested in the management track, new engineering managers, or existing engineering managers who may be lacking opportunities. This list can be used to identify opportunities in these areas.
Expert hiring manager
Communicating company decisions
For an explanation on what to expect as a Staff engineer and a list of ideas for tactical initaitives, visit this page.
Although we have a bias for asynchronous communication, synchronous meetings are necessary and should adhere to our communication guidelines. Some regular meetings that take place in Manage are:
|Monthly||Stage-level social call||@dennis||Getting to know each other|
For one-off, topic specific meetings, please always consider recording these calls and sharing them (or taking notes in a publicly available document).
Agenda documents and recordings can be placed in the shared Google drive (internal only) as a single source of truth.
All meetings should have an agenda prepared at least 12 hours in advance. If this is not the case, you are not obligated to attend the meeting. Consider meetings canceled if they do not have an agenda by the start time of the meeting.