Engineering Manager Job Description: Duties, Skills, Salary

Engineering Manager Job Description: Duties, Skills, Salary, and Career Path

The median annual wage for engineering managers, classified by the Bureau of Labor Statistics under Computer and Information Systems Managers, was $171,200 in May 2024, with employment projected to grow 15 percent from 2024 to 2034, much faster than the average for all occupations [1].

Key Takeaways

• Engineering managers plan, coordinate, and direct the work of software engineering teams while owning hiring, performance, delivery, and team health.
• The May 2024 BLS median annual wage for the umbrella occupation (Computer and Information Systems Managers) is $171,200, with about 55,600 openings projected per year over the decade [1].
• Typical entry requires a bachelor's degree in computer science or a related field plus five or more years of related experience, often as a senior software engineer or tech lead [1].
• Core skills are 1:1s, performance reviews, calibration, hiring loops, OKRs, roadmapping, budget cycles, and sociotechnical org design.
• The management track typically progresses Line Manager (M1) -> Senior Manager (M2) -> Group Engineering Manager (M3) -> Director (D1) -> Senior Director (D2). For the broader role context see our engineering manager career hub.

What Does an Engineering Manager Do?

An engineering manager is responsible for the output, growth, and well-being of a software engineering team, usually four to ten engineers. The role sits at the intersection of people management, technical decision-making, and cross-functional product leadership. BLS describes the parent occupation as professionals who "plan, coordinate, and direct computer-related activities in an organization" [1].

A typical week runs on three loops. The daily loop is standups, unblocks, code-review nudges, and incident triage. The sprint loop is planning, demos, retros, and roadmap check-ins with the PM and tech lead. The quarterly loop is OKR setting, headcount planning, performance reviews, calibration, promotion packets, and the budget conversations that determine whether the team grows or holds.

O*NET's task list for the parent SOC code captures the recurring duties verbatim: "direct daily operations of department, analyzing workflow, establishing priorities, developing standards and setting deadlines"; "meet with department heads, managers, supervisors, vendors, and others, to solicit cooperation and resolve problems"; "assign and review the work of systems analysts, programmers, and other computer-related workers"; and "recruit, hire, train and supervise staff, or participate in staffing decisions" [2].

The translation work is constant: engineer concerns into product trade-offs, product strategy into technical scope, ambiguous executive priorities into concrete quarterly goals. Camille Fournier captures the shift in The Manager's Path: a tech lead optimizes for the team's technical output; an engineering manager optimizes for the team's overall output, which sometimes means accepting slower technical progress in exchange for healthier collaboration or stronger hires [3].

Core Responsibilities

People management duties consume roughly 40 percent of the time:

1. Run weekly 1:1s with each direct report to surface blockers, give feedback, coach on growth, and detect early disengagement before it becomes a resignation.
2. Write and deliver performance reviews on a half-yearly or annual cadence, including 360 feedback synthesis, ratings, and calibration meetings where ratings are normalized across the org.
3. Run hiring loops: write the JD, partner with recruiting, screen candidates, design and run interview panels, debrief, and make hire/no-hire calls.
4. Develop careers: growth conversations, promotion packets, calibration defense, and off-cycle compensation cases when warranted.
5. Manage out underperformance: deliver hard feedback early, write PIPs when necessary, and own the outcome whether that is recovery, transfer, or termination.

Delivery and execution duties, roughly 35 percent:

1. Translate product strategy into a quarterly roadmap with the PM and tech lead, scoping what is achievable given capacity and dependencies.
2. Run the sprint cadence: planning, standups, demos, retros; keep commitments realistic and turn misses into learning.
3. Unblock the team: chase cross-org dependencies, escalate when external blockers stall progress, and shield the team from low-value churn.
4. Own incident response for systems the team operates, including blameless postmortems, action-item follow-through, and reliability investments.

Strategy and organizational duties, the remaining 25 percent:

1. Set and track OKRs aligned with broader engineering and company goals.
2. Participate in budget and headcount cycles, defending the case for new hires, conversions, and tooling spend.
3. Shape sociotechnical org design: service ownership, team boundaries, and when to split or merge teams.
4. Cross-functional alignment with product, design, data, security, and partner engineering teams [2].

Required Skills

The skills required to do the job well are not a smaller version of the senior-engineer skill set. They are a different set, and most new managers underestimate how different.

People skills come first. Effective 1:1s are a learnable craft: start with the engineer's agenda, listen more than talk, ask open questions, follow up on commitments week to week. Lara Hogan's Resilient Management argues that the 1:1 is the manager's primary instrument, and that what looks like a soft skill is a high-leverage operational practice [4]. Will Larson, in An Elegant Puzzle, frames the manager's job as systems work where the system is the team itself: input quality (hires), throughput (delivery), and output quality [5].

