I've been working as a junior systems administrator for about 10 months at a small company of roughly 50 employees. My current work includes Entra ID, Intune, MDM, MAM, Defender, Sentinel, PIM, and RBAC, along with asset management, user training, documentation, and regular helpdesk responsibilities. In practice, I'm probably closer to a Tier 1.5 helpdesk role despite having a junior sysadmin title, and I currently earn about $55,000.
A recruiter contacted me about an L3 position at a local managed service provider. The role asks for five to eight years of experience and lists technologies such as Cisco servers, Citrix, and Azure virtual machines—many of which I haven't worked with extensively. The salary is $86,000–$90,000, which would be a major increase, but I'd be stepping into what sounds like a senior-level position in a demanding MSP environment.
The person currently in the role is retiring in the spring and would train me before leaving. Is this a reasonable opportunity for someone at my experience level, or would I be setting myself up to struggle with work intended for a much more experienced administrator?
5 Answers
This could be a very good career move if you’re comfortable learning aggressively. Changing jobs is often how people get meaningful raises, and exposure to infrastructure, virtualization, networking, and client environments could make you much more marketable. Just ask direct questions before accepting so you know whether the training is genuine and whether the expectations are realistic.
I’d seriously consider taking it. The worst case is that the role doesn’t work out, but you’ll gain experience and earn substantially more while you’re there. Having the retiring employee train you is a much better situation than being dropped into the job with no support.
The biggest concern is the workload. MSPs can be intense, and you may be expected to handle several clients, urgent issues, and unfamiliar technologies at the same time. Make sure you understand the on-call expectations, client load, training plan, documentation, and what happens after the current employee leaves.
The company’s size matters too. A larger MSP may have better processes and more people to ask for help, while a tiny provider could leave you responsible for everything with little direction.
Don’t let the job description intimidate you too much. Employers often write an idealized wishlist, and they may hire someone who has the right attitude and can learn quickly instead of someone who checks every box. Your current experience with identity, endpoint management, security tools, and access controls gives you a useful foundation.
I’d take it seriously, but I wouldn’t assume the title means you need to already know everything. You’ll probably have gaps, especially around the listed server and virtualization technologies, but those can be learned with structured training and access to the person you’re replacing. Go in prepared to work hard, document everything, and ask for help early rather than trying to bluff your way through problems.
That workload is common in MSPs, but the higher salary makes it a more worthwhile way to build experience. I’d view it as a strong learning opportunity rather than a long-term destination if the environment becomes unhealthy.