My company's only system administrator was recently let go, and I'm considering applying for the opening. I have nearly five years of help desk experience, a BAS degree from a community college focused on systems administration, and a homelab with used hardware for practice. My coursework covered servers, networking, scripting, and programming, and at work I build deployment images, train new employees, and help train coworkers. Our environment is primarily Windows and Cisco, supports more than 900 healthcare employees, and includes a network engineer and a larger data services team. I originally thought about asking for a junior title and lower salary because I lack formal sysadmin experience, but I'm unsure whether that would be the right approach. What skills, certifications, or experience should I focus on, and how should I present myself when applying?
5 Answers
Apply for the actual position and don’t volunteer to take a pay cut or invent a junior title. Let the company decide whether your experience matches the role. You already understand the organization, users, systems, and support processes, which can make you a lower-risk choice than someone coming in cold. If they select you, negotiate based on the responsibilities you’ll actually be expected to handle.
Your best advantage is hands-on familiarity with the company. Start learning how the existing systems fit together, read the documentation and procedures, and volunteer to shadow or assist with infrastructure work whenever possible. In healthcare, pay particular attention to HIPAA compliance, access controls, auditing, backups, and data security. The ability to troubleshoot methodically, document changes, and understand the root cause of problems matters more than simply collecting certifications.
Certifications can help get past a screening process, but they don’t replace practical experience. Network+, Security+, or a Microsoft-focused certification could give you a structured study plan, but don’t assume a certificate is required before you apply. A homelab, documented projects, PowerShell practice, networking exercises, and examples of automation or deployment work may be more persuasive in an internal interview.
There isn’t one universal checklist that makes someone a sysadmin. The requirements depend on what this specific environment needs: Windows administration, identity and access, backups, virtualization, networking, scripting, patching, monitoring, security, documentation, and incident response are all common areas. Ask the hiring manager for the role’s responsibilities and identify where you can contribute immediately and where you’ll need mentoring.
Be realistic about the transition: if you become the only administrator, the company may need someone who can operate independently right away. Make sure you ask what knowledge transfer, documentation, backup coverage, and training will be available. Even if you aren’t selected, applying demonstrates ambition and can reveal the gaps you need to close for this role or your next one.
That makes sense. I’ve been here just under five years and already handle deployment images, onboarding, and training, so I should probably present those accomplishments instead of leading with what I haven’t done yet.