First Job...finally got a foot in the door at an MSP but I didn't work out...

2»

Comments

  • linuxabuserlinuxabuser Member Posts: 97 ■■□□□□□□□□
    You quit your first IT job after 3 days?

    Maybe you should find a different industry.
  • techfiendtechfiend Member Posts: 1,481 ■■■■□□□□□□
    I wouldn't say he needs to find a different industry. He took on the most accelerated and potentially stressful entry level job and found out it wasn't for him. Lower stress jobs like desktop support and noc jobs he may really enjoy.
    2018 AWS Solutions Architect - Associate (Apr) 2017 VCAP6-DCV Deploy (Oct) 2016 Storage+ (Jan)
    2015 Start WGU (Feb) Net+ (Feb) Sec+ (Mar) Project+ (Apr) Other WGU (Jun) CCENT (Jul) CCNA (Aug) CCNA Security (Aug) MCP 2012 (Sep) MCSA 2012 (Oct) Linux+ (Nov) Capstone/BS (Nov) VCP6-DCV (Dec) ITILF (Dec)
  • IIIMasterIIIMaster Member Posts: 238 ■■■□□□□□□□
    Im going to be honest here. You miss your rite of passage. EVERYONE who ever started out in their first support role has been through this. NO ONE is going to hold your hand or baby you. This is IT you are there to find a solution... So im sure they had knowledge articles or you could have use google.
    I recall my first month...man my first customer burnt me hard. One of my trainers had to kiss her butt for weeks. But hey thats IT though. You are excepted to know stuff and if you dont act like you do know and find a solution. Those bumps are what builds you up man.Also this is an example as to why companies seek individuals with experience for work. Some of you newbies will come in and have no clue.
  • Tremie24Tremie24 Member Posts: 85 ■■□□□□□□□□
    Not to sounds mean or anything, but you should have toughed it out. Unless you work for a very big company, you probably won't get a whole lot of formal training. My current job, also my first IT job, I didn't receive a whole lot of training. Had a person show me around, how to log on, and a few other things. I shadowed that person for a bit and that was it. Was it overwhelming? Of course! But like others have said, you'd be surprised at how much you know when you start to taking things on. It would have eventually slowed down for you and you would have felt more comfortable. Also did you ever talk to your boss? Ask him what you should be doing next, what he wants you to concentrate on? As far as getting the feeling that your co-workers weren't welcoming, they probably had a lot on their plate. I remember my second day, I pretty much just sat my desk the whole day and didn't do a thing. The person that was training me got caught up on something and didn't have time to keep training me that day.

    One thing to remember too is working in IT out in the real world is a lot different than being in the class room.
  • N2ITN2IT Inactive Imported Users Posts: 7,483 ■■■■■■■■■■
    Sorry to hear things went down like they did, but like a few others have mentioned quitting is the worst possible strategy.

    Well not really the worse but one of the worse.

    What I have experienced from quitting is when you do quit you start to build a pattern that can end up ruining your career. It can be extremely toxic so be careful next job, because if you start to quit over and over again your resume will be trashed for life and you will train yourself to accept that behavior.

    I've quit two jobs straight out before without another job waiting. Once it was absolutely required, my co worker kept talking about suicided. I told management and my co workers no one did anything. I was getting physically ill, so much my body and lower back was locking up. I eventually quit after the contract was over which was 3 months. The other time I quit the heat and pressure started to mount and I bailed.

    To this day I regret doing that, I burned a lot of friends and family. Even with the 2 weeks people know I bailed on them.

    Anyway good luck but I just wanted to toss my two cents in.
  • LeBrokeLeBroke Member Posts: 490 ■■■■□□□□□□
    Honestly, if you felt like you weren't doing anything at the place or couldn't help with tickets.. sit there and do nothing. Worst case scenario is, you get fired.. which is kind of what you did yourself.

    Shitty job > no job unless you've got wealthy parents/SO, and even then... Unless you're a rich retired teen actor/lottery winner and can afford to cherrypick until you're 100% sure you enjoy it.

    Thing is, even with a short job (even if it's only a few months), it'll be much easier to find the next one. Short employment will turn away less hiring managers than no previous experience whatsoever. Just don't give a dumb answer at your interview, like "well, my boss was a moron so I've had it after a month and advised him to engage in some inappropriate and anatomically improbable behaviour."
  • brianshafferbrianshaffer Member Posts: 5 ■□□□□□□□□□
    @appolloofc The company was using autotask (ticket system) and Level Platforms (RMM).

    Thanks again for those providing feedback and insightful thoughts.

    Next time I have issues I'll be sure to come here to the boards to get advise about the best way to deal with any problems I'm having at the workplace.

    Hearing others tell their stories of having similar experiences has given me some perspective.
  • ratbuddyratbuddy Member Posts: 665
    Now, go crawling back on hands and knees and lick boots until they give you a second chance. Not kidding.
  • aderonaderon Member Posts: 404 ■■■■□□□□□□
    Sounds pretty lousy to me. In all four IT positions I've been in, I've had multiple weeks of training. Usually a month, but sometimes as high as 10 weeks and that doesn't include the time they give you to sit with people and watch what they're doing. I don't think you're really missing out by leaving, but personally I would've stuck with it while looking for other jobs.
    2019 Certification/Degree Goals: AWS CSA Renewal (In Progress), M.S. Cybersecurity (In Progress), CCNA R&S Renewal (Not Started)
Sign In or Register to comment.