Stay at job or take new job
retained text
4 years at a national MSP, 2 of them as a senior engineer. I'm the only senior technical resource for my region..the sole escalation point for network, endpoint, identity, cloud, email, and vuln management, plus a couple of platforms nobody else on my team is certified in. I've been lucky to stack certs here. The problem is I've been told repeatedly there's nothing above me. Company direction shifts constantly with every cost-cutting push. My promotion added admin and project load, and that scope has kept growing to the point where another promotion would just be accurate to what I'm already doing. There's nobody above me to learn from technically except my boss, who's been offloading his responsibilities onto me so he could move up. He said there was nowhere for me to go until he moved. He moved. There's still nowhere to go. I'm covering two vacant roles with no plan to backfill (thanks, private equity). Comp is low six figures with a scheduled inflation bump and no promotion path anyone has been able to describe \*\*The offer:\*\* internal security engineer at a mid-size company. About 10% over current salary, with further increases written into the letter that put me \\\~15% up within a year, plus a performance component. Different cloud than I'm used to, but picking things up fast has always been the job.. The IT manager was honest that year one is mostly operational /admin: access reviews, alert triage, audit documentation, tier 2/3. architecture and automation, the part I actually want, is framed as “growth goals” down the line. My MSP has no real cloud presence beyond VMs in Azure; the new role has actual in-house applications I'd be securing. **Case for staying:** I'm indispensable, which is leverage and also a trap. Broad exposure across many environments and tools. Stability, and a team I know (though I do not always enjoy). A counteroffer conversation opened after I disclosed the offer..they've asked for a week to put something together and say they'll do anything to keep me **Case against staying:** nothing is in writing yet, and it feels too late. If they can only produce something now, I don't think it's sustainable, and I'll be the person who almost left. I've had review after review where I exceeded expectations and was told there's nowhere for me to go. "You're too big for us, you should go somewhere else" is its own kind of answer **Case against going: I**d be trading a place where I'm valued for being the new person again. The manager doesn't know how I work. I don't know that this place is actually better. I already accepted, but the counteroffer has me second-guessing. I also think the MSP will be in bad shape if I leave, and two weeks isn't enough handoff time.. For context on what I want: I like building things and making systems talk to each other. The work I'm proudest of wasn't assigned- I found a reporting gap in a vendor product, reverse-engineered the undocumented API behind it, and built my own tooling to fill it. Questions for anyone who's been here: \\- Has anyone made the MSP-to-internal jump? \\- Does "growth goals" language ever turn into actual growth, or is that just how operational roles get sold? \\- Is being indispensable somewhere with no ladder as bad a sign as it feels? \\- Should I feel bad about leaving them short-handed?
document fetched 2026-09-27 00:34 · canonical https://reddit.com/r/sysadmin/comments/1wqj9qy/stay_at_job_or_take_new_job