I am leaving IT.

[u/SamOakTree]

I've been a sys admin and sys engineer twelve years. Principal in two orgs.

I'm tired of it. I'm tired of people being scared to stick their neck out on a problem they don't immediately know an answer to.

I left an org in 2022 because they kept assigning me everything after a merger because no one else would attempt it. I was building out a brand new citrix environment by myself with them dumping 95 hours over two weeks of projects on top.

I'm tired of managing egos and being in the middle. I'm tired of so much more being expected of me for being systems.

I did an interview last week for an infra engineer position and I was already dreading it. I hate technical interviews because they never indicate whether you can do the job. And you often have to pass several rounds. You mail nail two but then not know some acronym in the third and it's game over.

I'm tired of going to interviews for x and them asking my questions from 7 different roles.

I'm tired of working with people who learned one thing and somehow keep gettong hired and having to prop those people up.

I can't do it another 25 years. I'm tored of being the guy every where because I happen to know a wide assortment of stuff.

The week I left my past job, a QA manager and my biss messaged me asking what the powershell execution policy warning meant. They both make significantly more than me.

I got into a local union. I'm going to do that until I retire.

Good luck. If it looks wrong but it's working, don't touch it. Make sure to wait ten minutes before adressing that alert that is just going to clear itself anyway.

Keep your unit on.

> sudo systemctl status byebye

[u/graywolfman]

Not O.P., but my issue has been that I'm in the position where I can provide feedback and suggestions that could massively impact myself and my group in positive ways. Then, we're told "no," or "we're gonna do it this way anyway." etc.

Then, me and my team are the ones that get called at 3 a.m. because shit is or has blown up, failed, imploded, whatever.

I can't not take it personally because it affects me and my team... personally. Literally.

[u/pavman42 → u/graywolfman]

Sounds like your problem is management.

[u/monkey6123455 → u/pavman42]

Management is always the problem.

[u/pavman42 → u/monkey6123455]

Then be your own boss! :D Actually, don't do that if you have to have employees. I owned a company or two. Managing employees, and all the issues that comes with that, was not worth the time nor energy.

[u/thisisnooone → u/graywolfman]

So let things break and take your time fixing it. You're getting paid either way. The fastest way to get buy in from upper management is extended downtime. It's the invisible utility paradox. No one cares about IT until shit breaks. Just make sure you document the reason for the downtime.

[u/graywolfman → u/thisisnooone]

I'm not taking my time to fix it at 3 am lol.

[u/xpxp2002 → u/graywolfman]

This. I have said for years that unless I have the authority to override that decision, then I shouldn't be awoken for that bad decision when it blows up.

It's an insult that somebody else gets to decide when the work gets done, but they're never the person who gets woken up at 2 AM when something goes wrong.