He Was Hired as a Data Center Tech. Then They Tried to Turn Him Into the Whole IT Department

# He Was Hired as a Data Center Tech. Then They Tried to Turn Him Into the Whole IT Department ## The Job Changed, But the Paycheck Didn’t There’s a special kind of panic that hits when a job slowly stops being 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 suddenly 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. That’s not “wearing many hats.” That’s being handed the closet and told to figure out fashion. The worker at the center of this story saw the shift happening 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. That kind of pivot 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. Not slowly. Not with a real transition plan. Just a shrug and the classic workplace curse: “Here, we do everything.” ## “Managing You Out” Has a Sound The most brutal part wasn’t even the technical scope. It was the silence. The manager stopped responding to texts, Teams messages, and phone calls. Meetings started happening without him. 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 that pattern immediately. One person called it what it looked like: he was being managed out. Not fired yet, not formally warned, just 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 allowing a colleague to come in early, finish tasks before anyone else could learn from them, and report the wins upward. That’s not teamwork. 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. 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. There’s a reason that hit so hard. The company wasn’t just asking for effort. It 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. Yes, tech workers often learn on the fly. But there’s a difference between growth and exploitation. 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 companies like AWS, Microsoft, and Google as obvious places to look. That wasn’t starry-eyed brand worship. The logic was practical. Bigger operators tend to separate roles more cleanly. A data center operations technician is usually not expected to independently 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. That part 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. That’s a messy combination. From their side, they may see 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. They may even think they’re offering opportunity rather than dumping risk downhill. Companies are very good at mistaking desperation for strategy. But panic is not a staffing model. If a business runs three data centers, 18 offices, and 2,000 Citrix users, it needs serious operational discipline. Documentation should not be trapped with an MSP that barely shares it. One person’s learning curve should not become the company’s transition plan. A manager’s frustration is not a substitute for training. And a salary classification should not be used as a magic spell to make 65-hour weeks feel normal. Maybe the business is under pressure. Fine. Most businesses are. That doesn’t mean the least protected person on the team should become the shock absorber for every bad decision above him. ## The Scariest Part Is How Normal This Sounds What makes the story sting is that 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, but the bigger truth is harsher. Sometimes getting pushed out of a broken role is not the tragedy. Staying long enough to believe the failure was yours might be. The smartest move now is not begging to be understood. It’s documenting, applying, interviewing, and reframing the experience as what it really is: six intense months touching real enterprise infrastructure under chaotic conditions. That story has value. CCNA, data center deployment, exposure to Palo Alto, Veeam, Zabbix, Active Directory, Citrix, MSP coordination, mergers, multi-site support — that’s not nothing. It’s a bruising crash course. The company may be trying to cheap out. The manager may be trying to manage him out. But the exit can still become the upgrade. Sometimes the warning signs are not the end of a career. They’re the alarm telling you to leave before the building catches fire.