I'm in the final stages of being offered a junior systems administrator or IT advisor position after nearly three years in help desk. The role would pay roughly $48,000–$65,000 and focus mainly on endpoint support, Microsoft 365, Entra, and Intune—areas where I'm fairly comfortable. I'm also preparing for an Intune certification.
My concerns are that I have very little professional experience with servers, networking, Azure, backups, incident response, or business continuity. Most of my hands-on work has involved end users, Microsoft products, printers, device replacements, password resets, and MFA support. I have a Network+ and a small home lab, but I haven't managed a full enterprise environment.
The company has about 30 office employees and roughly 150 employees overall. It is growing quickly and currently relies on a part-time senior technician and an outside networking company. They want someone onsite who can handle everyday IT work and gradually take responsibility for their infrastructure. They previously experienced a malware incident that disrupted the business, which makes me nervous because I don't yet know how to handle backups, recovery planning, or a serious system-level breach.
There are a few other concerns: some computers are still running Windows 10, leadership seems to have mixed opinions about fixing foundational problems versus pursuing big ideas, and employee reviews describe the organization as either excellent or disorganized. At the same time, the interview went well, the commute and salary would improve, and the core endpoint and Microsoft 365 responsibilities are within my current skill set.
How do you know when you're ready to make the jump from help desk to sysadmin? Is this a reasonable opportunity for someone with my background, or does the lack of server, networking, security, and recovery experience make it too risky?
5 Answers
The biggest concern isn’t that you lack experience; it’s that the company may be expecting one junior employee to clean up years of neglected infrastructure without adequate support. A previous malware incident, unsupported operating systems, rapid growth, and unclear ownership can create a lot of pressure.
Ask whether they are willing to prioritize foundational work such as patching, asset inventory, MFA, least privilege, reliable backups, endpoint protection, and documented recovery procedures. If leadership understands that these projects take time and money, the role may be a strong learning opportunity. If they expect you to guarantee recovery while refusing to invest in basic controls, be careful.
You don’t become ready by reaching a point where there is nothing left to learn. Many people apply once they’ve gained as much as possible in their current support role and are ready to take on broader responsibility. Your three years of experience, Microsoft background, certification work, and willingness to learn are a reasonable foundation.
Build good habits from the start: use change management, keep detailed documentation, maintain an inventory, avoid making untested changes during business hours, and create clear escalation paths. Your first objective should be understanding the environment and reducing risk, not trying to redesign everything immediately.
Be realistic about the personal cost. Small IT teams often involve after-hours maintenance, unexpected outages, and being the person everyone contacts when something breaks. Ask about on-call expectations, planned maintenance windows, vacation coverage, and whether the outside providers are available during incidents.
If the compensation and support match those responsibilities, it could be a worthwhile next step. If they want a one-person IT department while paying and staffing it like a basic help desk role, that’s a warning sign regardless of your technical ability.
The position sounds like a support-to-sysadmin transition rather than a traditional senior infrastructure role. Your Microsoft 365, Entra, Intune, and endpoint experience is directly useful, and the missing server and networking knowledge can be built over time. Start by learning the fundamentals of DNS, DHCP, Active Directory, Group Policy, virtualization, firewalls, backups, and recovery testing.
Before you accept, ask practical questions: What servers and network equipment are in use? Who administers them today? Are backups monitored and regularly restored in tests? Is there an incident-response plan? What happens after hours? If the answers are vague, treat that as a business risk rather than a personal failure.
You’re probably more ready than you feel. Nobody knows every part of systems administration before taking the first role, and imposter syndrome is extremely common. The important skill is being able to say, “I don’t know yet, but I’ll find out,” then research carefully, test changes, document what you learn, and ask for help before making a risky production change.
That said, clarify the expectations before accepting. Find out what systems you would own, who handles emergencies, whether the senior technician or networking company will support you, what backups exist, and whether you’ll have time and budget for training. The job could be a great growth opportunity, but you don’t want to unknowingly become the sole person responsible for recovering an undocumented environment.
Even experienced administrators regularly encounter technologies they haven’t used before. Admitting that early is much safer than pretending to know something during an outage.
A job title matters less than the actual authority and resources. Make sure you’ll be allowed to fix problems instead of being held responsible for systems you’re not permitted to change.