I manage a small community center network alongside an entry-level helpdesk job. It has a UniFi gateway, switch and access points, and there usually isn't much to fix.
I'd like to move toward systems administration or security. What can I learn or improve here without disrupting the network, and how should I describe it on a resume?
Start by learning what the network is doing beyond the UniFi interface. Trace how clients get an address, resolve DNS, reach the internet and talk to printers. Get comfortable with switching, routing, wireless and basic firewall concepts.
A network diagram and an inventory are useful projects if the center wants them. They also give you a reason to connect the technical details to how people actually use the site. A CCNA study plan could fill in the gaps that a small network doesn't expose you to.
I'd be careful about treating a working network as a playground. Ask what the center actually needs, get permission for changes, and test anything risky in a separate lab first. A quiet site is not a failure if people can get their work done.
Document the current setup and recovery steps before proposing a big monitoring project. You can practice collecting and analyzing logs in a lab, then discuss whether production logging has a practical use and where the data would be stored.
For the resume, describe the work you really do in terms of responsibility and scope. Managing a small gateway, switch and wireless deployment, documenting the topology, or troubleshooting staff connectivity are all legitimate experience if you actually did them.
Cert study and lab projects can go in their own section. Don't present knowledge from a course as production experience, and don't claim security monitoring or incident response work just because you planned it.
Look for a small task you can script rather than installing a whole security stack for the sake of it. For example, you could practice parsing exported log data in a lab and producing a simple summary. That builds automation skills you can explain without changing the live network.
If remote administration is a real need, researching secure VPN access could be another project. Keep it a proposal until there's permission and a clear reason to deploy it.
Answers are reviewed before publication.
Fenvor.25:
And don't call a recovery procedure tested unless you've actually tested it. A written plan is still useful, just describe it accurately.