Example · Director of Engineering
Companies have been removing director layers, and agents make that case easier to argue. Keep your seat by owning the decisions your VP cannot make from a dashboard.
34 of your 40 hours still need you
- 23 stay yours
- 11 faster with AI
- 6 tools could take
A typical week at the middle pace. Your plan uses your own tasks.
Is engineering management a dying career?
By our task-by-task count, 34 of a typical 40-hour week as a director of engineering still need a person. Tools could already take about 6 hours. The work that justifies a director, coaching managers, org design, calibration and multi-team trade-offs, is the least exposed work you do. About 58% of your week sits there.
Read more
The pressure is on the seat itself. Google cut manager, director and VP roles by 10% (reported December 2024). Meta planned to cut vice president roles from about 300 to about 250 (reported June 2024). Microsoft named "removing layers of management" in its July 2025 cuts, and Intel's CEO said in April 2025 that "many teams are eight or more layers deep."
A director layer adds a hop between the VP and the managers who do the work. When status, relay and roll-ups move to agents, that hop is easier to remove. The director who keeps a seat is the one whose org visibly runs better because of calls only they make.
The hard truth
Wider manager spans thin out the layer you lead.
Engineering managers now run bigger teams, so the same org needs fewer of them. Hiring is tilting toward senior individual contributors.
Sources (2)
- Engineering managers at large tech companies now oversee about 12 engineers, up from about 10 in 2019. SignalFire, State of Talent Report 2026, 2026-06
- Senior IC and staff roles are growing as a share of hiring, while engineering manager roles are flat or declining. SignalFire, State of Talent Report 2026, 2026-06
What stays yours
Coaching engineering managers and growing new ones
This rests on relationships and context. Whether a new manager is ready for a second team comes from months of watching them run one. A model can draft a development plan. It cannot see that your best manager is burning out.
Org design: team boundaries, scope and spans
You carry this accountability for the employer, and it takes context. Someone has to stand behind a reorg that moves dozens of people, and answer when it breaks a team.
Calibration, promotions and exits across teams
This takes accountability and context. You make ratings consistent across several managers and defend the result to your VP and HR.
Multi-team delivery and cross-org trade-offs
You hold this accountability informally. When two teams want the same engineers, or the quarter slips, your VP wants one person who will decide and answer.
Senior hiring: managers and staff engineers
This takes careful checking. A bad manager hire can hurt a team for much longer than a quarter, and you own the relationship through the close.
What's the next role for a director of engineering?
Plan A is your best move inside the work you do now. Most sessions in the 13-week plan build toward it.
- A
Director who owns AI-enabled delivery for a group
Why it fits
Why you. You already sit where several teams' output, quality and headcount meet.
The gap. You don't yet have measured numbers across your teams, written shared standards or a capacity model that includes agents.
The trade-off. You are building the case that fewer people can deliver more, which may be used to cut headcount in your own group.
Other moves that fit
These are also good bets in this field. Read them if Plan A doesn't suit you.
Lead developer AI enablement
Why it fits
Why you. You have changed how several teams work, which is what these roles ask for. Rocket Companies (August 26, 2026) asks for someone who has "led a team whose output was consumed by other engineering teams." Money Forward in Tokyo (October 15, 2026, ¥9M to ¥18M) asks for experience measuring AI's impact on speed and quality.
The gap. These roles want hands-on depth with coding agents, which directors often lack.
The trade-off. Most of these postings are at manager level, so it may be a step down in title, and the role may fold into platform teams.
Move to principal engineer or architect
Why it fits
Why you. You came up as an engineer and you still run architecture reviews.
The gap. You have not shipped hands-on in years, and interviews for staff-level roles and above test that.
The trade-off. You give up the people work, which is your most protected work, and compete with former managers making the same move.
What's a plan B for engineering directors?
Plan B is a job AI is creating that these skills already fit. One session a week in the plan trains you for it, so it is ready if your job shrinks or you want a change.
BPlan B, picked for this role
Developer AI enablement lead
You already set shared rules for review and definition of done across teams, and measuring whether agents help is the same job.
Other options
AI enablement and adoption lead
You coach managers through org change and new habits, which is how AI adoption actually sticks across a large group.
AI/ML technical program manager
You already run multi-team plans and trade-offs, and AI releases add model versions and evaluation gates to track.
In your own plan you can switch to any of the 47 roles.
The first two weeks
The first 2 of 13 weeks. Each week has three sessions of 30, 45 and 30 minutes, plus one 40-minute Plan B session. By week 13 you'll have a decision log of calls only you made, a one-page memo asking to lead AI work across your teams, and a developer AI enablement playbook.
- Week 1: Measure your week
What you do
- ATrack one week of your work against the task list on this page. Write down roughly how many hours went to each task.
- AList every recurring meeting and report you own. Note who reads each one and what they do with it.
- AList the decisions you made last quarter that no one else in your org could have made.
- BTake the first half of Anthropic's free AI Fluency course. Write down its four habits for working well with AI.
- Week 2: Show what your layer adds
What you do
- AFor each decision on your list, write what it was worth in hours, dollars, people or risk.
- AAsk your VP in writing which three outcomes they most need from your group next half.
- APut a 10-minute weekly reminder on your calendar to add one line to the decision log.
- BFinish the AI Fluency course and pass its final assessment.
Three courses from the plan
Checked 2026-10-16.
- 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 helps you judge when an agent roll-up can be trusted.
- Introduction to agent skillsAnthropic Academy · Free
Yes. It is short, and it shows what could be standardized across teams.
Risks beyond AI: highLayer removal risk
The first-line manager's risk is a wider span. Yours is the whole layer going, with your managers kept and moved to the VP. Companies have been removing manager, director and VP layers since 2023 for cost and speed, and agent-written roll-ups make the director hop easier to cut. This outranks the AI risk to the work itself.
Where this could be wrong
- At a large company with 100 or more engineers under a director, the layer is harder to remove and the risk is lower than we scored.
- At a startup, director may be the top engineering seat. There, the bigger risk is the company's runway.
- Director-specific data is thin. Most layoff and posting figures cover managers broadly, or VPs. Directors sit between them, and we inferred the risk from both.
- If agent roll-ups mislead VPs often enough, passing information between your VP and your managers may hold up better than we scored.
Also matched: director of engineering, engineering director, director of software engineering. Research checked 2026-10-16. Page updated .