Engineering Management

Definition: Leading an engineering team by bringing together people, processes, and tools, while advocating quality engineering principles to the wider organisation and acting as a two way channel between the team and leadership.

So what? In a quality engineering context, the role combines people leadership with the quality engineer's mindset: empowering and protecting the team, managing what information flows in each direction, and feeding back to leadership how decisions are landing.

Example: Deciding whether an update is shared as a group announcement or handled one to one, depending on how sensitive or disruptive it is likely to be.

Definition: Engineering Management is the practice of leading a software engineering team across a mix of technical, people, process, and product responsibilities. The exact mix varies by organisation and by manager, ranging from hands-on technical leadership to people development, delivery coordination, or product ownership, and the same person may play a different mix of these as the team or business changes over time.

So what? There is no single, industry-wide definition of what an Engineering Manager does day to day. Understanding the different shapes the role can take (from writing code and setting architecture, to running 1:1s and clearing blockers, to managing stakeholders and roadmaps) helps teams and organisations set clearer expectations for the role rather than assuming it means the same thing everywhere.

Examples: A day built almost entirely around meetings (1:1s, team planning, cross-functional syncs) with a short block of quiet time for docs and reflection at the end. A manager who stays hands-on with code and architecture while also running the team (a "Tech Lead EM"), versus one who spends most of their time with stakeholders and end-users shaping the roadmap (a "Product EM"). A manager at a large, established business who spends real time on legacy systems, business context, and coaching consultants so the team isn't dependent on them.