I've worked in large organizations since graduating and have about 14 years of IT experience, ranging from help desk and break/fix support to data migrations, running a small help desk, and handling sysadmin-level responsibilities. I previously held a sysadmin title, but an acquisition eliminated the onsite IT team, and my current role is officially Support Specialist.
I'm considering a fully remote Sysadmin II position with a managed service provider. It would pay about $8,000 more and give me the title and responsibilities I'm looking for. The IT director asked why I wanted to make what he viewed as a backward move, since people often leave MSPs for larger internal IT departments. I told him the decision wasn't primarily about pay or title, although both are definitely important factors.
I've never worked directly for an MSP, though I've frequently been the internal point of contact for MSPs supporting organizations where I worked, including healthcare and academia. I'm trying to understand what the transition is really like. Should I expect much heavier ticket volume, constant context switching, incomplete documentation, and a major impact on work-life balance? Or can an MSP provide valuable technical breadth and career growth?
My current manager knows I've been exploring part-time work but does not know about this interview. He has mentioned moving me away from delivery and support work and possibly training a new employee, though there is no clear promotion or timeline. I've also had stress-related heart issues in a previous demanding role, so workload and health are major considerations. Based on what I've heard, I'm leaning toward staying with my current organization, but I'd appreciate perspectives on whether this move is truly a step backward.
6 Answers
There is no universal answer because MSPs range from well-run specialist firms to chaotic ticket factories. Try to speak with future teammates and ask what a normal day looks like, how many clients each administrator supports, how often people work after hours, and whether the company has separate help desk, engineering, and project teams. If the answers sound evasive or the role is measured almost entirely by ticket counts and billable time, staying or finding another internal role may be wiser.
With your experience, you do not need an MSP just to prove you can work in IT. If the offer is mainly attractive because of the title and raise, compare it with other internal sysadmin roles too. An MSP could broaden your skills, but a healthier organization with a clear advancement path may provide the same career progress without the grind.
Your manager’s comments about eventually training someone are not the same as a promotion or a concrete career path. It is reasonable to choose the role that offers the title, pay, flexibility, and responsibilities you want now. There is nothing wrong with saying compensation and advancement are part of the decision. Just do not rely on a vague promise from your current employer unless they can provide a specific position, timeline, and salary.
The downside is that many MSPs are understaffed by design. You can end up juggling dozens of clients, large ticket queues, SLAs, time tracking, angry customers, and urgent issues while constantly being pulled away from planned work. Some technicians gain valuable experience; others burn out quickly. Before accepting, ask about average ticket volume, queue size, on-call expectations, utilization targets, turnover, documentation standards, and why the position is open.
An MSP can be an excellent learning accelerator, but the workload is usually much broader and more fragmented. You may support many clients, each with different networks, policies, tools, and undocumented quirks. Ticket volume and service-level targets can be intense, although project or professional-services teams are often more controlled than the general support queue. It is not inherently a backward move; it depends heavily on how well the MSP is managed and what team you join.
Some MSPs standardize their technology stacks and procedures, which makes supporting multiple clients easier. The important questions are how many environments you would own, how tickets are measured, how much project work exists, and whether documentation and staffing are actually adequate.
The main career benefit is variety. You can gain hands-on experience with identity, cloud platforms, networking, security, backups, servers, and automation much faster than in a highly siloed enterprise role. That broad exposure can make you more attractive for future internal sysadmin or engineering jobs. Many people use an MSP as a two- to five-year skill-building phase rather than as a permanent destination.
I moved from internal IT to an MSP and learned more in months than I had in several years at a large company. It was stressful, but the experience helped me move back into internal IT later with a much broader skill set.
A fully remote position and an $8,000 raise are meaningful advantages, but they may not compensate for worsening health or work-life balance. Given your history of stress-related heart problems, treat workload and management quality as deal-breakers rather than assuming you can endure the job temporarily.