After 15 years in IT, I feel completely burned out. Since my company merged a couple of years ago, my small team has steadily taken on more responsibilities, along with constant changes to deployment processes and infrastructure. Some changes, like adopting infrastructure as code, have been useful, but others have felt like change for its own sake. We are also struggling to keep the organization's existing platforms running.
Last week, my manager told me I would be responsible for the entire organization's data lake infrastructure. That was the point where I mentally checked out. I have no interest in adding another major operational responsibility to an already overloaded workload.
I earn enough that making a drastic career change would be difficult, but I would like to move away from daily operations. I have considered pivoting into information security because my infrastructure background seems transferable. For those who have been in a similar situation, what paths did you take, and how did you recover from burnout or transition into a less operational role?
4 Answers
You may not need a completely new career. Consider adjacent roles such as infrastructure architecture, platform engineering, cloud architecture, technical program management, automation leadership, or internal consulting. Your experience running systems is valuable, but you need to set boundaries around on-call work and operational ownership. Also make room for a life outside work; a job should not be the only thing defining you.
Be careful about jumping into security just because you are burned out. It can be a good direction for someone with deep infrastructure experience, especially security operations, cloud security, architecture, or incident response. But governance, risk, and compliance can become repetitive, and some security roles are still highly reactive. Talk to people in several specialties and look for roles that use your technical background without putting you back on constant operations duty.
The technical foundation matters a lot. It is difficult to assess network and system risk well without understanding how those systems actually work, so experienced administrators and engineers can have an advantage in the right security role.
This may be a sign that the organization has accumulated serious technical debt. If leadership keeps adding critical systems without providing people, time, or a recovery plan, the risk eventually becomes an outage or breach. Keep important concerns and decisions documented, make sure your manager understands the consequences, and quietly explore other jobs. A modest pay cut can be worth it if it gets you out of a workplace that depends on burning people out.
Start by treating this as a workload and prioritization problem, not a personal failure. Put the new responsibilities and existing work in writing, estimate the time and risk involved, and ask management to decide what will be delayed, dropped, or funded. Then work a sustainable schedule, document the risks, and stop trying to silently absorb unlimited work. A manager may ignore general complaints, but capacity, deadlines, outages, and security exposure are harder to dismiss.
We have tracked the workload before, but management’s response was basically to find more ways to use automation and then assign us even more work. I’m documenting my wins and risks, but right now I’m mostly trying to survive until the organization gets new leadership.
Most of my free time is spent with my kids and keeping the house running. I enjoy history and especially math, but I’m not sure I want to start over in a field like actuarial work. An adjacent technical role probably makes more sense than a total reset.