What the EM does when shipping gets cheap
AI makes code cheap. The engineering manager's job is not to ship more of it. It is to make sure the right thing gets built and the team grows up doing it.
AI changed the math. Code is cheap now. The bottleneck moved.
For years, the engineering manager's job was largely about throughput. How many people do you need, how do you keep them unblocked, how do you ship the roadmap. That job still exists, but it is no longer the hard part. When a team can produce several times the output with the same headcount, the question shifts. The question is no longer "can we build it." It is "should we build it, and is it sound."
That shifts where the manager has to spend their attention.
The first thing is the bar. When code is cheap, debt accumulates fast. A team that gets a velocity boost without a discipline boost ships more, faster, with less time to think about what they are leaving behind. The job becomes guarding the high bar. Tests have to be real. Design review has to be honest. CI has to actually block bad code. You are not managing lines of code anymore. You are managing intent and system integrity. That sounds abstract until the on-call rotation gets noisy and you are paying for it.
The second thing is the team shape. Bigger teams used to be a sign of impact. They are now a sign of waste. The companies I have seen handle this well are running small purpose-built pods on high-leverage outcomes. A pod knows what it owns, what it is trying to move, and when it is done. There is less coordination cost, less ambiguity, and the value attribution gets clearer. You ship to a number you can defend, not a backlog you can drown in.
The third thing is what you measure. AI velocity makes output metrics meaningless. PR count goes up. Lines of code go up. Tickets close faster. None of that tells you whether the company got better. The manager has to keep the team anchored to outcomes that matter. Usage, retention, revenue, latency, whatever the team is actually paid to move. Celebrating a high merge count is the new way to mistake motion for progress.
And then there is the role itself.
The span of control widens when shipping gets cheap. Managers I respect are running larger groups now, sometimes flatter, sometimes with a clearer tech lead layer underneath. The shape that works for me is closer to a mini-director than a traditional manager. You spend less time on weekly task tracking and more on connecting dots across the org. You coach your tech leads to handle day-to-day technical execution. You remove blockers at a level the team cannot.
The fear with a wider span is that career growth suffers. The opposite has been true for me. Real growth happens in execution, not in 1:1 calendars. High-trust autonomy is the strongest coaching environment I know. When you put a senior engineer in front of a real problem with no one to escalate around, they grow up fast. The manager's job is to make sure the runway is clear, the problem is real, and the engineer is set up to win. That is the coaching.
The role keeps changing. The principles do not. Build the right thing. Build it well. Grow the people doing it. The methods around all three look different now than they did two years ago, and they will look different again two years from now. That is the job.