Commit 302a7dc7 authored by Hanif Smith-Watson's avatar Hanif Smith-Watson
Browse files

Remove duplicate page content + redirects

parent ca523834
......@@ -3838,3 +3838,18 @@
- /handbook/marketing/growth-marketing/brand-and-digital-design/brand-guidelines/
target: /handbook/marketing/inbound-marketing/digital-experience/brand-guidelines/
comp_op: '='
- sources:
- /job-families/engineering/site-reliability-engineer
- /job-families/engineering/site-reliability-engineer/
target: /job-families/engineering/infrastructure/site-reliability-engineer/
comp_op: '='
- sources:
- /job-families/engineering/engineering-management-infrastructure
- /job-families/engineering/engineering-management-infrastructure/
target: /job-families/engineering/infrastructure/engineering-management/
comp_op: '='
- sources:
- /job-families/engineering/database-reliability-engineer
- /job-families/engineering/database-reliability-engineer/
target: /job-families/engineering/infrastructure/database-reliability-engineer/
comp_op: '='
......@@ -22,7 +22,7 @@ Please refer to the [development documentation for database guidelines](https://
We have two primary job roles that are focused on the database aspect:
 
1. [Backend Engineer, Database](/job-families/engineering/backend-engineer/) - in Development
2. [Database Reliability Engineer](/job-families/engineering/database-reliability-engineer/) - in Infrastructure
2. [Database Reliability Engineer](/job-families/engineering/infrastructure/database-reliability-engineer/) - in Infrastructure
 
The Backend Engineer, Database role is a software engineering role concentrated on application-side improvements and foundational database work in the GitLab codebase.
 
......@@ -36,7 +36,7 @@ The Database Maintainer role:
 
* Is an additional role, typically for Backend Engineers.
* Follows the same definition as any other [GitLab maintainer](/handbook/engineering/workflow/code-review/#maintainer).
* It does not come with operational responsibility for GitLab.com and its database infrastructure. This responsibility belongs to the [Database Reliability Engineer](https://about.gitlab.com/job-families/engineering/database-reliability-engineer/).
* It does not come with operational responsibility for GitLab.com and its database infrastructure. This responsibility belongs to the [Database Reliability Engineer](https://about.gitlab.com/job-families/engineering/infrastructure/database-reliability-engineer/).
* It is not expected to participate in incident management issues.
* Adheres to the [review turnaround time](https://docs.gitlab.com/ee/development/code_review.html#review-turnaround-time) of 2 working days.
* At the moment there's a low ratio of engineers per Database Maintainers, causing the Dabatabase Maintainer reviews to take more time. We're actively trying to [increase the number of Database Maintainers](https://gitlab.com/gitlab-org/gitlab-ce/issues/63790).
......
......@@ -212,7 +212,7 @@ In this program, engineers are expected to devote 1 entire week to shadow SREs.
 
Team members interested in the program should notify their respective managers. We are currently limited to 2 max shadows per release so that we do not overload the SRE team. If you are shadowing during the same release as another engineer, coordinate to create a combined access request for the duration of the release.
 
The participant's manager and the [Engineering Manager, Reliability Engineering](/job-families/engineering/engineering-management-infrastructure/) should collaborate with you to define a schedule in the Slack channel `#monitor-sre-shadow`. You can either check [PagerDuty schedules](https://gitlab.pagerduty.com/schedules#P05EL5A) or coordinate with the SRE manager to figure out who you'll be shadowing. Your schedule should include the week and working hours of your on-call shift, along with which SRE team member(s) will be on-call at the same time.
The participant's manager and the [Engineering Manager, Reliability Engineering](/job-families/engineering/infrastructure/engineering-management/) should collaborate with you to define a schedule in the Slack channel `#monitor-sre-shadow`. You can either check [PagerDuty schedules](https://gitlab.pagerduty.com/schedules#P05EL5A) or coordinate with the SRE manager to figure out who you'll be shadowing. Your schedule should include the week and working hours of your on-call shift, along with which SRE team member(s) will be on-call at the same time.
 
The participant should create an access request for PagerDuty and assign the access request to the SRE manager (this is a departure from [established processes](/handbook/business-ops/employee-enablement/it-ops-team/access-requests/#bulk-access-request)). PagerDuty licenses are limited so previous participants in the program may have to relinquish their licenses to you. Once PagerDuty access is set up, and you have been assigned to SRE engineer, you should override [shadow PagerDuty schedule](https://gitlab.pagerduty.com/schedules#PZEBYO0) and assign yourself to corresponding shift, you can add contact details like a mobile number so PagerDuty can send alerts to you.
 
......
......@@ -14,8 +14,8 @@ title: "Career Development in the Infrastructure Department"
There are a number of tools we use to plot and manage career development:
 
* Role descriptions, which outline role responsibilities, requirements and nice-tohaves for each level in the role.
* [DBRE](/job-families/engineering/database-reliability-engineer/)
* [SRE](/job-families/engineering/site-reliability-engineer/)
* [DBRE](/job-families/engineering/infrastructure/database-reliability-engineer/)
* [SRE](/job-families/engineering/infrastructure/site-reliability-engineer/)
* [Backend Developer, Delivery](/job-families/engineering/backend-engineer/)
* [Backend Developer, Infrastructure](/job-families/engineering/backend-engineer/)
* [Compa Ratios](/handbook/total-rewards/compensation/compensation-calculator/#compa-ratio), which reflects demonstrated ability to drive projects and deliverables from the position description in a quantifiable manner.
......@@ -56,7 +56,7 @@ Cross reference for [Internship for Learning](/handbook/people-group/promotions-
 
There is a reasonable amount of interest to intern with Infrastructure so we wanted to put a brief landing section in the handbook. If you are interested in interning with Infrastructure, we would ask that you talk to your current manager and create an issue per the mentioned process. This can help us track who is helping on what and what they would like to learn. Mention the Reliability Engineering team members and managers to help us know you are interested. One note, in some cases, you may need to submit access-requests to get access to certain systems to help with work.
 
Don't know what to learn? Talk with us! We have a broad set of technical skills listed in the [job description for SRE](/job-families/engineering/site-reliability-engineer/) if you are looking for ideas on what to learn. Set up a coffee chat with a team member or one of the managers.
Don't know what to learn? Talk with us! We have a broad set of technical skills listed in the [job description for SRE](/job-families/engineering/infrastructure/site-reliability-engineer/) if you are looking for ideas on what to learn. Set up a coffee chat with a team member or one of the managers.
If you're interested in learning more about SREs in general, you may wish to read Alice Goldfuss's blog post, "[How to Get Into SRE](https://blog.alicegoldfuss.com/how-to-get-into-sre/)." This blog post is an overview of all sorts of SRE related things, some of which may not be in use here at GitLab. However, it can be a valuable tool to learn more about SREs in general, and it links to many resources that you can use to learn more about a variety of SRE related topics.
 
Specific ways to work in the internship:
......
......@@ -25,7 +25,7 @@ We are entering our **fourth organizational iteration**: the department (and the
 
Infrastructure is now composed of five teams, and three individual contributors(ICs): three **Reliability** teams comprised of SREs and DBREs, the **Delivery** team, with continued focus on improving and dogfooding our CI/CD capabilities, and the **Scalability** team, which is hone in our scalability capabilities. Three IC's in the team are `Distinguished Engineer, Infrastructure`, `Engineering Fellow, Infrastructure`, and `Infrastructure Analyst`.
 
Infrastructure will continue to be comprised [DBRE](/job-families/engineering/database-reliability-engineer/)s, [SRE](/job-families/engineering/site-reliability-engineer/)s, backend (BE) and frontend (FE) engineers.
Infrastructure will continue to be comprised [DBRE](/job-families/engineering/infrastructure/database-reliability-engineer/)s, [SRE](/job-families/engineering/infrastructure/site-reliability-engineer/)s, backend (BE) and frontend (FE) engineers.
 
Note, Product Management support for the Infrastructure Department is provided by the [Enablement Stage](/handbook/product/product-categories/#enablement-stage) and is therefore not captured in this organization structure. To engage with the Infrastructure PM, see the [Infra PM page](/handbook/engineering/infrastructure/product-management/).
 
......
......@@ -2,10 +2,10 @@ The people of Core Infra are:
 
| Person | Role |
| ------ | ------ |
| [David Smith](/company/team/#dawsmith) | [Engineering Manager,Reliability](/job-families/engineering/engineering-management-infrastructure/#engineering-manager-reliability) |
| [Alex Hanselka](/company/team/#ahanselka) | [Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/) |
| [Devin Sylva](/company/team/#devin) | [Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/) |
| [Craig Barrett](/company/team/#craig) | [Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/) |
| [Cameron S McFarland](/company/team/#cmcfarland) | [Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/) |
| [Hendrik Meyer](/company/team/#T4cC0re) | [Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/) |
| [Graeme Gillies](/company/team/#ggillies) | [Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/) |
| [David Smith](/company/team/#dawsmith) | [Engineering Manager,Reliability](/job-families/engineering/infrastructure/engineering-management/#engineering-manager-reliability) |
| [Alex Hanselka](/company/team/#ahanselka) | [Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/) |
| [Devin Sylva](/company/team/#devin) | [Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/) |
| [Craig Barrett](/company/team/#craig) | [Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/) |
| [Cameron S McFarland](/company/team/#cmcfarland) | [Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/) |
| [Hendrik Meyer](/company/team/#T4cC0re) | [Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/) |
| [Graeme Gillies](/company/team/#ggillies) | [Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/) |
......@@ -35,13 +35,13 @@ Datastores is:
 
| Person | Role |
| ------ | ------ |
|[Alberto Ramos](/company/team/#albertoramos)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/engineering-management-infrastructure/#engineering-manager-reliability)|
|[Alejandro Rodríguez](/company/team/#eReGeBe)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Ahmad Sherif](/company/team/#ahmadsherif)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Henri Philipps](/company/team/#hphilipps)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Jose Cores Finotto](/company/team/#jose-finotto)|[Staff Database Reliability Engineer](/job-families/engineering/database-reliability-engineer/)|
|[Nels Nelson](/company/team/#nnelson)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|Open Position|[Database Reliability Engineer](/job-families/engineering/database-reliability-engineer/)|
|[Alberto Ramos](/company/team/#albertoramos)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/infrastructure/engineering-management/#engineering-manager-reliability)|
|[Alejandro Rodríguez](/company/team/#eReGeBe)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Ahmad Sherif](/company/team/#ahmadsherif)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Henri Philipps](/company/team/#hphilipps)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Jose Cores Finotto](/company/team/#jose-finotto)|[Staff Database Reliability Engineer](/job-families/engineering/infrastructure/database-reliability-engineer/)|
|[Nels Nelson](/company/team/#nnelson)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|Open Position|[Database Reliability Engineer](/job-families/engineering/infrastructure/database-reliability-engineer/)|
 
 
## Vision
......
......@@ -37,7 +37,7 @@ Reliability Engineering is responsible for all of GitLab's user-facing services,
 
## Team
 
The Reliability Engineering team is composed of [DBRE](/job-families/engineering/database-reliability-engineer/)s and [SRE](/job-families/engineering/site-reliability-engineer/)s. As the role titles indicate, they have different areas of specialty but shared ownership of GitLab.com's availability. The team is broken down into three sub-teams, each with their own area of ownership.
The Reliability Engineering team is composed of [DBRE](/job-families/engineering/infrastructure/database-reliability-engineer/)s and [SRE](/job-families/engineering/infrastructure/site-reliability-engineer/)s. As the role titles indicate, they have different areas of specialty but shared ownership of GitLab.com's availability. The team is broken down into three sub-teams, each with their own area of ownership.
 
#### Core Infra
 
......@@ -57,13 +57,13 @@ Datastores is:
 
| Person | Role |
| ------ | ------ |
|[Alberto Ramos](/company/team/#albertoramos)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/engineering-management-infrastructure/#engineering-manager-reliability)|
|[Alejandro Rodríguez](/company/team/#eReGeBe)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Ahmad Sherif](/company/team/#ahmadsherif)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Henri Philipps](/company/team/#hphilipps)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Jose Cores Finotto](/company/team/#jose-finotto)|[Staff Database Reliability Engineer](/job-families/engineering/database-reliability-engineer/)|
|[Nels Nelson](/company/team/#nnelson)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|Open Position|[Database Reliability Engineer](/job-families/engineering/database-reliability-engineer/)|
|[Alberto Ramos](/company/team/#albertoramos)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/infrastructure/engineering-management/#engineering-manager-reliability)|
|[Alejandro Rodríguez](/company/team/#eReGeBe)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Ahmad Sherif](/company/team/#ahmadsherif)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Henri Philipps](/company/team/#hphilipps)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Jose Cores Finotto](/company/team/#jose-finotto)|[Staff Database Reliability Engineer](/job-families/engineering/infrastructure/database-reliability-engineer/)|
|[Nels Nelson](/company/team/#nnelson)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|Open Position|[Database Reliability Engineer](/job-families/engineering/infrastructure/database-reliability-engineer/)|
 
 
#### Observability
......@@ -76,13 +76,13 @@ Observability is:
 
| Person | Role |
| ------ | ------ |
|[Anthony Sandoval](/company/team/#AnthonySandoval)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/engineering-management-infrastructure/#engineering-manager-reliability)|
|[Cindy Pallares](/company/team/#cindy)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Ben Kochie](/company/team/#bjk-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Igor Wiedler](/company/team/#igorwwwwwwwwwwwwwwwwwwww)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Michal Wasilewski](/company/team/#mwasilewski-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Matt Smiley](/company/team/#msmiley)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Craig Furman](/company/team/#craigf)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Anthony Sandoval](/company/team/#AnthonySandoval)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/infrastructure/engineering-management/#engineering-manager-reliability)|
|[Cindy Pallares](/company/team/#cindy)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Ben Kochie](/company/team/#bjk-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Igor Wiedler](/company/team/#igorwwwwwwwwwwwwwwwwwwww)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Michal Wasilewski](/company/team/#mwasilewski-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Matt Smiley](/company/team/#msmiley)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Craig Furman](/company/team/#craigf)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
 
 
## How We Work
......
......@@ -15,13 +15,13 @@ Observability is:
 
| Person | Role |
| ------ | ------ |
|[Anthony Sandoval](/company/team/#AnthonySandoval)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/engineering-management-infrastructure/#engineering-manager-reliability)|
|[Cindy Pallares](/company/team/#cindy)|[Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Ben Kochie](/company/team/#bjk-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Igor Wiedler](/company/team/#igorwwwwwwwwwwwwwwwwwwww)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Michal Wasilewski](/company/team/#mwasilewski-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Matt Smiley](/company/team/#msmiley)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Craig Furman](/company/team/#craigf)|[Senior Site Reliability Engineer](/job-families/engineering/site-reliability-engineer/)|
|[Anthony Sandoval](/company/team/#AnthonySandoval)|[Engineering Manager, Reliability](https://about.gitlab.com/job-families/engineering/infrastructure/engineering-management/#engineering-manager-reliability)|
|[Cindy Pallares](/company/team/#cindy)|[Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Ben Kochie](/company/team/#bjk-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Igor Wiedler](/company/team/#igorwwwwwwwwwwwwwwwwwwww)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Michal Wasilewski](/company/team/#mwasilewski-gitlab)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Matt Smiley](/company/team/#msmiley)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
|[Craig Furman](/company/team/#craigf)|[Senior Site Reliability Engineer](/job-families/engineering/infrastructure/site-reliability-engineer/)|
 
 
## Vision
......
......@@ -40,4 +40,4 @@ Non-public information relating to this security control as well as links to the
 
Examples of evidence an auditor might request to satisfy this control:
 
* Evidence that PostgreSQL database access above data reader is limited to [Database Reliability Engineers](/job-families/engineering/database-reliability-engineer/)
\ No newline at end of file
* Evidence that PostgreSQL database access above data reader is limited to [Database Reliability Engineers](/job-families/engineering/infrastructure/database-reliability-engineer/)
\ No newline at end of file
......@@ -576,8 +576,8 @@ Anthony Sandoval, Engineering Manager - Reliability Engineering, Secure and Prot
Jose Finotto, Engineering Manager - Reliability Engineering, Dev and Ops
**Useful links:**
[Infrastructure handbook](/handbook/engineering/infrastructure/team/)
[Site Reliability Engineer job family](/job-families/engineering/site-reliability-engineer/)
[Database Reliability Engineer job family](/job-families/engineering/database-reliability-engineer/)
[Site Reliability Engineer job family](/job-families/engineering/infrastructure/site-reliability-engineer/)
[Database Reliability Engineer job family](/job-families/engineering/infrastructure/database-reliability-engineer/)
[SRE stable counterparts and areas of ownership](/handbook/engineering/infrastructure/#sre-stable-counterparts-and-areas-of-ownership)
 
Team vision: We are a blend of operations gearheads and software crafters that apply sound engineering principles, operational discipline and mature automation to make GitLab.com ready for mission-critical customer workloads. We strive for excellence every day by living and breathing GitLab's values as our guiding operating principles in every decision we make and every action we take.
......
......@@ -200,7 +200,7 @@ When running in development or test mode, GitLab now detects n+1 situations and
 
At the start of May 2018, the Infrastructure team responsible for GitLab.com consisted of five engineers.
 
Since then, we've had a new director join the Infrastructure team, two new managers, a specialist [Postgres DBRE](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/13778), and four new [SREs](/job-families/engineering/site-reliability-engineer/). The database team has been reorganized to be an embedded part of infrastructure group. We've also brought in [Ongres](https://www.ongres.com/), a specialist Postgres consultancy, to work alongside the team.
Since then, we've had a new director join the Infrastructure team, two new managers, a specialist [Postgres DBRE](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/13778), and four new [SREs](/job-families/engineering/infrastructure/site-reliability-engineer/). The database team has been reorganized to be an embedded part of infrastructure group. We've also brought in [Ongres](https://www.ongres.com/), a specialist Postgres consultancy, to work alongside the team.
 
Having enough people in the team has allowed us to be able to split time between on-call, tactical improvements, and longer-term strategic work.
 
......
......@@ -35,7 +35,7 @@ who is responsible for keeping all user-facing services and other GitLab product
systems running smoothly.
 
_You can learn all about them in [our
handbook](/job-families/engineering/site-reliability-engineer/)._
handbook](/job-families/engineering/infrastructure/site-reliability-engineer/)._
 
**Here are some of my general takeaways from that week:**
 
......
Moved to the [infrastructure/ directory](../infrastructure/database-reliability-engineer/).
Moved to the [infrastructure/ directory](../infrastructure/engineering-management/).
......@@ -8,7 +8,7 @@ title: "Engineering Management - Infrastructure"
The Manager, Engineering (Delivery) personally manages the engineering team responsible for tasks relating to
release management of GitLab releases as well as continuous delivery/deployment on GitLab.com.
Team mandate is described in the [team handbook](/handbook/engineering/infrastructure/team/delivery/)
and it consists of [Site Reliability Engineers](/job-families/engineering/site-reliability-engineer/) and
and it consists of [Site Reliability Engineers](/job-families/engineering/infrastructure/site-reliability-engineer/) and
[Backend Engineers](/job-families/engineering/backend-engineer/).
The Engineering Manager's responsibility is primarily their team. They need to
be familiar with GitLab's underlying technologies and processes to be able to support their teams growth, as well as be the final conclusive vote in cases where the team is blocked on a path forward.
......@@ -60,8 +60,8 @@ Manager, Engineering (Delivery), have the following job-family performance indic
## Manager, Engineering Reliability
 
The Manager, Engineering (Reliability) personally manages the engineering team relentlessly focused on GitLab.com's
performant reliability, a team composed of [DBRE](/job-families/engineering/database-reliability-engineer/)s and
[SRE](/job-families/engineering/site-reliability-engineer/)s. They see the team as their product. They may work on
performant reliability, a team composed of [DBRE](/job-families/engineering/infrastructure/database-reliability-engineer/)s and
[SRE](/job-families/engineering/infrastructure/site-reliability-engineer/)s. They see the team as their product. They may work on
small features or bugs to keep their technical skills sharp and stay familiar with the code, but they emphasize
hiring a world-class team and putting them in the optimal position to succeed. They own the delivery of product
commitments and they are always looking to improve the productivity of their team. They must also coordinate
......@@ -112,7 +112,7 @@ Manager, Engineering (Infrastructure), have the following job-family performance
 
## Manager, Engineering (Scalability)
 
The Manager, Engineering (Scalability) personally manages the engineering team responsible for GitLab and GitLab.com at scale, working on the highest priority scalability items in the application in close coordination with **Reliability Engineering** teams and providing feedback to other Engineering teams so they can become better at scalability as well. Team mandate is described in the [team handbook](/handbook/engineering/infrastructure/team/scalability/) and it consists of [Backend Engineers](/job-families/engineering/backend-engineer/) and [Site Reliability Engineers](/job-families/engineering/site-reliability-engineer/).
The Manager, Engineering (Scalability) personally manages the engineering team responsible for GitLab and GitLab.com at scale, working on the highest priority scalability items in the application in close coordination with **Reliability Engineering** teams and providing feedback to other Engineering teams so they can become better at scalability as well. Team mandate is described in the [team handbook](/handbook/engineering/infrastructure/team/scalability/) and it consists of [Backend Engineers](/job-families/engineering/backend-engineer/) and [Site Reliability Engineers](/job-families/engineering/infrastructure/site-reliability-engineer/).
 
The Engineering Manager's responsibility is primarily their team. They need to be familiar with GitLab's underlying technologies and processes to be able to support their team growth, as well as be the final conclusive vote in cases where the team is blocked on a path forward.
 
......
......@@ -197,7 +197,7 @@ continuously contribute to GitLab codebases), and have a good grasp on observabi
 
## Career Ladder
 
The next step for both individual contributors and managers of people is to move to the [Engineering Management - Infrastructure](/job-families/engineering/engineering-management-infrastructure) job family.
The next step for both individual contributors and managers of people is to move to the [Engineering Management - Infrastructure](/job-families/engineering/infrastructure/engineering-management/) job family.
 
## Performance Indicators
 
......
Moved to the [infrastructure/ directory](../infrastructure/site-reliability-engineer/).
......@@ -75,7 +75,7 @@ extra_css:
| Engineering | Backend Engineer, Enablement: Distribution | [What we're looking for](https://about.gitlab.com/job-families/engineering/backend-engineer/#distribution) |
| Engineering | Backend Engineer, Scalability | [What we're looking for](https://about.gitlab.com/job-families/engineering/backend-engineer/#scalability) |
| Engineering | Backend Engineer, Verify | [What we're looking for](https://about.gitlab.com/job-families/engineering/backend-engineer/) |
| Engineering | Database Reliability Engineer | [What we're looking for](https://about.gitlab.com/job-families/engineering/database-reliability-engineer/) |
| Engineering | Database Reliability Engineer | [What we're looking for](https://about.gitlab.com/job-families/engineering/infrastructure/database-reliability-engineer/) |
| Engineering | Product Designer, Release: Progressive Delivery | [What we're looking for](https://about.gitlab.com/job-families/engineering/product-designer/) |
| Engineering | Product Design Manager, Manage/Plan | [What we're looking for](https://about.gitlab.com/job-families/engineering/ux-management/) |
| Engineering | Senior Product Designer, Verify: Runner & Testing | [What we're looking for](https://about.gitlab.com/job-families/engineering/product-designer/ ) |
......
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