Job Hopping Woes

N7Valiant

Following up on my job transition from MSP > Federal, I'm going through some concerns about my new position.  Namely that there's an overwhelming sense that it will be a Field Tech position.  All signs are pointing in that direction, and compared to what I was doing before (working on client servers, Powershell, automation, domain registrars, Office 365), it does seem like it would be quite a few steps down in terms of skill.  I can't say for sure yet since I'm still waiting on a process for access to systems for a while yet.

I am curious if, after finishing my MCSA Windows Server certification I should just move on and look for another job that lets me work with servers?  Or wait 1-2 months after?  Concerned about job hopping showing up on my resume.  However I'm also curious if my experience at an MSP isn't grossly distorting my expectations.  I'm not sure if many places in-house or government would let someone they just hired touch their servers.  Although because it's the government with their technology stack from almost the last decade, I am experiencing a bit of frustration with how run-down and inefficient the processes are.

Granted, I'm not sure it'll be that bad to just apply to positions that give me exactly what I'm looking for (mostly Windows Servers) in the meantime...  Again, just concerned I'll have busted my butt for this cert and spend the next year painfully crawling towards it and having my skills waste away because most of my day was spent fixing laptops and desktops.  The pay is great for what I do, but it's the skills I want most of all.

jeremywatts2005

Never be afraid to change jobs. It is your career and your happiness take hold of it and go forth. Companies have no problems at any point and time cutting employees and we should not be afraid to cut them out of our lives. If they are not fulfilling or helping us to fulfill that ultimate goal which is retirement and short term building crazy good skills that help push our dollars up. Our time is money don't waste the most valuable resource you have doing a job that does not move you forward. Seeing beyond today will help make the decision to transition to another company easier. I have done it several times over my 20 yrs in the field. 2006 I was stuck at making 35K a yr and going nowhere when I figured out that I needed to make some tough choices and advance my career. Now 13 yrs later I make $150K a yr. Just 6 yrs ago I was making $70K a yr. Take charge and advance best of luck

techie2018

I agree. If you aren't happy at a job or you feel you aren't getting a chance to improve or grow your skills leave. There is no point being stuck in a miserable job, or a dead end job, unfortunately there are a lot of people that are.

That's always been one of my keys to success. I'll tell anyone that will listen, job hop until you find the right situation. 

DatabaseHead

I left a job I was at for ~18 months and it was pretty decent and the benefits etc were fantastic.  I was lied too (classic bait and switch) and I had to quit and now I am looking.  F it, I am not sitting around mopping around feeling sorry for myself.  I bounced and now I am on the prowl.

scaredoftests

I despise being lied to in an interview.  It takes all the trust away.

Pmorgan2

What is your federal position sub parenthetical in your position description or on your SF-50?  It's not common for Customer Service positions to do server work, but not unheard of.  If System Administrator or Enterprise Architecture is in your description, then I expect you'll be all over those servers. 

Federal position postings can feel pretty misleading.  They are very general and don't give you a good idea of what you'll actually do.  It's hard to even get a good idea from the interview or the first few weeks of work.

ArabianKnight

Too much job hopping can backfire if you are not careful.  I am noticing more and more recruiters ask why I have been at X number of jobs in only a certain timeframe.  I tell them that its government contracting and the contract ended.  Outside of the gov contracting space though private sector companies may not even call you if they see only shorter term jobs on your resume.  They dont understand the contracting world.

SpetsRepair

I'm still looking. Maybe a few months now consistently applying and looking for work in the network/security engineering side

I'm currently a Network design engineer and have been looking for something else. No luck so far

What sucks is I'm in Denver and I know there are jobs out here but no real offers yet. Just interviews, phone screens and RTRs etc..

Job hunting sucks

MontagueVandervort

ArabianKnight said:

Outside of the gov contracting space though private sector companies may not even call you if they see only shorter term jobs on your resume.  They dont understand the contracting world.

I label my contract jobs "Contract" on my resume, and I haven't had any trouble with this so far.

Nobody even brings it up during interviews either.

paul78

ArabianKnight said:

..... Outside of the gov contracting space though private sector companies may not even call you if they see only shorter term jobs on your resume.  They dont understand the contracting world.

I work in private sector tech in the US and contracting is very well understood among hiring managers. At least in financial services and venture-backed tech which is the sector that I'm most familiar.

Azt7

MontagueVandervort said:

ArabianKnight said:

Outside of the gov contracting space though private sector companies may not even call you if they see only shorter term jobs on your resume.  They dont understand the contracting world.

I label my contract jobs "Contract" on my resume, and I haven't had any trouble with this so far.

Nobody even brings it up during interviews either.

Yeah I have a 1 year and a 3 month one in my recent history. 

Since I indicate on my resume that they are contract, it just goes smoothly. 

N7Valiant

Pmorgan2 said:

What is your federal position sub parenthetical in your position description or on your SF-50?  It's not common for Customer Service positions to do server work, but not unheard of.  If System Administrator or Enterprise Architecture is in your description, then I expect you'll be all over those servers. 

Federal position postings can feel pretty misleading.  They are very general and don't give you a good idea of what you'll actually do.  It's hard to even get a good idea from the interview or the first few weeks of work.

Well the thing is, my actual employer reached out to me advertising the position as "Cybersecurity Analyst".  I'm actually contracted out to another contractor (so subcontractor?) who contracts out to the DoD.  My offer letter says I'm an IT Specialist - Mid.  The paper on my desk says I'm a Field Service Technician.

During the phone interview where 2 of my direct supervisors didn't show up until the last 2 minutes, the 1 other guy whom I never saw even now said maybe they might want me writing Powershell scripts for their Exchange server.  The job description mentions network scanning and scripting in an Enterprise environment.

I see none of that and no indication that anyone in the office has any management access over any server.  I did also hear from other new hires that they were bothered that said supervisors only interviewed them for 2 minutes and asked no technical questions.