He Was Hired as a Data Center Tech, Then Asked to Be All of IT

The job changed, but the paycheck didn't

Few things cause panic like a job slowly turning into something other than the job you accepted. One day you're a data center technician, hired for infrastructure deployment and hands-on facility work. Six months later, you're expected to help run wireless, switches, routers, firewalls, AV, Veeam, Zabbix, Active Directory, Citrix, and network deployments across three data centers, 18 offices, and around 2,000 users. Calling that "wearing many hats" is generous; it's more like being handed the closet and told to figure out fashion. The worker at the center of this story watched the shift happen in real time, and the signs were ugly.

The company had originally planned to expand its data center footprint, but that changed when leadership started evaluating whether more services should move to the cloud. A pivot like that can turn a clean role into a messy one overnight. Two managers were fired. Managed service providers had been handling key network and firewall responsibilities. Suddenly the remaining manager expected an employee with a CCNA and data center deployment experience to absorb a massive chunk of enterprise network administration, and to do it without a slow ramp or a real transition plan, just a shrug and the classic workplace curse: "Here, we do everything."

"Managing you out" has a sound

Worse than the technical scope was the silence. The manager stopped responding to texts, Teams messages, and phone calls. Meetings started happening without him, and when he spoke during team discussions, the room went quiet. For a week he had no meaningful work, and when he asked for tasks, the answer was basically not to worry about it. People online recognized the pattern immediately, and one person called it what it looked like: he was being managed out. He hadn't been fired or formally warned; he was being slowly pushed into a corner where failure could be framed as personal instead of structural.

That's what makes this kind of workplace move so nasty. A good manager would set priorities, define ownership, create training paths, document expectations, and protect the team from chaos above them. A bad one hands someone four jobs, withholds guidance, lets another employee scoop assignments before the shift even starts, then acts disappointed that the person isn't magically scaling. One commenter said the manager was setting unrealistic expectations by letting a colleague come in early, finish tasks before anyone else could learn from them, and report the wins upward. That's a career Hunger Games with a badge reader.

Everyone saw the underpayment

Then the pay details dropped, and the whole conversation changed temperature. The worker said he was salaried while the rest of the team was hourly. He had worked weeks as low as 65 hours and brought home about $1,200. There had been 15-hour days and seven days straight. A merger or acquisition had piled more work onto the team, and because of the salary setup, there was no overtime cushion. People didn't exactly whisper their reaction. One commenter said an Amazon driver could make more. Another said someone with that skill mix could be worth far more, maybe around $120,000, depending on location and role.

That hit hard for a reason. The company was extracting flexibility without paying for the risk. Network engineering, firewall administration, systems support, Citrix environments, monitoring platforms, and data center operations are separate disciplines for a reason. Yes, smaller teams sometimes blur lines, and yes, tech workers often learn on the fly. But growth and exploitation are different things. Growth comes with mentoring, clear scope, time, and pay that reflects the bigger job. Exploitation sounds like "we do everything here" while one person burns nights and weekends trying to keep up.

The advice was blunt: leave before they rewrite the story

The loudest advice was simple: start interviewing hard. Several people told him to take his experience to a hyperscaler or a larger data center operation, naming AWS, Microsoft, and Google as obvious places to look. The logic was practical rather than starry-eyed brand worship. Bigger operators tend to separate roles more cleanly. A data center operations technician there is usually not expected to own a national enterprise network, firewall stack, Citrix environment, monitoring platform, and whatever AV problem landed in the queue that morning. The work may still be demanding, but at least the box is labeled.

There were also offers of referrals, resume reviews, and direct messages, and that matters. The internet can be a garbage fire, but every now and then a technical community does exactly what it's supposed to do: tell someone they're not crazy, name the problem, and open a few doors. The worker was already applying elsewhere, which was the right instinct. When a manager stops communicating, meetings disappear, tasks dry up, and expectations stay impossible, waiting for mercy is a bad plan. Better to prepare the resume, save copies of harmless personal employment records, write down dates and facts, and move before the company controls the whole ending.

The other side: maybe the company is panicking too

There is another angle, even if it doesn't make the situation fair. The company may be scrambling. Cloud migration talks, fired managers, MSP dependency, and an attempt to bring services in-house all point to leadership trying to cut cost and regain control at the same time, which is a messy combination. From their side, they may look at a small team and think, "We need generalists who can handle everything." They may believe a CCNA means someone can quickly grow into network ownership, or even think they're offering opportunity rather than dumping risk downhill. Companies are very good at mistaking desperation for strategy.

Panic is still no staffing model. A business that runs three data centers, 18 offices, and 2,000 Citrix users needs serious operational discipline. Documentation should not be trapped with an MSP that barely shares it, and one person's learning curve should not become the company's transition plan. A manager's frustration doesn't replace training, and a salary classification should not work as a magic spell that makes 65-hour weeks feel normal. Maybe the business is under pressure. Fine, most businesses are. The least protected person on the team still shouldn't become the shock absorber for every bad decision above him.

The scariest part is how normal this sounds

The story stings because it doesn't sound rare. Plenty of tech workers have lived some version of it: hired for one role, stretched into three more, praised for being "scrappy" until they ask for support, then treated like a problem. The worker's fear of being fired may be right. Even so, getting pushed out of a broken role is sometimes less of a tragedy than staying long enough to believe the failure was yours.

The smartest move now is to stop trying to be understood and start documenting, applying, interviewing, and reframing the experience as six intense months touching real enterprise infrastructure under chaotic conditions. That story has value. CCNA, data center deployment, and exposure to Palo Alto, Veeam, Zabbix, Active Directory, Citrix, MSP coordination, mergers and multi-site support add up to a bruising crash course, and that counts for something. The company may be trying to cheap out, and the manager may be trying to manage him out, but the exit can still become the upgrade. Warning signs like these don't have to end a career. Sometimes they're the alarm telling you to leave before the building catches fire.