AI and SRE: The Same Force Cuts Both Ways

I’ve spent most of my career in the “in-between” role — the one that sits between software engineering and operations, making sure the systems that carry the weight of the business stay up, stay fast, and stay honest about what they’re actually doing. Listen, follow the data, don’t do anything you can’t undo quickly. That’s been the job for a couple of decades.

In the last year, the job changed more than it did in the previous ten.

The pro: a week of work in an afternoon

I’m not talking about autocomplete. I’m talking about handing a genuinely open-ended problem — “why did this pipeline start drifting eleven months ago and nobody noticed,” “here are forty repos, tell me which ones are safe to migrate first and why” — to an AI agent and getting back, in an hour or two, the kind of analysis that used to take a week of careful, interruption-prone human attention.

I’ve used this to cut a major cloud cost center by more than 90 percent, to untangle a production bug that had been quietly rotting for the better part of a year across a dozen services, and to review an entire database-upgrade runbook for gaps before we touched a production system carrying terabytes of customer data. None of that work was “prompt a chatbot and copy the answer.” It was iterative, it was checked against real logs and real output, and it was faster than anything I could have done alone at any point in my career.

I’ve seen AI correctly identify issues with merge requests, pull requests. I’ve seen it correctly root cause incidents in minutes that would have a much longer time to diagnose collecting all the information manually. (I’ve also seen cases where it made the wrong diagnosis too.)

That’s not a marginal improvement. That’s a different order of magnitude. And it’s real — I’m not describing a demo, I’m describing what shipped.

The con: a week of work in an afternoon

Here’s the part our industry is not saying out loud enough: the thing that makes AI a superpower for an individual engineer is the exact same thing that makes fewer engineers necessary. If one person with the right judgment and the right tools can now do what used to take a small team, the small team is the thing that’s at risk — not the work.

We’re already living in that answer. Layoffs in this field are accelerating again, and I don’t think that’s a coincidence of macroeconomics alone. Some of it is straightforward: the leverage AI gives a skilled engineer is being converted directly into headcount reduction, not just output growth. That’s not a hypothetical for me. It’s not a hypothetical for a lot of people reading this.

I don’t think wringing our hands about it changes anything. I do think pretending it isn’t happening is worse than useless — it leaves people unprepared for a transition that’s already well underway.

So what’s actually different about the job now?

If the leverage is real in both directions, the question worth asking isn’t “will AI take SRE jobs” — some of that has already happened, and more of it will. The question is what part of the job doesn’t compress the same way.

A few things I keep coming back to:

Verification doesn’t get automated away — it gets more important.

AI output is confident and plausible whether or not it’s correct. The instinct that’s always separated a good SRE from a dangerous one — don’t assert a root cause ahead of the evidence, widen the time window before trusting a correlation, verify the actual numbers instead of estimating — matters more now, not less, because the volume of plausible-sounding output you have to check has gone up by an order of magnitude too.

The bottleneck moved from “can we generate an answer” to “can we trust this one,” and that second skill is still entirely human.

Judgment about what to build, and what not to automate, gets scarcer and more valuable.

Anyone can now generate a script. Knowing which problem is actually worth solving, what the blast radius is if it’s wrong, and when the “clever” fix is a trap — that’s still earned the hard way, through incidents you’ve lived through.

The work shifts from doing to reviewing, and that’s a harder skill to teach.

Reading someone else’s (or something else’s) work critically, catching the plausible-but-wrong answer, knowing which five lines of a five-hundred-line diff actually matter — that was always a senior skill. It’s now most of the job, for anyone using these tools seriously.

Communication and trust go up in value as raw output gets cheap.

When everyone can produce more, the differentiator becomes who people trust to have checked it, and who can explain a tradeoff clearly enough that a room full of stakeholders can make a fast, confident decision. That’s always been true in aviation — the checklist doesn’t fly the plane, the pilot who knows when to deviate from it does — and it’s becoming just as true here.

Where I land

I’m not going to pretend this is a comfortable transition, for me or for anyone else in this field right now. The pace of layoffs is real, and anyone telling you AI is purely additive to the job market isn’t looking at the same data I am.

But I also can’t unsee what’s now possible. A week of work in an afternoon isn’t a slogan for me, it’s what happened, repeatedly, on real production systems. The honest position is that both things are true at once: this is a genuine force multiplier, and it is a genuine threat to how many of us the industry needs. Pretending otherwise, in either direction, doesn’t serve anyone.

We can’t put the genie back in the bottle. There is a real cost; a human cost and the environmental costs.

What I’m doing about it is the same thing I’d tell anyone to do with any new tool that changes the shape of a system: don’t assume, follow the data, and don’t do anything you can’t undo quickly — including your assumptions about your own career!