Skip to content
This repository was archived by the owner on Aug 16, 2021. It is now read-only.

Latest commit

 

History

History
209 lines (192 loc) · 7.06 KB

engineering-manager.md

File metadata and controls

209 lines (192 loc) · 7.06 KB

Engineering Manager

👩‍👨 People

Level 2 Level 3
  • Demonstrate people development skills of individual contributors
    • motivating
    • coaching
    • mentoring
    • empowering
    • helping individual to increase their performance
  • Manage performance of significant number of individuals (6)
    • 1:1
    • Onboarding new members, helping them to make the most of their onboarding.
    • Career development & progression
    • Handling leaving members
  • Engineering management team
    • Participate actively in led by other departemental initiatives
    • Participate actively in management meetings
  • Performance calibrations
    • Read and share feedback for some non line managed individuals
  • Promotions and In-band payrise
    • Read submissions for non line managed individuals
  • Demonstrate people development skills of individual contributors
    • Is being recognised for helping individuals to improve
    • Provide extensive feedback to indiviudal on how to improve
  • Performance calibrations
    • Read and share feedback for a significant number of non line managed individuals
  • Promotions and In-band payrise
    • Read and share feedback for some non line managed individuals
  • Quarterly rotation
    • Actively look for opportunities in the coming quarters for managed individuals
    • Help resolve rotation gap suggesting individuals that would best fit
  • Hiring & Handling resignation
    • Suggest improvements to hiring process and activities
    • Convince people to remain when handling their resignation

🚚 Delivery

Level 2 Level 3
  • Delivery focus
    • Champions the importance of delivery in their team
    • Helps to unblock obstacles
    • Supports technically their team in delivering its goals.
    • Share with a wider group importance of delivery
  • Delivery pace
    • Is conscious about team delivery pace
    • Understand impact of management on it.
    • Identify bottlenecks in delivery pace
    • Collaborate on continuously improving pace of their team
  • Health
    • Participate in definining key metrics for systems owned by team
    • Ensure team monitors key metrics for systems owned by team
    • Evaluate and decide time to spend on health each quarter
    • Demonstrate improvements on specific key metrics
  • Technical contribution
    • Continue to write code at least once a week and release features, but avoid being on the critical path.
    • Continue to review significant PR and talking through problems with team members
    • Continue to help diagnosing issue or fix some of them
  • Context awareness
    • Understands the constraints placed on the business.
    • Demonstrate flexibility to adapt to those constraints.
    • Understands the capabilities of their team and communicates that clearly to stakeholders.
  • Delivery pace
    • Resolve bottlenecks in delivery pace
    • Share with senior managers opportunity to improve
    • Ensure small changes with high impact are released quickly not just added to the backlog
  • Health
    • Ensure the right balance between Health and OKR between quarters,engaging product and scrum master in the process
  • Context awareness
    • Suggest reasonable changes to the constraints that help solve stakeholder issues

▶️ Leadership

Level 2 Level 3
  • Team
    • Communicate progress and achievements to the department
    • Recognise outstanding works from individuals within team
    • Ensure there is, but don't orgnanise, demo of team work
    • Ensures that all members of their team have a clear grasp of the KR for their products and that they are focused on improving them
  • Stakeholders
    • Communicate technical challenges and opportunities in the domain area of their team in a clear way to stakeholders
  • Strategy
    • Share technical opportunities with their manager
    • Participate in defining OKR team with product manager
  • Ownership
    • Clearly communicate and share ownership of existing systems
    • Help decide where ownership of new systems seat
  • Evangelise simplicity
    • Engage with product in removing rarely used features
    • Encourage clear and readable code, organised in way that divides implementation in independant units of work
    • Promote a change that reduce size of code base

💷 Costs Managements

Level 2 Level 3
  • Health
    • Monitor system and delivery pipeline health
    • Participate in defining health tasks
    • Share with stakeholders importance of health for sustainability
  • Operating costs
    • Understand details of costs structure
    • Participate in costs reduction initiatives
    • Ensure costs remain within allocated budget
  • Operating costs
    • Evaluate costs of new projects providing recommendations for cost-efficiency and trade-offs