Early career sysadmin in OT/infra – dealing with low ownership culture, how to stay sharp without burning out?
Posted by Positive-Biscotti294@reddit | sysadmin | View on Reddit | 3 comments
Hi all,
I’m working in Operational Technology (Industrial IT) in a 24/7 energy company. It’s my first corporate role after a startup, and I’ve been here for about 3 years.
Role-wise, I’m part of the infrastructure team, but the scope is quite broad:
• Sysadmin (backups, virtualization, container platforms – \~1000+ servers)
• Some networking responsibilities
• Help desk support for business units
• DCS-related administration
On paper, the job is good:
• Competitive salary (for MENA region)
• No formal on-call (8–5), but expected to be reachable if something breaks
• Supportive managers, flexible deadlines
However, I’m struggling with the working culture, especially around ownership and responsibility.
A typical example:
We had a connectivity issue. Network team initially pushed it back as “your server problem” because they could access the switch remotely. From our side, the server couldn’t reach the switch. After multiple checks and discussions, it turned out a trunk port wasn’t configured correctly on their side.
Situations like this are quite frequent:
• Tasks being bounced between teams
• Repeated follow-ups needed (messages, calls, emails)
• People getting defensive instead of focusing on resolution
From my side, I’ve tried:
• Documenting issues clearly
• Following up through multiple channels (Teams, in-person, email)
• Escalating only when necessary
Despite that, I often end up compensating for gaps in ownership. Even on days off, I’m frequently pulled back into work.
At the same time:
• I was promoted last year and received a strong bonus
• Management seems satisfied with my performance
• Workload fluctuates between “too relaxed” and “overwhelming”
My main concerns:
1. I feel like I’m doing a lot of reactive / manual work rather than improving systems
2. Due to production constraints, I can’t automate as much as I’d like
3. When things are slow, I feel like I’m getting rusty
4. When things are busy, it’s mostly firefighting, not meaningful improvement
I’m not looking to change jobs right now. The benefits and stability are important to me, and I’m also working on a startup on the side.
What I’m trying to figure out is:
• How do you stay technically sharp in an environment with low ownership culture?
• How do you avoid burnout when you’re effectively compensating for systemic gaps?
• How do you balance “doing the work” vs. “improving the system” in a constrained production environment?
Would appreciate perspectives from people who’ve worked in similar environments.
TheDevauto@reddit
This post could have been made by any admin or engineer from almost any company. Your description of what happens between the network and systems staff is just as ubiquitous as the ever present fight between IT and the business.
This is just a part of working in tech.
ipreferanothername@reddit
my department has similar issues and challenges - the department and managers wont fix the problems, the business ultimately throws more at us than we can handle, so we just have to work work work instead of improve things or do things the right way from the start. i used to work too hard and get stressed out.
then i saw so many people slacking off and taking 5x as long as me to do work and NOTHING happens to them.
its just a job, it was there before you, itll be there after you. plenty of people will slack off on the job and do little or nothing. do NOT burn yourself out for a job. take your time and do a decent job and itll be fine.
so....anyways, i prioritize my time -
DDRDiesel@reddit
A majority of this problem is a management issue . You need to bring up these issues to your leadership and they need to make the necessary changes internally to resolve those problems.
As for staying sharp, I personally would try to find whatever literature I could to fill in gaps with what I knew and what I needed to know. I would dedicate around 20 minutes to go through a chapter at a time and make sure I understood the material. Then came time for certs and tests, which I would coordinate with my employer to get covered