Commit 2d5a7623 authored by Michelle Gill's avatar Michelle Gill
Browse files

docs: consolidate engineering careers sections

parent b7a78ca4
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -153,7 +153,7 @@
/content/handbook/engineering/development/sec/security-risk-management/security-infrastructure/ @ryaanwells
/content/handbook/engineering/development/sec/security-risk-management/security-insights/ @svedova
/content/handbook/engineering/development/sec/security-risk-management/security-policies/ @alan
/content/handbook/engineering/training/ic-to-manager.md @dsatcher
/content/handbook/engineering/careers/training/ic-to-manager.md @dsatcher
/content/handbook/engineering/workflow/ @timzallmann @jeromezng @sgoldstein @dsatcher @m_gill

# CODEOWNER approvals are required for Code Review to support dogfooding approvals
+1 −1
Original line number Diff line number Diff line
@@ -250,7 +250,7 @@ There are five departments within the Engineering Division:
- [Engineering Career Development](/handbook/engineering/careers/)
- [Engineering Career Mobility Principles](/handbook/engineering/careers/#mobility-principles)
- [Emerging Talent @ GitLab](/handbook/hiring/)
- [Engineering Management](/handbook/engineering/management/)
- [Engineering Management](/handbook/engineering/careers/management/)

### Cross-Functional Prioritization

+15 −1
Original line number Diff line number Diff line
@@ -65,7 +65,7 @@ Career mobility is a part of career development, we support and encourage develo

Most important is the fork between purely technical work and managing teams. It's important that Engineering Managers self-select into that track and don't feel pressured. We believe that management is a craft like any other and requires dedication. We also believe that everyone deserves a manager that is passionate about their craft.

Once someone reaches a Senior-level role, and wants to progress, they will need to decide whether they want to remain purely technical or pursue managing technical teams. Their manager can provide opportunities to try tasks from both tracks if they wish. Staff-level roles and Engineering Manager roles are equivalent in terms of base compensation and prestige. Learn more about what it means to be a Staff-level engineer at GitLab in an [Engineering IC Leadership page](/handbook/engineering/ic-leadership/).
Once someone reaches a Senior-level role, and wants to progress, they will need to decide whether they want to remain purely technical or pursue managing technical teams. Their manager can provide opportunities to try tasks from both tracks if they wish. Staff-level roles and Engineering Manager roles are equivalent in terms of base compensation and prestige. Learn more about what it means to be a Staff-level engineer at GitLab in an [Engineering IC Leadership page](/handbook/engineering/careers/ic-leadership/).

### Trying the Management Track

@@ -153,6 +153,20 @@ On top of the success criteria we require that before moving into fulltime posit

For more details on logistics of ending an interim or acting period please refer to the [promotions and transfers page](/handbook/people-group/promotions-transfers/#interim-and-acting-roles).

## Career Development Resources

### Training and Learning

Explore our [training resources](/handbook/engineering/careers/training/) including secure coding best practices, Ruby on Rails performance, frontend development, GraphQL, and resources for Engineering Managers and Staff+ engineers.

### IC Leadership

Learn about [Engineering IC Leadership](/handbook/engineering/careers/ic-leadership/) at GitLab, including the four archetypes of Staff+ roles and the [Tech Lead role](/handbook/engineering/careers/ic-leadership/tech-lead/).

### Engineering Management

Discover resources for [Engineering Management](/handbook/engineering/careers/management/) including hiring, career development, project management, and team retrospectives.

## Roles

### Development Department
+4 −2
Original line number Diff line number Diff line
---
title: "Engineering IC Leadership"
aliases:
  - /handbook/engineering/ic-leadership/
---

## Engineering IC Leadership at GitLab: going beyond Senior level
@@ -58,7 +60,7 @@ Much of what each engineer said overlapped, but each had a unique perspective ba

There are [four common archetypes of Staff-plus roles in the industry](https://staffeng.com/guides/staff-archetypes/) that could explain this variability their perspective:

- The **Tech Lead** guides the approach and execution of a particular project. Most frequently they partner closely with a single manager, but sometimes they partner with two or three managers within a focused area. At GitLab, Tech Lead is not only an archetype, but it is also a [role](/handbook/engineering/ic-leadership/tech-lead)
- The **Tech Lead** guides the approach and execution of a particular project. Most frequently they partner closely with a single manager, but sometimes they partner with two or three managers within a focused area. At GitLab, Tech Lead is not only an archetype, but it is also a [role](/handbook/engineering/careers/ic-leadership/tech-lead)
- The **Architect** is responsible for the direction, quality and approach within a critical area, both today and stretching into the multi-year future horizon. They combine a deep knowledge of technical constraints, user needs, and organization level leadership.
- The **Solver** digs deep into arbitrarily complex problems and finds an appropriate path forward. Some focus on a given area for long periods, others bounce from hotspot to hotspot as guided by organizational leadership.
- The **Right Hand** is a partner and an extension of an executive-level manager, borrowing their scope and authority to operate particularly complex organizations. They provide additional leadership bandwidth to leaders of large-scale organizations.
@@ -72,7 +74,7 @@ There are [four common archetypes of Staff-plus roles in the industry](https://s
The most common archetype for a new Staff Engineer is the Tech Lead, as a
Senior Engineer may start showing Staff level behaviors emerging from their
team. At GitLab, this is not only an archetype but also a role assigned to
engineers on per-project basis. Read more about this on a dedicated [Tech Lead Handbook page](/handbook/engineering/ic-leadership/tech-lead).
engineers on per-project basis. Read more about this on a dedicated [Tech Lead Handbook page](/handbook/engineering/careers/ic-leadership/tech-lead).

A Staff Engineer partners with the Engineering Manager and the Product Manager
for milestone planning and helps teammates address complexity with their
+3 −1
Original line number Diff line number Diff line
---
title: "Tech Lead at GitLab"
aliases:
  - /handbook/engineering/ic-leadership/tech-lead/
---

## Tech Lead at GitLab

At GitLab, Tech Lead is an [archetype](/handbook/engineering/ic-leadership) and a role. When we think
At GitLab, Tech Lead is an [archetype](/handbook/engineering/careers/ic-leadership) and a role. When we think
about "Tech Lead" as an archetype we mean that Staff+ Engineers at GitLab are
supposed to exhibit patterns of behavior that make them act as technical
leaders, who partner with Engineering Managers and Product Managers to support
Loading