Hiring is its own discipline. A good engineering manager calibrates the interview loop so it predicts on-the-job performance, writes feedback the next interviewer can use, and avoids the common failure mode of hiring people who agree with the manager rather than challenge them. Andy Grove's High Output Management anchors the leverage view: a manager's output is the output of the people they touch, and hiring is the highest-leverage activity available [6].

Performance management requires comfort with conflict. Fournier writes that the moment a new manager flinches from direct, specific feedback is the moment the team starts to drift [3]. Calibration tests the same skill at the org level: defending an engineer's rating against peers defending theirs, with limited promotion slots in the room.

Technical judgment remains essential. The manager has to know enough to spot when an architectural choice will cause a year of pain, when a deadline is padded, and when a tech-lead recommendation is solid. Charity Majors's "Engineer/Manager Pendulum" argues that staying technically credible, including by occasionally swinging back to IC, keeps managers grounded [7].

Operational rhythm rounds out the kit: OKR-setting that produces real focus, roadmaps that survive contact with reality, budget cycles, and org structures where team boundaries match system boundaries.

Education and Certifications

BLS reports that the typical entry-level education for the parent occupation is a bachelor's degree, with five or more years of related work experience [1]. In practice, almost every engineering manager in software comes through an IC path: a computer science degree, four to seven years as a software engineer, then promotion or transfer into management.

An MBA is uncommon and not a meaningful advantage. The dominant path is practical experience as a senior engineer or tech lead, ideally with mentorship from a strong existing manager. Michael Lopp, writing as Rands, has long argued that the best engineering managers are made on the job, by managers who actively invest in their successors [8].

There is no industry-standard certification for engineering management. Books fill that gap. The most cited canon: Fournier's The Manager's Path, Will Larson's An Elegant Puzzle and the StaffEng project, Lara Hogan's Resilient Management, Andy Grove's High Output Management, Lopp's Managing Humans, and Ben Horowitz's The Hard Thing About Hard Things, particularly its chapters on layoffs, executive hiring, and peacetime versus wartime [3][4][5][6][8][9]. Gergely Orosz's Pragmatic Engineer newsletter and Charity Majors's charity.wtf are the strongest current sources of practical operating advice [7][10].

Work Environment and Schedule

BLS notes that computer and information systems managers "are employed in many industries. They usually work in an office setting. Most work full time, and some work more than 40 hours per week" [1]. In software, hybrid and fully remote arrangements are common, and many engineering manager roles at technology companies are listed as remote.

The calendar is meeting-heavy: a 30- to 60-minute 1:1 per direct report, team standups, sprint planning, a skip-level with the manager's manager, and cross-functional meetings with product, design, data, and partner teams. Maker-time blocks, where they exist, tend to go to writing: performance reviews, promotion packets, roadmap docs, postmortems, and 1:1 prep.

On-call rotations vary. Some managers carry a pager for the systems their team owns; others rotate it and only get paged for major incidents. Either way, the manager owns the response, the postmortem, and the follow-through. Travel is modest, mostly quarterly on-sites with distributed teams and occasional offsite planning or recruiting events.

Salary by Experience

The BLS-reported May 2024 median annual wage for Computer and Information Systems Managers is $171,200, or $82.31 per hour [1]. That figure spans the full umbrella occupation, including IT and infrastructure managers in non-software industries, so software-specific compensation at major tech employers tends to run substantially higher.

For market-rate compensation by level, the most reliable public source is levels.fyi. The compare tool at levels.fyi/comp.html?track=Engineering Manager shows real distributions for the engineering manager track at companies including Stripe, Meta, Google, Airbnb, Netflix, Anthropic, Linear, and Databricks.

The structure that recurs across the industry:

• Line Engineering Manager (M1): 4 to 10 direct reports, single team. Total comp at major tech employers usually clears the senior software engineer band.
• Senior Engineering Manager (M2): a larger team or two small teams, often with a tech lead per team. Comp approaches the staff engineer band.
• Group Engineering Manager (M3): multiple teams through other managers, 15 to 40 engineers. Comp overlaps the principal engineer band.
• Director (D1) and Senior Director (D2): org-level scope, multiple groups, typically reporting into a VP of Engineering.

BLS does not publish a software-specific engineering manager figure, so benchmark by triangulating BLS with levels.fyi data for the specific company tier and scope.

Career Outlook

