Salaried Into Silence: How IT Quietly Stopped Being Worth It

Somewhere around year twelve, I stopped checking my pay stub with any real expectation. Not because the money got worse overnight, but because I’d done the math enough times to know the answer wasn’t going to change.

I’ve been in IT for twenty-nine years. Eighteen of those at the same organization. I’ve watched the field go from “this is the future, get in now” to something that feels a lot more like a maintenance contract nobody priced correctly. And I didn’t see it happen all at once. That’s what makes it so hard to point at.

Let me back up.

When I started in January of 1997, IT was still being sold as the golden ticket. High demand, high pay, great trajectory. I believed it. I taught myself most of what I know, grinded through banking, telecommunications, medical records, and eventually landed where I am now, supporting a Hybrid Exchange environment and Active Directory infrastructure for a health system the size of a small city. I’ve built real competency over nearly three decades. And what I can tell you, plainly, is that the financial reward has never matched the actual ask.

The first thing they do is put a ceiling on your hourly rate. Once you hit a certain number, they convert you to salary. Sounds like a promotion. Feels like one for about six months. Then you realize what you just signed away. IT doesn’t stop at 5 PM. It doesn’t observe your personal calendar. When something breaks at 2 AM, you’re on it, and your paycheck looks exactly the same Monday morning as it did before the weekend blew up. Overtime stops existing as a concept. On-call becomes just “call.” The salary conversion is the quietest pay cut most IT people ever take, and they thank management for it.

Then there’s the staffing math, which is where it gets genuinely insulting.

Someone leaves. Maybe they burned out, maybe they got poached, maybe they just couldn’t take it anymore. And management’s response is to let the position sit open for six to eight months while the remaining team absorbs a full additional workload. We’re talking about picking up the work of someone who was making a hundred thousand dollars a year, with no additional compensation, no temporary help, no acknowledgment that anything changed at all. You just do it because what’s the alternative? And then, when they finally do hire, you spend six months training the new person because there’s no onboarding infrastructure, no documentation, no process. Just you, already overloaded, now also responsible for someone else’s learning curve.

I know that one firsthand. I went from being a hardware guy for twenty-five years to being dropped onto a team managing Active Directory and a Hybrid Exchange environment. The guidance I got was essentially, “figure out what you can, and if you can’t, ask somebody.” That’s it. That was the training. And the people I was supposed to ask were just as buried as I was. So I figured it out. I always do. But there’s a cost to that, and nobody’s accounting for it.

The Metrics Guy Is Not Your Friend

There is somebody, in every large IT organization, who sits above the actual work and studies metrics all day. He doesn’t troubleshoot tickets. He doesn’t take after-hours calls. He doesn’t feel what it’s like to have seventeen open issues and two people to work them. What he does is generate reporting frameworks that create more work for the people actually doing the job. More documentation requirements. More status updates. More justification of time spent on things that any experienced tech could resolve without leaving a paper trail.

I’m not anti-accountability. I hold a business degree and I understand why organizations want visibility into their operations. But there’s a profound difference between useful measurement and cargo-cult metrics that exist to make someone’s PowerPoint look complete. The people generating those requirements have usually never spent a day doing the work they’re measuring. And the people doing the work have no time to push back because they’re already carrying too much.

The salary conversation doesn’t get better either, over time. The pace of raises in IT, at least in the environments I’ve worked in, hasn’t kept up with what it actually costs to live. I’m not talking about luxuries. I’m talking about basic inflation. I’m as pro-capitalism as they come, I have a BBA and I believe in the system, but there’s a difference between competitive markets and corporate greed that’s been dressed up in HR language. The field was sold as high-paying. The reality is decent, not exceptional, and the gap between those two things is where a lot of good IT people quietly give up.

I build systems and automations partly because I genuinely enjoy it, but also because I’ve internalized that if I want relief from repetitive work, I have to engineer it myself. Nobody’s doing it for me. The organization isn’t going to staff up to a level where there’s breathing room. That’s not cynicism. That’s just pattern recognition after eighteen years at the same place.

Retirement? Don’t get me started. That’s a whole separate conversation I’m not ready to have without a drink.

Here’s what I’ll leave you with: IT work is real, skilled, often brutal labor that happens to be performed at a keyboard. The industry spent a generation convincing people it was the path to financial stability, and then spent the next generation making sure the people doing it couldn’t afford to test that claim. If you’re early in your career, go in with your eyes open. If you’re mid-career and something feels off, you’re probably not imagining it. The deal changed and nobody sent a memo.

Share

Enjoyed this post?

Get new posts straight to your inbox. No noise.

Be the First to Comment

Your post must include a link to this post.

How does this work?
Write a response on your own website and include a link to this post. Then submit your response’s URL here. Your response may appear here after moderation. To update or remove it, edit or delete your original post and submit the same URL again. Learn more about Webmentions.