MSP Jobs

Hey guys. I'm 21, still in school for Computer Networking, and working at an MSP. Is this a good place to be at? It's my first IT job and I've been into computers for about 17 months. It's just really stressful and they expect SO much out of me when I only work part time. I feel like no matter what I do is wrong and it makes me feel like crap. Should I just stick it out while I'm in school? Will this on my resume help me with a job in the future? Or will it hurt it?

Find more posts tagged with

Save $250 on 2025 certification boot camps from Infosec!

Book now with code EOY2025

Button

Comments

RouteMyPacket

What is "working at an MSP"? Working at an MSP could mean anything, elaborate.

jerseytech

MSP=Managed Service Provider

Danielm7

I don't think the question was what does MSP mean, but more, what are you doing there? What are they asking you to do that is wrong? Are you actually doing everything wrong or is it just a bad work environment?

jamthat

jerseytech wrote: »

Hey guys. I'm 21, still in school for Computer Networking, and working at an MSP. Is this a good place to be at? It's my first IT job and I've been into computers for about 17 months. It's just really stressful and they expect SO much out of me when I only work part time. I feel like no matter what I do is wrong and it makes me feel like crap. Should I just stick it out while I'm in school? Will this on my resume help me with a job in the future? Or will it hurt it?

Are you in their NOC or what? I just started at an MSP as well. I hear where you're coming from with high expectations haha..just roll with it and appreciate the fact that you're given the opportunity to learn so much so quickly on the job. I've learned wayy more about networking in the past two months (I'm in a Jr. Engineer-ish role) than I expected to, and there's still so much more to wrap my head around!

My take on it so far - it's awesome experience and a great starting point. Stick it out! And if you feel overwhelmed or like you're always 'wrong', I felt like that too initially. I can't stress this enough - don't be afraid to ask questions!

jerseytech

For instance. Last week on Tuesday I was told that I needed to prep this PC for a new hire. All day long I kept asking for the resources that I needed (keys, product keys) I asked my manager, than my director, than the VP, even the owner! Finally I got all the stuff but it wasn't until 4:45 (we leave at 5:30). I had to go at 5:30 because I have school right after which they KNOW, they new since my interview. I got called in for a meeting and got my a** chewed out because it didn't look "clean" enough on the desk area. I said "I had no time and by the time I was done installing and updating everything I had to go" and that wasn't good enough... So was I suppose to be late to school?

jerseytech

I'm an entry level guy in the NOC

pram

MSPs are usually terrible environments, BUT, you'll more than likely get very robust experience if they have a large amount of clients. I worked at one for a year. It was terrible and I hated it the entire time I was there, but I definitely don't regret it.

ande0255

I just started at an MSP today on the VoIP side of things, haven't got into much yet, but the broadness of requests and issues indicate it's going to be a **** ton of experience fast. The company seems ok too, even though the commute sucks.

TheNewITGuy

I am against MSP's 100% - I work for one actually and they're terrible environments without a work/life balance and the expectations are ridiculous. However that being said, you do drink from the fire hose and you'll be more valuable quicker.

Hypntick

Having worked at MSP's for almost 3 years now, I will agree the expectations are a little higher than you would expect. However, as others have said, you will learn more, and get to touch more technologies than you would at a regular corporate environment. If you can handle the stress and are capable of learning quickly, the experience is well worth it.

One of the most positive aspects is the fact you're working at a small business (well at least in my case). So if i've got to go to the doctor or have an obligation come up, I can take care of it with no questions asked. Now will my next job be a MSP? Only if I can find a MSSP, so I can expand my security knowledge as quickly as i've done with the other aspects. Although if I can't find one of those, it'll be back to a non-MSP, which may not be enjoyable as i'm sure I won't have the freedom that I do here.

Good luck where you are, if you can stick it out, it's worth the experience.

darkerz

I worked at an MSP for 1 year, I started off as a "MSP Network Technician".

Within 2 months, I was leading multiple projects, deployments and direct customer engagement.

Within 5 months I was the lead Network Engineer for our company, releasing and designing an entirely new Cisco based MetroE product set and selling it to customers.

By month 12, I had built out and deployed 2 colocations linked together by a L2 link, multiple BGP sessions, a large switching fabric for our hosted VoIP solution - which was a success.

I would tell you that NO corporate or other experience could have given me 4-5 years of practical, networking experience all condensed in 1 hectic, on call 24x7x365, 8 to 16 hour a day work schedule. Totally worth it.

RouteMyPacket

jerseytech wrote: »

For instance. Last week on Tuesday I was told that I needed to prep this PC for a new hire. All day long I kept asking for the resources that I needed (keys, product keys) I asked my manager, than my director, than the VP, even the owner! Finally I got all the stuff but it wasn't until 4:45 (we leave at 5:30). I had to go at 5:30 because I have school right after which they KNOW, they new since my interview. I got called in for a meeting and got my a** chewed out because it didn't look "clean" enough on the desk area. I said "I had no time and by the time I was done installing and updating everything I had to go" and that wasn't good enough... So was I suppose to be late to school?

