| KPI | Health | Status |
|---|---|---|
| Candidates Sourced by Recruiting Department vs. Candidates Hired | Unknown |
|
| Top of Funnel Diversity | Unknown |
|
| Outbound Candidates versus Candidates Hired | Unknown |
|
| Hires vs. Plan | Unknown |
|
| Time to Offer Accept (Days) | Unknown |
|
| Interviewee Satisfaction (ISAT) | Unknown |
|
| Cost Per Hire | Unknown |
|
How many candidates were sourced by the Recruiting Department out of those who we hired in a given month.
Target: The candidates sourced versus candidates hired target is greater than 0.50
Chart (Sisense↗)
Status: Unknown
Candidates at the top of funnel contribute to the diversity of the company
Target: Outreach to diverse candidates meets or exceeds 90%
Status: Unknown
Outbound candidates are candidates sourced from GitLab Talent Community, along with Referrals, Social Referrals, and Candidates Sourced by Recruiting Department.
Target: The goal is that outbound candidates are greater than 80 percent of all hired candidates.
Chart (Sisense↗)
Status: Unknown
The number of hires based on start date divided by the number of planned hires in a given month. Hires comes from BambooHR. This KPI is tracked and reported on a monthly basis but year to date (headcount v plan) is also measured.
Target: greater than 0.9
Chart (Sisense↗)
Status: Unknown
The median number of days from when a candidate is active in Greenhouse (applied, referred, or sourced) to accepting an offer in a given month.
Target: The Time to Offer Accept (Days) target is < 45.
Chart (Sisense↗)
Status: Unknown
The answer to the ‘Interviewee Satisfaction (ISAT) Score’ question, “Overall, my interviewing experience was a positive one,” is greater than 4.1 across all departments in a given month (1 - 5 response scale).
Target: Greater than 4.1
Chart (Sisense↗)
Status: Unknown
Cost per hire is calculated by taking the total monthly expenses incurred in the Recruiting department and other monthly expenses related to the hiring process and dividing by the total number of hires in that month. Besides the expenses incurred in the Recruiting department (i.e. salaries, travel expenses, recruiting software etc.) other expenses related to recruiting are agency fees and referral bonuses. These expenses are incurred in departments outside of Recruiting but hit their own GL accounts. These GL accounts will be what is included in Cost Per Hire, along with the total Recruiting Department expenses. This is calculated on a rolling three month average.
Target: The cap is less than $6,500.
This KPI cannot be public.
URL(s)
Status: Unknown
The percentage of Offer Accepts whose source was “Referral” in a given calendar month. This is calculated by taking the number of “Referral” Offer Accepts and dividing that by the total number of Offer Accepts for a given calendar month. “Referrals” are tracked in Greenhouse.
Status: Unknown
On average, the time it takes to complete one Recruiting Team project.
Status: Unknown
How many Recruiting Team projects have been completed versus projects that are currently open in a given period of time (e.g. per quarter)
Chart (Sisense↗)
Status: Unknown
Analysis of the number of submitted internal support tickets, the number of resolved tickets, and the average time to resolution.
Status: Unknown
The number of Offers sourced by a Sourcer.
Status: Unknown
The number of sourced candidates moved to the Reference Check stage.
Status: Unknown
The number of candidates submitted by Sourcer that were Hired.
Status: Unknown
The number of candidates submitted by Sourcer that received an Offer.
Status: Unknown
The number of candidates submitted by Sourcer that successfully passed the screening call.
Status: Unknown
The number of candidates scheduled to speak with a Recruiter on a screening call.
Status: Unknown
The number of Prospects submitted to a Recruiter and/or a Hiring Manager by one Sourcer.
Status: Unknown
The percentage of Offer Accepts whose source was “SocialReferral” in a given calendar month. These candidates applied via links shared on social media sites (e.g. LinkedIn, Twitter, and the like). This is calculated by taking the number of “SocialReferral” Offer Accepts and dividing that by the total number of Offer Accepts for a given calendar month. “SocialReferrals” are tracked in Greenhouse.
Status: Unknown
The percentage of the company that has a recruiting or hiring manager seat on LinkedIn. This is calculated by taking the total number of recruiting and hiring manager seats divided by total employees on a calendar month basis.
Status: Unknown
Average number of days a Candidate spends per stages in the [interview plan](/handbook/hiring/recruiting-framework/coordinator/#step-14c-schedule-team-interviews).
Status: Unknown
The percentage of team members that have a *Recruiter* or *Hiring Manager* seat and at least 1 active day of use per month. This is calculated by taking the total number of team members with at least 1 active day of use and dividing it by the total number of team members that have a seat.
Status: Unknown
| Value | Level | Meaning |
|---|---|---|
| 3 | Okay | The KPI is at an acceptable level compared to the threshold |
| 2 | Attention | This is a blip, or we’re going to watch it, or we just need to enact a proven intervention |
| 1 | Problem | We'll prioritize our efforts here |
| 0 | Unknown | Unknown |
| Value | Level | Meaning |
|---|---|---|
| 3 | Okay | We are correctly capturing and measuring data for GitLab.com and self-managed instances. |
| 2 | Attention | Missing one of: GitLab.com or self-managed data. |
| 1 | Problem | Missing both: GitLab.com and self-managed data. |
| 0 | Unknown | Unknown |
Pages, such as the Engineering Function Performance Indicators page are rendered by an ERB template that contains HTML code.
Other PI Pages sectionmaturity table, make changes to the Performance Indicators Maturities ERB fileThese ERB templates calls custom helper functions that extract and transform data from the Performance Indicators data file.
kpi_list_by_org(org) helper function takes a required string argument named org (deparment or division level) that returns all the KPIs (pi.is_key == true) for a specific organization grouping (pi.org == org) from the Performance Indicators data file.pi_maturity_level(performance_indicator) helper function automatically assigns a maturity level based on the availability of certain data properties for a particular PI.pi_maturity_reasons(performance_indicator) helper function returns a reason for a PI maturity based on other data properties.performance_indicator_target(name) helper function returns the target value from the target property for a specific PI from the Performance Indicators data file.performance_indicators(org) takes a required string argument named org (deparment or division level) that returns two lists - a list of all KPIs and a list of all PIs for a specific organization grouping (department/division).signed_periscope_url(data) takes in the sisense_data property information from the Performance Indicators data file and returns a signed chart URL for embedding a Sisense chart into the handbook.The heart of pages like this is the Performance Indicators data file which is in YAML file. Each - denotes a dictionary of values for a new (K)PI. The current elements (or data properties) are:
| Property | Type | Description |
|---|---|---|
name |
Required | String value of the name of the (K)PI |
base_path |
Required | Relative path to the performance indicator page that this (K)PI should live on |
definition |
Required | refer to Parts of a KPI |
parent |
Optional | should be used when a (K)PI is a subset of another PI. For example, we might care about Hiring vs Plan at the company level. The child would be the division and department levels, which would have the parent flag. |
target |
Required | The target or cap for the (K)PI. Please use Unknown until we reach maturity level 2 if this is not yet defined. |
org |
Required | the organizational grouping (Ex: Engineering Function or Development Department) |
is_key |
Required | boolean value (true/false) that indicates if it is a (key) performance indicator |
health |
Required | has two additional elements/property - level (inclusive value between 0-3) and reasons. This should be updated monthly before Key Meetings by the DRI. |
urls |
Optional | list of urls associated with the (K)PI |
sisense_data |
Optional | contains elements/properties related to Sisense, including chart (numeric Sisense widget ID), dashboard (numeric Sisense dashboard ID), shared_dashboard (Sisense shared dashboard ID), embed (v2) |
public |
Optional | boolean flag that can be set to false where a (K)PI does not meet the public guidelines. |
instrumentation |
Optional | has two additional elements/property - level (inclusive value between 0-3) and reasons. This should be updated monthly before Key Meetings by the DRI. |
shared_dashboard, chart , and the dashboard key-value pairs to the Performance Indicators data file under the sisense_data property: in strings as it's an important character in YAML and will confuse the data parsing process. Put the string in "quotes" if you really need to use a :urls: should be an array (indented lines starting with dashes) even if you only have one urlmaturity.level and health.level display a value between 0 and 3 (inclusive). The health value is a manual input while the maturity is an automated value based on other discrete (K)PI data properties.