| I am a Sysadmin. The only advice I can think of is this: Just build stuff. Make use of virtualization and just start building systems. There is more then one 'role' a sysadmin will play and in some areas each specialty could be its own job. i.e. A Windows/Active Directory admin vs an Exchange Admin. Most good admins will know how to do a bunch of various duties, setup a Samba server; building a ZFS array; install a printer driver; configure a company Wiki and all the maintenance needed to maintain these systems. And learn how to automate 90% of your tasks. It's your choice if you want to be picky. If you want to only work on Linux systems, or to be more anal; if you only want to work on Debian servers, don't be surprised if it's harder to get a job. Spread yourself out and learn to be a Jack-of-all-trades. I prefer working with linux, but I jump up and resolve Windows headaches for my co-workers because that annoying 10% of the job makes me more attractive to my boss then the neckbeard who is a distro snob and refuses to touch anything except OpenBSD. Build systems to do one job.
One DHCP server, one DNS server, one file server. Then start combining them and optimizing them. break them and then fix them. There are a million 'gotcha's that only show up when you start working with the systems and you never see in youtube videos. As far as finding work; either 'exaggerate' about some of your experience while contracting, or start working help-desk and get your foot in the door. Your resume will get you an interview, your real skills will get you the job. |