ALWAYS leave yourself a paper trail. Email requests for resources...then when they jump you on something. Simply provide a trail of you attempting to reach out for info/assistance.

Oh, and clean your area man..sheesh! ha

DoubleNNs

darkerz wrote: »

I worked at an MSP for 1 year, I started off as a "MSP Network Technician".

Within 2 months, I was leading multiple projects, deployments and direct customer engagement.

Within 5 months I was the lead Network Engineer for our company, releasing and designing an entirely new Cisco based MetroE product set and selling it to customers.

By month 12, I had built out and deployed 2 colocations linked together by a L2 link, multiple BGP sessions, a large switching fabric for our hosted VoIP solution - which was a success.

I would tell you that NO corporate or other experience could have given me 4-5 years of practical, networking experience all condensed in 1 hectic, on call 24x7x365, 8 to 16 hour a day work schedule. Totally worth it.

Wow, that sounds awesome.

I'm looking for a role where I could gain valuable experience like that.

Hypntick

@DoubleNNs MSP is the way to go then, just be prepared for a lot of stress. You'll get sales guys promising things that can't be delivered, projects that run way out of scope, "C" levels of SMBs breathing down your neck, and every possible config that you can think of supporting. Having the ability to do just about anything you've wanted to do is quite nice.

tier~

I'd love to hear some more opinions on working for MSPs/VARs from those who've done it or are currently doing it. I've been pondering trying to get into one of a few MSPs in the area, leaving the corporate world, for many of the aforementioned reasons.

Even though the hours can be miserable and the expectations completely unreasonable, the experience and breadth of technologies you encounter in a consulting environment just seems like it can't be beat.

As for the OP, despite the tough conditions, I would think the experience gained would outweigh the negatives depending on what all you're getting to work with in the NOC and the room for growth.

alan2308

I've been working for an MSP for a year and a half now and I've absolutely loved it. Based on what I've read here, I guess I got lucky and work for one of the few good ones. The hours aren't what I've heard normally, and the work is mostly fun.

I've worked my way up from the new know-nothing to running the technical side of the house in that short time. I've done wireless deployments, server upgrades, voice deployments, active directory deployments (Windows Server and Samba 4 based), company mergers, and turned a few computers off and on again. The real fun of it is the internal stuff. If I think we need to move from an SBS based server to a multiple Exchange server database availability group, I lab it up once or twice and then build it. If a client mentions Dropbox, I build an alternative that we run.

j23evan

pram wrote: »

MSPs are usually terrible environments, BUT, you'll more than likely get very robust experience if they have a large amount of clients. I worked at one for a year. It was terrible and I hated it the entire time I was there, but I definitely don't regret it.

Truer words have never been spoken. MSP's are a great learning environment, and will develop you to be a good engineer/SME. I have the scars to prove my time and am glad to have it behind me. That being said I would stick with it until you have got enough experience under your belt to move up the ladder.

ande0255

Yes today is my second day and I've learned how to setup profiles in call manager, how to trace and debug call routing scripts / triggers, and I barely knew anything about CUCM / UCCX / UC before today.

Also got to troubleshoot routers and switches for a wireless issue, and got kudos for seeing it through to the end, on my second day

MSP'S are like an IT boot camp that you're getting paid to attend, if you get a chance I'd definitely suggest taking the job, as there's a good potential for exploding growth if you can hang in there!

TheNewITGuy

I think an MSP gig is good for folks starting out and wanting to gain a ton of knowledge. Having a family and personal demands outside of work, the hours and stress can take a toll on you.

ande0255

^Yup, very true. I wish I would have known about this years ago, I would be soooo much further into my career. I guess now in life is better than never though

TheNewITGuy

I actively work for an MSP and have done so now for a few years - I came from Corp. I have legit lost all my passion for IT working these types of positions. YMMV.

Zartanasaurus

jerseytech wrote: »

For instance. Last week on Tuesday I was told that I needed to prep this PC for a new hire. All day long I kept asking for the resources that I needed (keys, product keys) I asked my manager, than my director, than the VP, even the owner! Finally I got all the stuff but it wasn't until 4:45 (we leave at 5:30). I had to go at 5:30 because I have school right after which they KNOW, they new since my interview. I got called in for a meeting and got my a** chewed out because it didn't look "clean" enough on the desk area. I said "I had no time and by the time I was done installing and updating everything I had to go" and that wasn't good enough... So was I suppose to be late to school?

What were you doing in the mean time while waiting to get your product keys? Nothing was stopping you from installing the OS and running the updates without product keys.

darkerz

There is such a talented, motivated, driven group of people on Tech Exams.

It would be a great place to rally troops for a MSP, remote-work kind of start up company.

I can't be the only one to have thought this.

Zartanasaurus

darkerz wrote: »

There is such a talented, motivated, driven group of people on Tech Exams.

It would be a great place to rally troops for a MSP, remote-work kind of start up company.

I can't be the only one to have thought this.

It takes more than tech talent to start and run a company.

TomkoTech

Zartanasaurus wrote: »

It takes more than tech talent to start and run a company.

Client acquisition for starters.