Example · Engineering Manager

88% of your week as an engineering manager is still yours.

Teams are getting wider and managers are getting fewer. Leading people who ship stays with you.

Make my planA typical week at the middle pace. Your plan uses your own tasks.

Are engineering manager jobs disappearing?

In a typical week at the middle pace, 53% of this work needs your judgment and 35% is work you do using AI. AI could do about 12%. Big tech has been removing manager layers since 2023, and the reasons given were cost and speed rather than models. Google said in August 2025 it had 35% fewer managers of small teams than a year earlier.

Read more

Amazon set a goal in September 2024 to raise its ratio of individual contributors to managers by at least 15%, then cut 14,000 corporate roles in October 2025 and 16,000 more in January 2026 while "reducing layers."

Most of what makes your seat worth having is the least exposed work you do: people, hiring, delivery calls. About 53% of your week sits there. The risk to you is the count of seats. A manager who can show a well-run wide team, with agents in the workflow and evidence in hand, is the one who keeps a seat when two teams merge.

The week, task by task

Who does each hour of a typical 40-hour week.

See every task
You53% · 21 hours

Needs your judgment.

  • 1:1s, coaching and career growth12%
  • Delivery accountability: commitments, trade-offs, saying no10%
  • Performance management: calibration, improvement plans, exits8%
  • Cross-team alignment and managing up7%
  • + 3 smaller tasks16%
You using AI35% · 14 hours

AI does the slow parts. You still own it.

  • Code and design review, technical direction10%
  • Hiring admin: job descriptions, interview kits, resume screens7%
  • Hands-on coding: small fixes, prototypes, spikes6%
  • Sprint planning, estimation and capacity allocation6%
  • + 1 smaller task5%
AI12% · 5 hours

AI could do most of it.

  • Status updates, delivery reports and metric roll-ups for leadership8%
  • Meeting notes, ticket hygiene and backlog admin5%
Why some tasks still need a person
1:1s, coaching and career growth

This rests on relationships and context. Trust built over months is the input. A model can draft a growth plan, but it cannot know your strongest engineer is interviewing elsewhere because of a family move.

Performance management: calibration, improvement plans, exits

This needs context and the accountability you carry for the employer. Someone must stand behind a rating or a termination in front of HR and sometimes a lawyer.

The hire or no-hire call

This depends on verification. A bad hire is discovered around month six and costs a quarter. The debrief is where your judgment matters most.

Delivery commitments and saying no

The accountability here is informal. Your name sits next to the date. When scope has to be cut, product and leadership want one person who will answer.

Incidents and production risk calls

This needs verification and accountability. Deciding whether to roll back at 2 a.m. takes a person with context and authority.

Good to know

What is hard about this field, and what you can do about it.

The hard truth

Manager engagement is falling faster than anyone else's.

Managing people is getting harder on the people doing it. Worldwide, manager engagement dropped five points in a year, while the people they lead held steady.

What you can doFind a peer group of managers outside your team. Ask for formal manager training, and drop one recurring meeting to make time for coaching.
Sources (2)

What's the next role for an engineering manager?

Plan A is the best move inside the work you do now.

APlan A

Grow in the job you have

The main focus. Most weekly sessions build toward it.

Your next stepBecome a senior engineering manager who owns AI delivery for a group
Each week
4 sessions
Ready in
About 90 days for the evidence
Why it fits

Why you. You already run a team where agents are being adopted, and you sit where output, review and quality meet.

The gap. You don't yet have measured numbers, written rules for agents or a tech lead strong enough to own review.

The trade-off. You are building the case that one manager can run more people. It may be used to widen your span or merge a peer's team.

2 other moves that fit
  • Lead developer AI enablement or productivityReady in about 6 to 12 months
  • Become a manager of managersReady in about 12 to 24 months

What's a plan B for software engineering managers?

Plan B is meant to be different from this job. It was picked because skills from this role carry over.

BPlan B

Get ready for a new kind of job

A second option. A newer job AI is creating that these skills already fit.

A job to aim forDeveloper AI enablement lead

You already set your team's review rules and own delivery quality, which is this job across several teams.

Each week
1 session
Outlook
Hiring now
Pay
$119.3K to $310.5K a yearTwo senior US postings, June 2026: MGM Resorts and HPE (California, 10+ years, now closed).
2 other options
  • AI enablement and adoption leadYou coach engineers through new habits in 1:1s and team rituals, which is how AI adoption actually sticks.
  • Agent workforce managerYou already set goals, review output and decide who approves what for a team, and agents need the same.

In your own plan you can switch to any of the 47 roles.

The 13 weeks

Small steps that add up. One plan for both: most sessions build Plan A, one a week builds Plan B.

By week 13 you will have

AFor Plan A

  • An evidence file for each person
  • A one-page memo asking for a senior manager title
  • A developer AI enablement playbook

BAnd for Plan B

  • A 60-day agent rollout plan
  • A developer AI enablement playbook
Month 1Weeks 1 to 4
  1. 1Measure your week
  2. 2Start an evidence file
  3. 3Measure review load
  4. 4Write rules for AI agents

You finish withTeam rules for AI agents posted

Month 2Weeks 5 to 8
  1. 5Hand off the status update
  2. 6Grow other reviewers
  3. 7Test a wider team
  4. 8Hire with AI in the room

You finish withA scorecard for judging AI-assisted work

Month 3Weeks 9 to 13
  1. 9Keep a delivery ledger
  2. 10Measure again
  3. 11Practice calibration
  4. 12Make your ask
  5. 13Build proof you can take with you

You finish withOne application sent for a manager role

Three courses from the plan
  • AI Fluency: Framework & FoundationsAnthropic Academy · Free

    Yes. It is a fast, free baseline for weeks 1 and 2.

  • AI Capabilities and LimitationsAnthropic Academy · Free

    Yes. It names the failure types you will see in agent-written code.

  • Claude Code in ActionAnthropic Academy · Free

    Yes, if your team uses coding agents. It covers permissions and hooks, which become your team rules.

Checked 2026-10-15.

The fuller picture

Risks beyond AI: highDelayering risk

Manager seats get cut when companies chase cost and speed, and that started before agents could write much code. When two teams merge, one manager seat goes, and the work that held does not save the person whose team was folded in. Agents make the case for wider spans easier to argue, which is why this risk outranks the AI one for your seat.

Where this could be wrong
  • At a startup you may already be a player-coach with four reports, and coding is a much bigger part of your week than we scored.
  • The review-load problem may be a 2026 artifact. If AI review tools get good, code review becomes one of the more exposed tasks and the player-coach case weakens.
  • Span widening could stall if more companies hit Meta's problem. If that happens, the risk of losing manager layers drops from high to moderate.
  • We did not score agents running 1:1 prep or calibration evidence. If employers allow it, performance work becomes more exposed, with AI doing part of it.

This is an example. Your plan uses your own week.

Make my plan

Also matched: engineering manager, software engineering manager, software development manager. Research checked 2026-10-15. Page updated .