BLS projects 15 percent employment growth for Computer and Information Systems Managers from 2024 to 2034, much faster than the average for all occupations, with about 55,600 openings projected each year over the decade and total employment of 667,100 in 2024 [1]. The driver is the same one driving most software-adjacent roles: organizations continue to expand their digital footprint, which increases the number of engineering teams, which increases the number of engineering managers needed to lead them.

Two countervailing pressures shape the outlook. Engineering organizations at large tech companies have been flatter since the 2022-2023 layoff cycle, with wider spans of control and fewer middle layers. Meanwhile, AI-assisted engineering has not, so far, reduced the need for human management; the leverage gain shows up in engineers' output rather than in lower management headcount. Organizations that try to operate without managers, relying purely on tech leads, often re-add the role within a year or two when delivery, hiring, and performance management start to slip.

How to Become an Engineering Manager

The most common path is the IC-to-manager pivot. The candidate spends four to seven years as a software engineer, reaches the senior or staff level, takes on tech-lead responsibilities, and then accepts a manager role internally or interviews for one externally.

1. Earn a bachelor's degree in computer science, software engineering, or a closely related field. Self-taught and bootcamp paths into engineering are viable, though manager hiring at large companies still skews toward four-year-degree backgrounds.
2. Build five or more years of software engineering experience, reaching senior level and ideally taking a tech-lead rotation that exposes you to project planning, mentorship, and cross-functional collaboration [1].
3. Develop the manager-adjacent skills early: run a project end-to-end, mentor a junior engineer, write a postmortem, lead a hiring loop. Each is a rep of a core EM responsibility.
4. Have an honest conversation with your current manager about the pivot, ideally a year before you want to make it. Read Charity Majors's "Engineer/Manager Pendulum" first, so you understand the trade-offs and the option to swing back [7].
5. Take a small team first. A team of three to six engineers, with a strong manager above you. Skipping straight from senior IC to manager-of-managers usually fails.
6. Read the canon and find a mentor. Fournier, Larson, and Hogan are the highest-yield reading [3][4][5]. A mentor one or two levels ahead, in a similar organization, accelerates everything.
7. Plan the longer arc. M1 -> M2 -> M3 -> D1 -> D2 typically spans 8 to 15 years, with each step adding scope rather than just title.

FAQ

Is engineering manager a coding role? Mostly not. Most engineering managers stop being primary code authors within a quarter or two. Some keep small contributions during low-meeting weeks, but the leverage is in hiring, unblocking, and developing engineers, not in writing PRs [7].

How is engineering manager different from tech lead? A tech lead owns technical direction without formal people-management authority. An engineering manager owns hiring, performance, compensation, and headcount in addition to delivery. Many strong managers tech-lead first; few do both at once successfully [3].

Do engineering managers do performance reviews? Yes. Writing reviews, defending ratings in calibration, and turning the conversation into clear next steps is core and one of the hardest parts of the role [3][4].

What is the salary for an engineering manager? The BLS May 2024 median for the umbrella occupation (Computer and Information Systems Managers) is $171,200 [1]. At major tech companies, total compensation for line and senior managers typically runs higher; for company- and level-specific data, levels.fyi is the most reliable public source.

Is engineering management a good career? For people who get energy from helping others succeed and working through systems rather than directly, yes. For people whose primary energy comes from shipping their own code, the role often feels like a loss of identity. The honest test is a small management rotation [7].

What's the career path after engineering manager? M1 -> M2 -> M3 -> D1 -> D2, then VP of Engineering and CTO. Some managers swing back to senior IC roles (staff or principal engineer); that is a valid path, not a failure [7].

What is the job outlook for engineering managers? BLS projects 15 percent employment growth from 2024 to 2034 for Computer and Information Systems Managers, much faster than the average for all occupations, with roughly 55,600 openings each year [1].

Sources

1. U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Computer and Information Systems Managers, last modified August 28, 2025.
2. O*NET OnLine, 11-3021.00 Computer and Information Systems Managers.
3. Camille Fournier, The Manager's Path, O'Reilly, 2017.
4. Lara Hogan, Resilient Management, A Book Apart, 2019.
5. Will Larson, An Elegant Puzzle: Systems of Engineering Management, Stripe Press, 2019; lethain.com; StaffEng project.
6. Andy Grove, High Output Management, Vintage, 1995.
7. Charity Majors, "The Engineer/Manager Pendulum," charity.wtf, 2017.
8. Michael Lopp, Managing Humans, Apress, multiple editions; Rands in Repose.
9. Ben Horowitz, The Hard Thing About Hard Things, Harper Business, 2014.
10. Gergely Orosz, The Pragmatic Engineer.