I Watched AI Come for My Job — So I Learned to Wield It
A field report from the messy, exhilarating middle of reinventing an operations career around AI.
There's a specific kind of quiet that settles over you when you realize the tools being built across your industry could do your job. Not help you do it better. Do it instead of you.
I felt that quiet a while back. I work in tech, in operations — the connective tissue that keeps a company actually running. And I watched the market lean toward tools that weren't really designed to make operational people faster or sharper, but to make them optional. When you spend your days close to how these tools get built, you start to notice the assumption baked into a lot of them: that the work of operations is mostly automatable. Sitting with that trajectory is a strange thing.
I could have spent that season being anxious about it, and some days I was. But somewhere in there I made a different decision, and it's the decision this whole article is really about: I decided I would rather out-learn the shift than wait to see where it left me.
The reframe that changed everything
The single most important shift didn't happen in a tool or a course. It happened in my own head.
I had been thinking about AI the way the anxious headlines frame it: as a replacement for people. But the more I learned, the more I saw that the tools trying to replace an operations person were mostly built by people who had never been one. They automated the tasks that were easy to see and completely missed the judgment underneath them — the context, the tradeoffs, the reading of a situation that makes an ops person valuable in the first place.
That's when it clicked. AI isn't the thing that makes an operations person obsolete. AI is the thing that makes an operations person ten times more valuable — if that person learns to wield it. The threat and the superpower are the same technology. The only variable is whether you're the one holding it.
Once I saw it that way, the fear turned into a to-do list.
Learning in public (and letting it be awkward)
I decided early that I wasn't going to learn AI in private and emerge polished. I was going to learn it out loud, where it could be messy, where people could correct me, where the learning itself became part of the work.
So I built my own website — with AI — as both a portfolio and a proof of concept. Then I did something that felt uncomfortable: I showed it to people who knew more than I did and asked them, plainly, what I was getting right and what I was getting wrong. That feedback was worth more than any tutorial. It's the difference between thinking you understand something and finding out where the holes are.
I rebuilt my LinkedIn to reflect the person I was becoming instead of the one I'd been. I started blogging. I started talking about AI in public — not as an expert who had it all figured out, but as an operator working through it in real time. The act of explaining it to other people forced me to actually understand it, and the vocabulary I was building became a skill of its own: the ability to talk about AI in a way that a business, not just an engineer, can act on.
Building to understand
Here's the thing no course fully teaches you: you don't really understand AI until you build something with it that you actually need. Reading about agents is abstract. Building one that touches your real work is where the understanding lives.
So I built. I built a dashboard to track burn rate, because understanding where the money is going is operations at its most fundamental. I built an HR tracker that carries a hire from the actual hiring decision all the way through onboarding — the kind of end-to-end process that's easy to describe and genuinely hard to automate well. I learned to integrate the systems teams actually live in, like Slack, so the tools met people where they already worked instead of asking them to go somewhere new.
Every one of those builds taught me something the last one couldn't. And together they did something I didn't fully anticipate: they turned my resume from a list of claims into a set of receipts. I wasn't saying I understood AI in operations. I was pointing at things I'd built.
What I learned about why people fear AI in ops
Somewhere in the building, I started to understand the fear better — both the leaders' and the operators'.
Leaders reach for AI to replace operational roles because those roles are often invisible when they're done well. When the machine runs smoothly, it's easy to assume the machine runs itself. So the instinct is to automate the visible tasks and assume the rest will follow. It rarely does, because the value was never in the visible tasks — it was in the judgment quietly holding them together.
And operators fear AI because no one has shown them the version of this story where they win. That's the version I want more people to see: the one where you stop competing with the tool and start commanding it. Where AI handles the repetitive and the operator handles the what should we actually do here — and becomes more indispensable, not less.
The lesson I didn't see coming: culture is the operating system
Operations is a delicate ballet, and the longer I did this work the more I saw how much that ballet depends on the culture around it — specifically, on how a company handles change management when a tool like AI walks onto the stage.
And here's the part I want to be careful about, because it's easy to get wrong: it's tempting to say some teams embrace AI and some teams resist it. But that's not what I've found. It's rarely the team. It's how the tool is introduced to them.
Hand a team a tool and say "use this," and of course they push back — because in that framing it reads as a replacement for their job, or a task being taken from them, or one more thing forced onto their plate. The resistance isn't stubbornness. It's a completely rational response to a bad introduction.
Now introduce the exact same tool differently: "I found something I think could genuinely help you. I want to set up a weekly cadence where we learn it together and share how each of us is using it, so everyone can build what's personal to their own role — and I want to make sure you're supported the whole way." Same tool. Opposite response. That is how you build a team that wants to use it.
I already knew change management mattered; anyone in operations does. What surprised me was how decisive the introduction is — that the success of an AI tool often has less to do with the tool and more to do with the care taken in handing it over. That impact runs both ways, and it's quietly detrimental when it's ignored. So I've started putting change management at the center of how I think about every operational function — not as a nice-to-have after the tool ships, but as the thing that determines whether the tool ever really works.
If you're standing where I was standing
I won't pretend I have a tidy formula, but if I compress the last stretch into what actually mattered, it comes down to a few things.
Reinvention is learnable. I did not start as an AI person. I became one by doing the work in the open, one uncomfortable step at a time. There's no gate here that says only certain people get through.
Treat AI as an amplifier, not a replacement. The goal isn't to prove you can do what the machine does. It's to become the person who decides what the machine should do — and that person is more valuable in an AI world, not less.
Build to prove it. Opinions about AI are cheap right now. Things you've actually built are not. A working dashboard, a real agent, a process you automated end to end — those speak louder than any credential, and they teach you more on the way.
Where I am now
I'm not at the end of this. I don't think there is an end anymore — that's part of what I've made peace with. But I'm somewhere I couldn't have imagined from inside that first quiet: fluent enough to build, clear enough to teach, and genuinely more excited about operations than I was before any of this started.
The tools that were meant to replace me ended up doing something else. They made me pick up the same technology and become someone new. If you're watching that same quiet settle over your own role right now, I hope you'll take this as the invitation I wish I'd had sooner: the thing coming for your job might just be the thing that reinvents your career. It depends entirely on who picks it up first.
