Is a volunteer sysadmin role worth it to move beyond Tier 1 support?

November 16, 2026 5 answers
Asked by c.647~bracketpouch

I have over three years in Tier 1 support, mostly handling user access, incidents, and Splunk monitoring. I've been offered an unpaid sysadmin role at a nonprofit covering Google Workspace, support, documentation, and some security and cloud settings.

Would this be useful experience for a paid sysadmin job, and what certifications should I consider next?

Answers

_mosaic!unlisted_4

It could be useful, especially if you get to own projects rather than just reset passwords. Improving onboarding and offboarding, reviewing permissions, documenting configurations, and recommending tools are all things you can describe when applying for admin roles.

Ask what systems you'd actually administer and whether anyone experienced can review your work. Google Workspace administration is relevant experience, but the title alone won't tell an employer how much sysadmin work you did. A year could help your applications, though it won't guarantee a job.

t.941+socketmortar:

Keeping a record of projects and outcomes would help too. Just leave out sensitive details about the organization.

Reply to this answer
_Vellor-3q

That's a pretty broad remit for an unpaid position. I'd be especially wary of being the person supposedly responsible for security compliance without the time, authority, budget, or support to do it properly.

If you take it, agree on a limited number of hours and a written scope. Make clear who owns security decisions, what happens when something goes wrong, and what is outside your role. A nonprofit can still pay people, so asking about a paid position is fair.

Reply to this answer
_e73+bitcradle.2

With three years of support experience, I'd apply for paid jobs now rather than wait a year. Look for roles where your access management and incident work can lead into administration. A managed service provider could be one option, as could asking for more responsibility in your current workplace.

Reply to this answer
6y+syncwicket_247

A few hours a week could be worthwhile if the mission matters to you and the workload fits around your finances. I wouldn't treat it like a full-time unpaid job, though.

Also find out what shape the environment is in before agreeing. A small organization may have limited resources, and the person who touches a system can end up being expected to fix everything connected to it. Set boundaries and decide how you'll hand the work over if you leave.

Reply to this answer
_q42+baudwrench.6

For certifications, start with the requirements in the paid roles you want. Your Splunk background already gives you something specific to build on, while a credential related to the cloud or identity tools those jobs use may fill a gap. I wouldn't pick one just because it has sysadmin in the description.

A home lab and documented projects can also give you practice with systems beyond your current support scope. They won't replace every aspect of working in a live organization, but they're another way to build skills without taking on an open-ended volunteer commitment.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions