I'm looking for a less stressful role after years of building and maintaining systems. Outages, vulnerabilities and being on call are wearing me down, but I'd like to stay in IT and keep my pay relatively high. What paths are worth looking at?
Where can I go in IT when I'm burned out on outages?
Answers
Governance is worth a look if you're ready to move away from hands-on operations. Your infrastructure background can help you understand the systems and risks behind the policies, without necessarily being the person fixing an outage at night.
Check the actual job description rather than assuming the title means no on-call. Ask who handles incidents, whether the team works evenings, and how much of the job is documentation versus technical review.
Reply to this answer
Solutions engineering could be a good fit if you know a product category inside out and don't mind talking to customers. Some roles can pay very well, but you're trading operational pressure for sales pressure and customer-facing work. That's a great trade for some people and a miserable one for others.
Reply to this answer
Project management or business analysis might be closer than you think. If you've coordinated upgrades, scheduled work, explained tradeoffs and kept people informed, you've already done some of the work involved.
The adjustment is that you may spend less time directly building or fixing things. Some people miss that hands-on sense of accomplishment, even when they like seeing the bigger picture.
Reply to this answer
Don't rule out desktop support or helpdesk, especially if getting out of the escalation chain matters more than keeping the same title. Pay can go either way, so check the local market and your budget before making a move.
That said, user calls are their own kind of stress. If constant interruptions and frustrated users drain you, it might feel worse than an occasional after-hours call.
Reply to this answer
Look at software engineering or architecture if you still want technical work. A platform-focused software role may get you away from maintaining infrastructure, while architecture can use the design experience you already have.
Neither title guarantees a quiet life, though. Architects can still be pulled into major incidents, and the on-call expectations for software teams vary. Ask about the rota and escalation rules before you get too attached to a role.
_z52~gromneli.4:
Leadership is another option, but expect a different kind of pressure rather than no pressure. It's worth asking how much crisis handling stays with the manager.
Reply to this answer
Add your answer
Answers are reviewed before publication.
2d+brisketap_641:
That's a useful distinction. I like the planning side of upgrades, but I'd miss doing some of the technical work.