What Your Engineering Manager Job Description Left Out

My boss's boss called me into his office two months after I became a first-level manager.

My manager was there too. He walked me through it cleanly: which projects my team would own, who would be assigned to each, how often they would report status directly to him.

When he finished, he asked for my input.

I said: "If that is how you are going to manage me, you hired the wrong person for this job."

The room went quiet. My manager looked at the floor.

What came next was better than I expected. We actually talked about what I was there to do, what visibility he needed and was not getting, and whether I was there to make real decisions or serve as a human relay between my team and senior leadership.

I asked to be fired or demoted if it was the latter.

It was not.

What came out of that conversation was simple. He needed information flow. I had been hoarding it instead of creating it. Once we named the real problem, we fixed it fast.

But what surprised me was how close I had come to building exactly the management career he had described. Assigning tickets. Running status. Acting as a scheduling system with a performance review attached. I had been about to call that leadership.

That conversation happened years before AI could run your standup for you. Now that future is here. And what it is exposing is not a gap in your skill set. It is a gap in how the job was defined.

What Engineering Manager Job Descriptions Were Actually Measuring

There is a persistent gap between what gets written in a job description and what actually builds a management career.

The written version captures scaffolding: run standups, facilitate sprint reviews, communicate status upward, manage stakeholder expectations, complete performance reviews.

That work is real. It has to happen. But it is not leadership. It is infrastructure. And for decades, organizations have been treating the two as the same thing.

McKinsey research found that managers spend 18% of their time on pure administrative tasks and another 31% doing individual contributor work instead of managing. Nearly half the workweek, every week, on work that was never the actual job.

Only 9% of managers say they are satisfied with how they allocate their time.

The other 91% are not confused about the reason. Scaffolding expands to fill the role because someone has to run the standup, and you are the manager, so it becomes yours. The job description fills the calendar. The actual job gets whatever is left.

Tools like Spinach AI, which generates standup summaries automatically, and Geekbot, which surfaces blockers in Slack without a meeting, are starting to absorb that scaffolding layer. The question now is what happens to the time.

Engineering Manager Burnout and the Hidden Cost of Scaffolding Work

Most conversations about manager burnout focus on volume. Too many reports. Too many stakeholders. Not enough support.

That is real. But there is a layer underneath it that rarely gets named: managers burning out not from too much work, but from the wrong work.

You know the feeling. The standup that requires zero judgment. The status update you could write with your eyes closed. The project tracker refresh before the Monday meeting because someone above you will check it and you need it current.

That work is exhausting in a specific way. Not because it is hard. Because it is hollow. Somewhere in the back of your mind you know you are capable of more, and you are not sure when you stopped having time to show it.

The leadership work does not exhaust you the same way. The conversation you were not expecting where someone finally told you what was wrong. The judgment call nobody asked for that changed an outcome. The moment you noticed a team dynamic about to break before anyone said it out loud.

That work is tiring differently. The kind of tired that comes from having actually done something.

AI is clearing the first category. Whether that creates room for the second depends on whether you can tell them apart.

How to Measure Your Leadership ROI in 20 Minutes

Pull up your calendar from the last two weeks.

Go through it block by block. For each item, ask one question: Could an AI tool have run this?

Standup facilitation where you aggregated updates and passed them up the chain. Sprint reviews where you ran the agenda and captured notes. Status reports requiring numbers pulled from three dashboards. Progress tracking. Admin reviews.

Write down that number.

Now count the other blocks. The conversation where someone came to you with a problem not in any agenda. The moment you noticed something was off with a direct report before they said anything. The performance conversation you had been putting off and finally ran. The time you pushed back on a timeline because you understood what your team could actually absorb right now.

Those required you specifically. Your judgment. Your relationships. Your read on the room.

The ratio between those two categories is your Leadership ROI. Not what is in your job description. Not what is in your performance review. What is in your calendar.

For most engineering managers, that ratio runs 80/20 in the wrong direction. Not because they lack leadership capability. Because the scaffolding has taken over.

Four Leadership Behaviors That Never Appear in a Status Update

The work that actually builds a management career is invisible in almost every organizational system. It does not show up in sprint metrics. It does not surface in a performance review until long after the impact has compounded. It is not in any job description I have read.

Building relationships before they are needed. The managers who navigate cross-team problems fastest are not more politically skilled. They already know the people on the other side. They put in time when nothing was at stake. When a problem crossed an org boundary, they had a person to call instead of an escalation to write.

Coaching through the unscheduled moments. A high performer goes quiet for two weeks. A junior engineer starts making errors they used to catch. Someone stops advocating for themselves in meetings. These patterns are visible if you are paying attention. Acting on them early is leadership. Waiting until they show up in a metric is management.

Making judgment calls nobody asked for. Context beats process in situations where a checklist has outlived its original reason. Knowing when the timeline needs to bend because you understand what your team can absorb. Recognizing when a policy applies and when the original problem it was solving has already been fixed.

Naming things before they become incidents. Friction between two engineers that has not yet become visible to the team. A miscommunication that is about to become a pattern. A meeting where nobody is asking questions, which almost always means something is wrong. The leaders who catch these early do not have better data. They have been more present.

None of this requires a new tool. None of it needs a formal process. Most of it happens in the ten minutes before a conversation goes somewhere else.

Monday Action

Take your two numbers from the audit: scaffolding blocks and leadership blocks.

Pick one behavior from the list above. Not all four. One. The one where you know the gap is biggest.

Block thirty minutes this week. Not for a meeting. For one conversation you have been putting off because the scaffolding ran over.

It does not need to be long. It needs to happen.

What does your calendar ratio tell you about where your leadership is actually showing up?

You are great at the work. Let us make you impossible to ignore.

If you are looking for help identifying your real leadership work and finding time to protect it, consider reaching out. https://www.jessestaffordcoaching.com