Career & Leadership › Career Growth

Engineering Manager

Leading people: hiring, growth, delivery and team health.

An engineering manager is responsible for helping a team deliver useful work while supporting its people and keeping the working environment healthy. The role commonly includes coaching, feedback, hiring, planning, coordination, and resolving organizational obstacles; the exact balance varies by company.

A manager does not need to make every technical decision. Their job is to ensure the right decisions are made by people with relevant context, that ownership is clear, and that risks reach the right level. For example, a team facing a migration may need the manager to negotiate capacity and resolve a dependency while engineers shape the technical approach.

People management has real trade-offs: time spent on planning or a difficult personnel issue is time not spent implementing code. Managers should be transparent about priorities and avoid promising outcomes the team cannot control. They also need to give feedback consistently rather than waiting for formal review cycles.

Backend managers often balance feature delivery with reliability and on-call load. Frontend managers coordinate design, release timing, and quality across surfaces. Data managers align source owners, consumers, and governance needs. Keep one-to-ones focused on growth and obstacles rather than status alone. Write down role expectations and revisit them when team size or responsibilities change, so feedback stays grounded.

Backend, frontend, and data teams have different constraints, and managers should learn enough to ask useful questions without pretending to be the domain expert. If you are considering the role, shadow the work and discuss expectations with current managers. See IC vs management track, delegation, and managing up.