Skip to content

Bootstrap Incubation Engineering career framework

Erran Carey requested to merge add-incubation-career-framework-page into master

Why is this change being made?

Creating a single source of truth for the DepartmentIncubation Engineering department's career development framework like we have for other engineering departments.

Currently incubation engineers need to base their career development against Division: Engineering without being able to point at specific accomplishments relating to our role while trying to compare our achievements with competencies listed under DepartmentDevelopment's career development page.

In future MRs we can add additional competencies to the specific Incubation Engineer role pages by level as suggested here https://gitlab.com/gitlab-org/incubation-engineering/meta/-/issues/23. For now this MR creates the basic structure we can build on with specific Incubation Engineer competencies that can be looked at for aligning expectations when having conversations around career development.

What is being changed?

Review app links for new pages:

  1. Added Incubation Engineering Department Career Framework page
    1. Added Incubation Engineering Department Career Framework: Intermediate page
    2. Added Incubation Engineering Department Career Framework: Senior page
    3. Added Incubation Engineering Department Career Framework: Staff page
    4. Added Incubation Engineering Department Career Framework: Principal page

Review app links for updated pages:

  1. Engineering Career Development page
    1. Added mermaid diagram for Incubation Engineering Department roles.
  2. Added Incubation Engineering career development page link to the Engineering Career Framework page.
  3. Added Incubation Engineering career development page link to the career framework navigation partial (rendered on children to the Engineering Career Framework page).

Screenshot_2023-02-15_at_15.25.44

Screenshot_2023-02-15_at_15.26.03

Screenshot_2023-02-15_at_15.40.02

Screenshot_2023-02-15_at_15.29.02

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Edited by Erran Carey

Merge request reports