Run Engineer → Run Manager

A realistic transition from Run Engineer to Run Manager: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 55%. Difficulty: Medium.

Difficulty: Medium6 stepsDuration: 9 to 13 monthsOverlap: 55%

Transition from Run Engineer to Run Manager.

Transferable skills

  • Run management
  • Incident management
  • ITIL
  • Automation roadmap
  • Vendor management
  • Risk management

Skills to learn

  • SLA & KPI
  • Team leadership
  • Shift planning
  • Reporting

Step-by-step learning plan

  1. 1. Build on your Run Engineer experience

    2–4 weeks

    Leverage

    • Run management
    • Incident management
    • ITIL
    • Automation roadmap

    Map transferable skills — Run management, Incident management, ITIL — against what a Run Manager needs.

  2. 2. Learn the core of the Run Manager role

    6–10 weeks

    Learn

    • SLA & KPI
    • Team leadership

    Technologies

    JiraConfluencePower BI

    Cover the biggest gaps first: SLA & KPI, Team leadership.

  3. 3. Master advanced Run Manager skills

    6–10 weeks

    Learn

    • Shift planning
    • Reporting

    Technologies

    ExcelTeamsOffice 365

    Handle the advanced topics: Shift planning, Reporting.

  4. 4. Get productive with the Run Manager toolchain

    4–8 weeks

    Technologies

    JiraConfluencePower BIExcelTeamsOffice 365SlackMFA

    Be hands-on with Jira, Confluence, Power BI and the rest of the target stack.

  5. 5. Practise Run Manager work in real conditions

    4–8 weeks

    Ship a portfolio project or take on Run Manager tasks at work.

  6. 6. Get certified and position yourself as a Run Manager

    4–8 weeks

    Technologies

    ITIL 4 Managing ProfessionalPRINCE2 FoundationLPIC-2

    Update your CV and LinkedIn around Run Manager, then apply to target roles.

Alternative routes