Commit fc66ab45 authored by Ashton Herrmann's avatar Ashton Herrmann

Merge branch 'hiring-definitions-update' into 'master'

Update hiring definitions and other references to job families

See merge request !12386
parents f5104888 a5962aff
Pipeline #23747670 passed with stages
in 14 minutes and 21 seconds
......@@ -7,7 +7,7 @@ title: "Hiring"
- [Interviewing](/handbook/hiring/interviewing/)
- [Vacancies](/handbook/hiring/vacancies/)
- [Roles](/handbook/hiring/roles)
- [Job families](/handbook/hiring/roles)
- [Lever](/handbook/hiring/lever/)
- [Sourcing](/handbook/hiring/sourcing/)
- [Principles](/handbook/hiring/principles/)
......@@ -27,35 +27,35 @@ title: "Hiring"
## Definitions
Roles and vacancies are different things and can't be used interchangeably.
Job families and vacancies are different things and can't be used interchangeably.
- A **role** is a permanent item, it is maintained under /roles, its contents is a superset of all vacancies for that role, and it is created with a merge request.
- A [vacancy](/handbook/hiring/vacancies/) is temporary item, posted on Lever, its contents subset of the role, and it is created by copying parts of a role based on an issue.
- A [job family](/job-families) is a permanent item; its content is a superset of all vacancies for the job family, and it is created with a merge request.
- A [vacancy](/handbook/hiring/vacancies/) is temporary item posted on Lever; its content is a subset of the job family, and it is created by copying parts of a job family based on an issue.
We don't use the word job to refer to role or vacancy because it is ambiguous.
We don't use the word "job" to refer to a job family or vacancy because it is ambiguous.
People at GitLab can be a specialist on one thing and expert in many:
- A [specialization](/team/structure/#specialist) is specific to a role, each team member can have only one, it defined on the relevant role page. A specialist uses the compensation benchmark of the role.
- An [expertise](/team/structure/#expert) is not specific to a a role, each team member can have multiple ones, the expertises a team member has are listed on our team page.
- A [specialization](/team/structure/#specialist) is specific to a job family, each team member can have only one, it defined on the relevant job family page. A specialist uses the compensation benchmark of the job family.
- An [expertise](/team/structure/#expert) is not specific to a a job family, each team member can have multiple ones, the expertises a team member has are listed on our team page.
The following parts describe what someone does at GitLab:
1. Level: Senior
1. Role: Developer
1. job family: Developer
1. Specialist: Gitaly specialist
1. Location: EMEA
1. Expert: Reliability, Durability
We use the following terms to refer to a combination of the above:
- Title (level and role, listed on the contract): Senior Developer
- Title (level and job family, listed on the contract): Senior Developer
- Headline (all parts except expertise, listed on vacancies): Senior Developer, Gitaly specialist, EMEA
Please use the same order as in the examples above, a few notes:
- Level comes before role.
- Specialist comes after role and always includes 'specialist'.
- Level comes before job family.
- Specialist comes after job family and always includes 'specialist'.
- Location comes after specialization.
We preface a title with interim when we're hiring for the position.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment