Merge branch 'add-time-to-hire' into 'master'

Adding Time-to-Hire Actuals

See merge request gitlab-com/www-gitlab-com!32209

source/handbook/hiring/interviewing/index.html.md

@@ -25,11 +25,30 @@ Please refer to the [country hiring guidelines](/jobs/faq/#country-hiring-guidel
 1. Once you have finished, click "Submit Application" at the bottom.
 1. Should you reach out to any GitLab team member on any social media platform, that you have not worked with previously or do not know, requesting to be referred, instead of or in addition to applying to our jobs page, you'll receive the following reply: "Thank you for your interest in GitLab. We would much rather prefer you apply for the position you have in mind directly via our [Jobs page](/jobs/). This will ensure the right GitLab team member reviews your profile and replies back to you! Unfortunately at this time, I can not refer you for the position as we have not had a chance to work together. To ensure we stay [inclusive](/handbook/values/#diversity--inclusion), I can also not influence your application".
 1. If at any point during the interview process, you send threatening emails, emails containing profanity, vulgar language, or [hurtful labels](/handbook/people-group/code-of-conduct/), we will close your application and inform you. We will also not respond any further to you. We aim to hire only people who align with our [values](/handbook/values/#credit).
-1. If your application is rejected because you are insufficiently qualified for the role, you are welcome to reapply to the same position once 6 months have passed. If you gain the skills, experience, or knowledge we outlined in our [feedback to you](/handbook/hiring/interviewing/#rejecting-candidates), you are welcome to reapply at any time. 
+1. If your application is rejected because you are insufficiently qualified for the role, you are welcome to reapply to the same position once 6 months have passed. If you gain the skills, experience, or knowledge we outlined in our [feedback to you](/handbook/hiring/interviewing/#rejecting-candidates), you are welcome to reapply at any time.
+
+#### Average Time-to-Hire
+
+We strive to be as expeditious as possible in our hiring process. However, the speed of the process can and does vary. The following is our average *time-to-hire* (i.e. Apply to Offer Accept). The *80th Percentile* has been included to account for outliers.
+
+- Overall: **53.06 days**
+
+    - Engineering: 60.17 days
+        - *80th Percentile: 51.17 days*
+    - G&A: 46.13 days
+        - *80th Percentile: 29.00 days*
+    - Marketing: 42.32 days
+        - *80th Percentile: 33.56 days*
+    - Product: 73.33 days
+        - *80th Percentile: 68.60 days*
+    - Sales: 51.63 days
+        - *80th Percentile: 37.79 days*
+
+Source: Greenhouse (ATS); September 2019         
 #### Reimbursement for Interviewing with GitLab
-If you are invited for an interview with GitLab and you need financial support for your interview, you may be reimbursed for the following: 
+If you are invited for an interview with GitLab and you need financial support for your interview, you may be reimbursed for the following:
    - Childcare or adultcare for dependents
    - Rental costs associated with laptop or computer if you don't own or have access to one
@@ -53,8 +72,8 @@ If you are a [current team member and are interested in applying](/handbook/peop
 ### Adjustments to our interview process
-We want our interview process to be accessible to everyone. You can inform us of any adjustments we can make to better accommodate your needs by writing in the text box labeled `Please let us know if there are any adjustments we can make to assist you during the hiring and interview process.` found in the application form. 
- 
+We want our interview process to be accessible to everyone. You can inform us of any adjustments we can make to better accommodate your needs by writing in the text box labeled `Please let us know if there are any adjustments we can make to assist you during the hiring and interview process.` found in the application form.
+
 If you’ve begun the process without sending in an application form, you can ask the Recruiter who’s supporting you through the process to make these adjustments, so we accommodate your needs.
 ## Typical Hiring Timeline
@@ -107,7 +126,7 @@ The GitLab team understands the importance of inclusive interviewing, and we str
      * Digital Marketing Programs
      * Field Marketing
      * Marketing Ops
-     * UX 
+     * UX
      * Quality
 ## Conducting a Screening Call
@@ -130,7 +149,7 @@ Example questions include:
 If a candidate is either sourced or referred, please note this in the `Public Notes` section of the scorecard.  This will give future interviewers more context for questions like "Why are you interested in GitLab".
-At the end of the screening call, you will tell the candidate what the next steps will be. You will also inform the candidate of the hiring timeline and the average number of days that it takes from application to acceptance for the role being discussed. 
+At the end of the screening call, you will tell the candidate what the next steps will be. You will also inform the candidate of the hiring timeline and the average number of days that it takes from application to acceptance for the role being discussed.
 ## Moving Candidates Through The Process
@@ -172,7 +191,7 @@ When discussing the interview process with candidates, it is encouraged to set t
 New internal interviewers will partake in [interviewing training](https://gitlab.com/gitlab-com/people-ops/Training/blob/master/.gitlab/issue_templates/interview_training.md), which will be assigned by the recruiting team. As part of the training, team members will shadow an interviewer and be shadowed by one in order to make sure all GitLab team-members are following our interviewing processes and creating an excellent candidate experience. The interviewer who will work with the team member should be aligned with either their timezone or the role they'll be helping interview for. Feel free to ping `@gl-hiring` in your training issue if you are not sure which interviewer to contact, or send a message in the `#recruiting` channel in Slack.
-Interviews should not be recorded. For interview training, we encourage our GitLab Hiring Managers to conduct mock interviews internally, or have no more than one GitLab team member at a time shadowing live interviews. 
+Interviews should not be recorded. For interview training, we encourage our GitLab Hiring Managers to conduct mock interviews internally, or have no more than one GitLab team member at a time shadowing live interviews.
 It is typically expected for new hires to focus on and complete their onboarding for at least two weeks before being part of an interview team for any vacancies. There may be extenuating circumstances where a team member needs to participate in interviewing sooner than this, but they should always complete the [interviewing training](https://gitlab.com/gitlab-com/people-ops/Training/blob/master/.gitlab/issue_templates/interview_training.md) and discuss the vacancy thoroughly with their manager and the recruiter prior to being on an interview team.