# Engineering Manager Role (EM)

# Responsibilities

  • To develop a healthy environment, aligned with Holaluz values (opens new window) and with the engineering vision and strategy.

  • To ensure that their purpose team has the right people and the right skillset, including hard and soft skills (opens new window). In agreement with the CTO, EM has the responsibility to decide hiring and firing. Movement of Individual Contributors (IC) between teams requires an agreement between EMs and Product Owners (PO) of both teams.

  • To be accountable (opens new window) for the throughput of the purpose team, where throughput is measured by the given business value, and to work in its continuous improvement. To collaborate with product people, UX, data scientists, and stakeholders to achieve that.

  • To deal with conflicts between individuals and engagement and performance issues and execute the necessary actions to solve those problems looking to maximize the benefits for the whole purpose team.

  • To work in the career path and personal growth of the ICs, aligning that with the team needs.

  • To ensure salaries are fair with the value given by the IC, fair inside the team, and that they feel fairly paid. In case there's an issue in this topic, ensure that the CTO is aware and have all the necessary information to take the proper actions. The final decision about salaries is the responsibility of the CTO, who ensures consistency between teams and also from a company and market perspective.

  • To align themselves with the CTO and other EMs and make sure to transmit to their team a shared direction and strategy, unified and uniform. Each EM should apply the most suitable techniques for each context and situation, but the strategy and the vision are common.

  • To ensure that the team have and know their domain and objectives, and have the tools to be sure that it's working and evolving as expected. It includes, but is not limited to, server monitoring, data governance, business functionalities, repositories, alerts, operative maintenance, and security, which they are responsible for.

  • To have experience in developing the IC job and abstraction capability enough to guide and technically challenge the team. To take part in technical decisions and help tiebreaking technical disagreements, besides not necessarily being the technical expert of the team.

  • To be very involved in the day-to-day of their team. To actively participate in the work dynamics: plannings, pairings, check PRs, etc., being that their primary workload and keeping enough time to do a good follow-up of the IC and strategical work with the EMT. The balance between both activities might change depending on team needs, but none of them should go under 25% of work time in any case.

  • We use a delegation board (opens new window) to have a precise and shared vision of the delegation levels in specific responsibilities between the CTO and each EM.