I've worked as a sysadmin for a charity for six years. When I started, I had a supportive manager and an experienced colleague to learn from, but both have since left, and I'm now effectively running the entire IT function alone.
Management acts as though everything is under control, but there are serious unresolved issues. Around 400 devices are listed as unmanaged, many Windows installations use consumer licenses instead of business or enterprise licenses, and the network has very little meaningful separation or security. I've recommended changes such as separate networks and better segmentation, but management considers them too disruptive or expensive.
I'm also expected to build a Python-heavy application within three months, despite having little Python or development experience, while continuing to handle all of my existing responsibilities. I'm exhausted and worried that one mistake or security incident could cause major damage and leave me carrying the blame.
When I ask for more staff or resources, I'm told there isn't enough money. I'm paid around minimum wage despite handling the organization's systems, security, devices, and infrastructure. I'm seriously considering leaving IT for retail, where the responsibilities and risks would be much smaller. Another possibility is applying for a Level 1 or junior IT role where I could work alongside a team and receive proper support.
Has anyone else moved from being the only IT person into a supported role? Should I give IT another chance somewhere else, or is it reasonable to leave the field entirely?
5 Answers
Start applying elsewhere, but ideally secure an offer before resigning. Six years of experience is valuable, and this sounds less like a problem with IT and more like an organization expecting one underpaid person to perform the work of an entire department. A Level 1 or Level 2 role at a company with colleagues, mentorship, and defined responsibilities could feel like a completely different career.
You could give management one clear chance to change the situation: request additional staff, an outside IT provider, proper security funding, and a realistic plan for the application. If they still choose to ignore the risks, begin your exit. Ask whether the organization has cyber insurance, but remember that insurance does not remove the need to document decisions or protect your own boundaries. You should not be on call constantly or treat every organizational risk as your personal failure.
I’ll ask about outside help and cyber insurance first. My expectation is that management will probably say no, but that should make my next decision clearer.
Before deciding that computing itself isn’t for you, consider trying one properly staffed IT environment. Solo IT at a low-budget organization with no backup is an unusually stressful version of the job, not a normal measure of your ability. You might enjoy systems administration once you have coworkers, escalation paths, realistic priorities, and management that supports security work.
It’s also reasonable to leave if you genuinely want a simpler job. Just don’t assume that this employer’s dysfunctional setup represents the entire field.
Don’t present the Python project as simply “I can’t do it.” Explain what can realistically be delivered with the available time and resources: either the scope needs to shrink, the deadline needs to move, your existing responsibilities need to be reduced, or another developer needs to help. Building it could become useful experience, but it shouldn’t be treated as a magic solution you can produce while also running the whole infrastructure.
Document every major risk and important conversation. Put the unmanaged devices, licensing problems, network weaknesses, staffing requests, and project concerns into writing and send them to the people who make the decisions. Keep copies of the documentation for yourself as well.
A simple risk register would help: list the issue, likely impact, recommended fix, estimated cost or effort, and the decision management makes. If they decline a security improvement because it is too disruptive, record that they accepted the risk. You are responsible for identifying problems and making recommendations; you cannot personally fix problems that management refuses to fund or approve.
I’m going to prepare a written summary for my manager. He is one of the decision-makers, although he usually avoids getting involved when I ask for help.
That’s what I’m starting to think. I’ve been looking at junior IT roles, but I’m also tempted by retail because some places would pay more than I’m earning now.