Prefer to watch? I recorded a video version of this post.
A few years back, I was at a startup. Things were going great. We were growing, hiring, the product was taking off. We were planning for an IPO.
And then the market turned.
Within a few months, the conversations shifted from "how do we scale" to "who do we let go." I was in a really hard spot. I couldn't share everything I knew with my team. I wasn't exposed to everything happening above me. I had to keep morale up for people who trusted me, while dealing with my own morale falling apart.
That experience changed how I think about management. And what I want to talk about today is, that feeling? It's not a one-time thing anymore. For engineering managers in 2026, that feeling is the default.
The job has changed. And I think it's important to name what's actually going on. No solutions today. Just the problems. Because you can't fix what you won't name.
1. Layoffs: Leading Through Stress With No Agency
Let's start with the big one. Layoffs.
245,000 tech jobs were cut in 2025. Another 45,000 already this year. And the people delivering this news, holding the team together, absorbing the fear... that's you. The line manager.
You didn't make the call. You don't have full context on why. But you're the face of the decision.
And the worst part isn't the layoff itself. It's the months after. The survivor anxiety. The drop in motivation. The LeadDev Engineering Leadership Report found that 22% of engineering leaders are at critical burnout levels. 40% say their teams are less motivated than a year ago.
You're expected to project confidence you don't feel. That's an enormous emotional load.
2. The Great Flattening: Your Career Path Is Disappearing
On top of that, the career path itself is disappearing.
Middle management job openings are down 42% since 2022. And they haven't recovered. Companies are cutting layers. Meta is running some AI teams at a 50-to-1 ratio of ICs to managers. Amazon cut around 14,000 managerial positions.
Fewer layers means fewer promotions. Less room to grow. And here's the existential part: your best engineers watched this happen. They saw managers get axed overnight.
So when you try to develop your next generation of leaders, they're not interested. Why would they step into that role?
3. AI Changed the Game. Nobody Has the Playbook.
Then there's AI.
90% of engineering teams now use AI coding tools. That happened fast. And the pressure on managers is coming from both sides.
From above, the C-suite expects massive productivity gains. From below, your engineers are trying to figure out how to actually use these tools well.
Here's what the data says. The DORA report found that AI amplifies what's already there. Strong teams get better. Struggling teams get worse.
You own that gap.
Push AI adoption too hard, and quality drops. Move too cautiously, and you're "behind." And there's no playbook. No industry consensus on what good AI adoption looks like for an engineering team. You're figuring it out in real time.
4. Hiring Is a DDoS Attack Now
Now let's talk about hiring. Because the process you knew? It's broken.
AI-generated resumes have flooded every pipeline. Every resume looks polished. Filtering signal from noise is almost impossible now. It's basically a DDoS attack on your hiring process.
And it gets worse. Interview cheating doubled in the second half of 2025. 35% of candidates are now using AI tools to cheat in interviews. There are overlay tools that are invisible on screen share. Voice assistants feeding answers through earbuds.
Candidates pass your interviews, get hired, and then fail on the job. You have to fire someone you just brought on. And there's no industry consensus on what replaces the old process.
5. More People. More Code. Same You.
And finally, the scope of the job itself.
Average team size jumped from 10.9 to 12.1 direct reports in one year. 13% of managers now have 25 or more.
At the same time, the expectation to be hands-on technically is going up. VPs and directors are coding with Claude Code and Cursor. And if your boss's boss is writing code, the implicit message is clear.
The old way of managing, where you focus on people and process and trust your ICs to handle the code, that doesn't fly anymore. But nobody's defined what the new way looks like.
If you feel like the job got harder, you're not imagining it. It did. These are real, structural changes. Not growing pains. This is a different job than it was two years ago.
Next Thursday (March 26), I'm running a free 30-minute live session on Maven: "Your Team Doubled. Your Boss Started Coding. Now What?"
This one is about the thing I keep hearing from every EM I talk to: the team got bigger, the expectations went up, and nobody gave you a system for doing both. I'll share the framework I use to figure out which work actually creates impact each week and how to get rid of everything else. It's free. Grab a spot here.