# The higher level job-families directory needs to be outside of a section and near the top of this CODEOWNERS file as job-families require additional approvals beyond what's listed in other sections below
# The higher level job-description-library directory needs to be outside of a section and near the top of this CODEOWNERS file as job-description-library require additional approvals beyond what's listed in other sections below
* The Principal Engineer role acts as the individual equivalent of a Senior Engineering Manager, Development.
* Extends that of the [Staff Frontend Engineer](/job-families/engineering/development/frontend#staff-frontend-engineer) or the [Staff Backend Engineer](/job-families/engineering/development/backend/#staff-backend-engineer) responsibilities
* Extends that of the [Staff Frontend Engineer](/job-description-library/engineering/development/frontend#staff-frontend-engineer) or the [Staff Backend Engineer](/job-description-library/engineering/development/backend/#staff-backend-engineer) responsibilities
* Collaborates and makes proposals across several teams on their engineering work, and helps their team members make informed decisions in alignment with the sub-department strategic plans.
* Exposes technology and organizational needs across their sub-department.
* Teach, mentor, grow, and provide advice to other domain experts, individual contributors, across several teams in their sub-department.
@@ -34,7 +34,7 @@ Choose the method below that feels most comfortable and have the following infor
> - Name file `yournameinlowercase` with the appropriate file extension.
- Story about your background and interests. (See other team member profiles for examples.)
- Add your personal LinkedIn / Twitter / GitLab handles. When adding these handles, make sure to only include your username without any links or `@` in front of them, such as `LinkedIn: username`. (Some incorrect examples are: `LinkedIn: linkedin.com/in/username`, `LinkedIn: @username`.)
- A relative link to your role. If your link is `https://handbook.gitlab.com/job-families/engineering/support-engineer/` use `/job-families/engineering/support-engineer/`. Refer to other entries for reference.
- A relative link to your role. If your link is `https://handbook.gitlab.com/job-description-library/engineering/support-engineer/` use `/job-description-library/engineering/support-engineer/`. Refer to other entries for reference.
{{% alert title="Note" color="primary" %}}
For more information on setting the `Export Name/Location to Team Page?` opt-in mentioned below, search for the ["How to: Set Team Page Export Preferences" Google doc](https://drive.google.com/drive/search?q=how+to+Set+Team+Page+Export+Preferences)(internal).
@@ -53,7 +53,7 @@ For more information on setting the `Export Name/Location to Team Page?` opt-in
-`country` should be set to `Remote`
- Verify your `role`
- If your position title is incorrect or not filled in, navigate to `job_families.yml` and use `command-F` (macOS) or `ctrl-F` (nix) to search for your job title. You can search for files in the Web IDE using `command-P` (macOS) or `ctrl-P` (nix).
- Check that your role has a link to your job description. If not, add a link. For example, change `<a href="">Solutions Architect</a>` to `<a href="/job-families/sales/solutions-architect/">Solutions Architect</a>`.
- Check that your role has a link to your job description. If not, add a link. For example, change `<a href="">Solutions Architect</a>` to `<a href="/job-description-library/sales/solutions-architect/">Solutions Architect</a>`.
- Verify `reports_to` lists your manager using the `slug` value from their team page entry. The filename (without the extension) is also the slug, meaning `aname.yml` has a slug of `aname`.
- If you are a manager, verify the `reports_to` of your direct reports are referring to your `slug`.
- If you're currently on a borrow request, add `borrow` and set the `to` and `end_date` keys, such as:
@@ -28,7 +28,7 @@ Note: Both volunteer groups have owner role to the `content-sites` group in orde
## What are the content websites?
1. The public [`handbook.gitlab.com`](/) website:
1. While often referred to as "the handbook", this website also serves a wide variety of other content including the [job families](/job-families), and the [TeamOps](/teamops) pages.
1. While often referred to as "the handbook", this website also serves a wide variety of other content including the [job description library](/job-description-library/), and the [TeamOps](/teamops) pages.
1.`handbook.gitlab.com` is primarily backed by the [`gitlab-com/content-sites/handbook`](https://gitlab.com/gitlab-com/content-sites/handbook/) project and repo.
1. Data (YML) files currently resides in the [`gitlab-com/www-gitlab-com`](https://gitlab.com/gitlab-com/www-gitlab-com) repository.
1. The ["Internal Handbook" at `internal.gitlab.com`](https://internal.gitlab.com/):
