Engineering managers wear many hats. From people development and delivery management to hiring and stakeholder communication, the role encompasses a broad range of responsibilities that vary by organisation but share a common core. This guide provides a comprehensive overview of what you are accountable for and how to balance competing priorities.
People Development and Performance
People development is the responsibility that most distinguishes engineering managers from other roles. You are directly accountable for the growth, engagement, and performance of every person on your team. This includes regular one-on-ones (typically weekly), formal performance reviews (quarterly or bi-annually), career development conversations, and continuous coaching and feedback.
Performance management is the aspect of people development that new managers find most challenging. Setting clear expectations, measuring progress against those expectations, recognising strong performance, and addressing underperformance are all part of the job. The key is consistency — apply the same standards to everyone on the team and address issues promptly rather than letting them fester.
Retention is a responsibility that is often invisible until it becomes a problem. The best engineering managers proactively invest in their team members' engagement by understanding what motivates each person, creating opportunities for growth, ensuring fair compensation, and building a team culture that people want to be part of. When a valued team member leaves, it is worth reflecting on whether there were signals you missed or actions you could have taken.
Delivery and Execution
Engineering managers are accountable for their team's delivery — ensuring that the team ships high-quality software on a predictable cadence. This does not mean micromanaging every task. It means creating the conditions for effective delivery: clear priorities, reasonable scope, sufficient resources, and well-designed processes.
Sprint management, backlog grooming, and capacity planning are the operational backbone of delivery. You need to ensure that the team has a clear understanding of what they are building, why it matters, and what 'done' looks like. You also need to protect the team's capacity from scope creep, interrupt-driven work, and unsustainable pace.
Quality oversight is another delivery responsibility. You set the standards for code quality, testing, documentation, and operational readiness. While you delegate the day-to-day enforcement of these standards to tech leads and senior engineers, you are ultimately accountable for the quality of what your team ships.
Hiring and Team Building
Hiring is one of the highest-leverage activities an engineering manager undertakes. A single great hire can elevate the entire team; a single poor hire can create months of disruption. You are responsible for the end-to-end hiring process for your team: defining requirements, sourcing candidates, designing interview loops, making hiring decisions, and onboarding new team members.
Team composition is a strategic responsibility that goes beyond filling open positions. You need to think about the balance of skills, experience levels, and perspectives on your team. A team of all senior engineers may lack the mentoring opportunities that keep people engaged. A team without sufficient senior expertise may struggle with complex technical challenges. Thoughtful team design is an ongoing responsibility.
Onboarding is often underinvested despite being critical to the success of new hires. A structured onboarding programme that covers technical context, team processes, cultural norms, and relationship building significantly accelerates new team members' productivity and engagement. As the engineering manager, you own this process and should continuously improve it based on feedback from recent hires.
Stakeholder Management and Communication
Engineering managers serve as the bridge between their team and the rest of the organisation. You translate business priorities into technical work for your team and communicate your team's progress, challenges, and needs back to stakeholders. This translation function is critical — miscommunication in either direction leads to misalignment, frustration, and wasted effort.
Your primary stakeholders typically include your product manager (priorities and scope), your own manager (team health and strategic alignment), peer engineering managers (cross-team dependencies), and senior leadership (organisational goals and resource allocation). Each relationship requires a different cadence and communication style.
Managing expectations is a subtle but essential part of stakeholder management. Be honest about what your team can deliver, surface risks early, and push back on unreasonable demands. Stakeholders respect engineering managers who communicate clearly and honestly, even when the message is not what they want to hear. The managers who consistently over-promise and under-deliver erode trust over time.
Balancing Competing Responsibilities
The breadth of the engineering manager role makes prioritisation essential. On any given day, you might need to prepare for a performance review, unblock a technical issue, interview a candidate, resolve a cross-team dependency, and update your director on a project's status. You cannot do all of these equally well, so you need to develop a framework for deciding where to invest your attention.
A useful prioritisation framework is: people first, then delivery, then everything else. If a team member is struggling, that takes priority over a sprint planning meeting. If a critical delivery is at risk, that takes priority over a non-urgent hiring conversation. This framework is not rigid — context matters — but it provides a default that keeps you focused on the highest-impact activities.
Time management is the practical skill that makes everything else possible. Block your calendar for deep work, batch similar activities together, and protect your one-on-one time from cancellation. Many engineering managers fail not because they lack the skills for any individual responsibility, but because they have not developed the time management discipline to handle all of them effectively.
Key Takeaways
- People development is your most distinctive responsibility — invest heavily in one-on-ones, feedback, and coaching
- Delivery accountability means creating conditions for effective execution, not micromanaging tasks
- Hiring is high-leverage — approach it as a strategic activity, not an administrative burden
- Stakeholder management requires translating between technical and business contexts in both directions
- Prioritise people first, then delivery, then everything else to manage the breadth of the role
Frequently Asked Questions
- How do I manage all these responsibilities without burning out?
- The key is delegation and time management. You do not need to do everything yourself — delegate appropriate responsibilities to tech leads, senior engineers, and other team members. Block your calendar to protect time for deep work and one-on-ones. Learn to say no to low-priority requests. And invest in your own well-being — exercise, sleep, and time away from work are not luxuries, they are necessities for sustainable management.
- Which responsibility should get the most time?
- People management typically deserves forty to fifty per cent of your time. This includes one-on-ones, feedback, coaching, performance management, and career development. Delivery management takes another twenty to thirty per cent. Hiring and stakeholder management share the remainder. These proportions shift based on circumstances — during a hiring push, hiring might temporarily dominate your calendar — but the people management core should remain consistent.
- How do responsibilities change as I advance?
- As you advance from EM to senior EM to director, the balance shifts. At the EM level, most of your time goes to direct people management and team-level delivery. At the senior EM level, you add organisational contributions and cross-team initiatives. At the director level, you focus on strategy, organisational design, and developing your management team. The specific responsibilities evolve, but the core competencies — people leadership, communication, and judgement — remain relevant at every level.
Explore the EM Field Guide
Our comprehensive field guide provides detailed frameworks and templates for every core engineering manager responsibility, from one-on-ones and hiring to delivery management and stakeholder communication.
Learn More