Are 3 months long enough?

Currently I'm in a PC Support/It Support/Trainer position which pays $0.00/hr. Obviously it's volunteer. I took it to put something on my resume to, perhaps, help me get my foot in the door.

Initially I planned to stay for 6 months but because it took so long to even get hired, that cut 2 months out of my plan; therefore, my altered plan had to become 4 months. As the environment is becoming more & more toxic, I'm considering leaving after 3 months.

To those whom have more experience in the employment aspects of IT:
Will 3 months of this on a resume be enough?
Is there even much difference between 3 months than 4, to an employer?
Was 4 months even enough? (I don't think I can make it until 6 months lol.)

I would appreciate any feedback. Thank you in advance.

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

olaHalo

Honestly I wouldnt put the amount of time on your resume. Just put that you worked there.
I did a 3 month internship and I did not say how long I was there until I was asked. (got the job btw)
I am sure people will disagree with that.

Once youre in the interview for your next job you can tell them that you were only there for a short amount of time.
At this point youre already golden since the point of youre resume is just to get you into the interview.

Iristheangel

I would specifically mark that it was a non-paid internship. That's the only way you're going to get by with that short of a first job on your resume. That being said, most people do internships in college and it's completely normal to have three month internships here and there so I wouldn't worry this early in your career. Is there anyone there that can vouch for you? If so, get a letter of recommendation now before you leave

N2IT

It's okay to list it as a 3 month project which you volunteered to perform duties or like Iris mentioned a non paid internship.

I'm currently on a 3 month project, I just got off of a 6 month project. As long as you explain at a high level what was going on you will be fine. Don't worry about getting to detailed.

Raywire86

Sure just list it as it is and start applying. Don't limit yourself, just go for it, and keep busy in the mean time. Here is how things worked out for me:

Got A+/Net+
3.5 months working as a integration tech (depot pc technician) [14/hr]

Got CCENT, and the experience above got me:
11 months technical operations support (half desktop support, half data room tasks/monitoring) [18hr]

Got CCNA and left for:
data center operations specialist (all data center rack and stack, and managing of equipment) [25/hr]

you can make a lot of progress in a short amount of time. Use certs to "prove" your skill set if you don't have the most experience. Keep busy and before you know it your résumé will beef up.

Xyro

Ok, so it looks like I have a number of options as to how to list/refer to this on my resume, making the 3-month period "ok" ... thank you ola, Irish, & N2.

Raywire86 wrote: »

Got A+/Net+
3.5 months working as a integration tech (depot pc technician) [14/hr]

Got CCENT, and the experience above got me:
11 months technical operations support (half desktop support, half data room tasks/monitoring) [18hr]

Got CCNA and left for:
data center operations specialist (all data center rack and stack, and managing of equipment) [25/hr]

you can make a lot of progress in a short amount of time. Use certs to "prove" your skill set if you don't have the most experience. Keep busy and before you know it your résumé will beef up.

This is good advice by example. I like the way you jumped levels each time you got a new cert. I like it. It's very incremental & makes a lot of sense.

DoubleNNs

Iristheangel wrote: »

That's the only way you're going to get by with that short of a first job on your resume.

But conversely, I've seen a lot of advice in this forum promoting job hoping earlier in our careers, saying after 3-6 months of experience it's possible to move up to a better job. The different opinions confuse me a bit.

Xyro

DoubleNNs wrote: »

But conversely, I've seen a lot of advice in this forum promoting job hoping earlier in our careers, saying after 3-6 months of experience it's possible to move up to a better job. The different opinions confuse me a bit.

Same, but perhaps it's just a matter of a difference of opinions.

It seems only logical though that the longer you stay in positions, the more stable & less of a risk you will seem to someone hiring.

N2IT

Projectized work is not job hopping it's called working a project. I know some very successful people who work as project managers and team members anywhere from 3 months project to 2 years. (just to give you a idea/range)

One of my friends graduated from the state uni in 2000 with a CS degree emphasis in OO programming. He took a Java a position for 1 year out the gate and has jumped from project to project for the last 13 years. He has even taken a one month project where he billed for over 175 an hour/80 hours a week with overtime. He was burnt after that one month but he was paid well. His wife is an executive and has amazing benefits, (cadillac plan). His only mission is to kill it and bill it.

He has never been without a job and has stuck to all Java positions so take it for what it's worth.

Job hopping is a stupid term to be honest with you. With todays resource model / hiring resources for short termed endeavors is common and becoming the norm.

Xyro

Yes, obviously contract & project positions are exempt from the terminology; however, this specific position was neither; therefore, both Iris's & Double's considerations were applicable in this circumstance.

Iristheangel

There's a different between job hopping in 1-2 years and job hopping within 3-6 months. I would never advise to job hop that early UNLESS it's seriously detrimental to you (I.e. emotionally abusive boss, harassment, etc)

This work you were doing is volunteer therefore doesn't apply as "job hopping" since it's not really a job. You aren't getting paid, paying taxes, etc. No one expects you to be paid $0 permanently so coming and going is fine. Any employer would understand as long as it states something on your resume about it being an internship or volunteer work

Plantwiz

Iris and N2IT are correct. Job hopping and projects are completely different.

IF you promised you'd work for 6 months and are now leaving after only three, it will matter if your new potential employer contacts the old one for what they think about your performance. IF this volunteer position is also in agreement to cut the project down to three months (regardless of the reason the feelings are mutual and they will wish you well leaving) than approach them and get a letter of recommendation. If your parting is not on mutually agreed terms than stick it out for three months and do the absolute best you can do. 20 years from now 3 months will not seem like that big-of-a-deal.

And I agree with Iris on the volunteer part NOT being considered a job. It is considered experience, but not a job. IMHO
What matters (IMO) is the terms in which you said you would 'volunteer'. If you promised six months, I'm leaning toward completing what you set out to do regardless of the conditions. Your 'word' will carry more weight down the road if you do what you said.

About7Narwhal

Why not eliminate the job hop problem all together and try to get a position while at the volunteer place? Generally, there is no term agreement for volunteer work, but if you agreed to stay for a certain amount of time, I would strongly consider doing that if possible. Assuming you have a good boss, they may be a great resource for job opportunities (based on the assumption that the volunteer work is some sort of community location: eg a church). Else, find a job and keep building experience while you look. It is easier to put "X date - present" then to explain why you left the position after only 3 months.

DoubleNNs

Well, I agree with the fact that volunteer work is different. So is contracts and project work.

The one sentence I had trouble with was the one I quoted. I feel like I've read a lot of threads her eon TE about people aggressively climbing the latter in their first 1-2 years of their IT career - i.e. Help desk for 3 months, desktop support for 6 at new company, junior net admin for 5 months at new company, then getting promoted in the same company where they stay for an additional year.

After reading thru threads like that I've started to believe that 3-6 months in your first job IS enough, and is usually the only way to start actually getting decent pay. Am I wrong in thinking that?

About7Narwhal

DoubleNNs,

I think it really depends on the job and company you are with. I stayed in my first Professional IT job for a little less than 2 years doing Service Desk. The company was a Fortune 500 and I was assigned to the Service Desk contract supporting another Fortune 500. The atmosphere was great and I learned a lot. Unfortunately, there was no option to move up so I started looking.

My current position has tenure of about 5 months and I am already thinking about applying for another position within the same company. My experience gives the impression that it can go either way. In addition, I think moving around is okay if you show that you are continually getting more responsibility or better jobs. While there is a limit, I don't think anyone would argue with an interviewee coming in and saying, "I was offered a position that granted more responsibility and challenge."

NetworkVeteran

DoubleNNs wrote: »

After reading thru threads like that I've started to believe that 3-6 months in your first job IS enough, and is usually the only way to start actually getting decent pay. Am I wrong in thinking that?

It's one way, but not the only way. I stayed with my first company for five years, and know many who have done the same. When my growth has aligned with my employer's business needs, I've had little trouble obtaining a bonus or raise. After all, most employers want to remain competitive and retain talent. This alignment is easier at larger companies with a multitude of roles.

buzzkill

About7Narwhal wrote: »

Why not eliminate the job hop problem all together and try to get a position while at the volunteer place?

Maybe because in his original post he clearly states he finds the environment "toxic" and seems desperate to get out of there as quickly as possible.

About7Narwhal

If Xyro were desperate to leave, he probably would not have posted this thread asking if he should stay longer. Xyro is considering leaving the position and I am giving an alternative to consider. I apologize that I did not make the same assumption you did.

linuxlover

I guess volunteer work doesn't really count as work experience then? Is is worth going for internship or is it better to go for a helpdesk job even though that has nothing to do with networking which is what I want to do?

gbdavidx

Raywire86 wrote: »

Sure just list it as it is and start applying. Don't limit yourself, just go for it, and keep busy in the mean time. Here is how things worked out for me:

Got A+/Net+
3.5 months working as a integration tech (depot pc technician) [14/hr]

Got CCENT, and the experience above got me:
11 months technical operations support (half desktop support, half data room tasks/monitoring) [18hr]

Got CCNA and left for:
data center operations specialist (all data center rack and stack, and managing of equipment) [25/hr]

you can make a lot of progress in a short amount of time. Use certs to "prove" your skill set if you don't have the most experience. Keep busy and before you know it your résumé will beef up.

I wish i could find something like that, desktop and data center type gig, where do you live?

Xyro

buzzkill wrote: »

Maybe because in his original post he clearly states he finds the environment "toxic" and seems desperate to get out of there as quickly as possible.

Exactly... why would I want to find a permanent position somewhere that I'm labeling "toxic"? lol

This has all been great feedback & I simply wanted to see public experience on this topic. I've decided to leave on the 3-month mark, which is just a couple of weeks away. If I stay any longer the outcome may be that I cannot put this on my resume at all as I would be cautious future employers may contact where I'm working now.

I believe it's better to leave now, while items are still (barely) balanced.

Iristheangel

If you don't mind me asking, what makes the environment "toxic?"

About7Narwhal

Xyro wrote: »

Exactly... why would I want to find a permanent position somewhere that I'm labeling "toxic"? lol

Perhaps my suggestion was unclear?

Find a job somewhere else while you are at the volunteer place then give 2 weeks notice to the volunteer position. It is easier to find a job when you have one (volunteer work included). I was trying to say that if it is a church or something similar, leaving on good terms is best because of their reach within the community. You don't want someone who sees that many people saying you were a terrible employee.

Xyro

About7Narwhal wrote: »

Why not eliminate the job hop problem all together and try to get a position while at the volunteer place?

I believe we were both going by this, at least I was.

The idea of looking for a job while I'm still there is a good 1 though, thank you.

Iristheangel wrote: »

If you don't mind me asking, what makes the environment "toxic?"

As always, toxic people make an environment toxic.

Raywire86

I think it's a mistake to really be too "loyal" to an IT position. The way I see it, IT is very fast paced, and I'm sure a lot of the people on this site are goal oriented and maybe very career aggressive (this is a site for career development!) so we shouldn't discourage one another for doing just that.

I know a lot of people in service desk and desktop support who really like their jobs, are okay with their skill sets (a+/n+) and stay there.

I tend to "hop" to another job when I've learned everything there is to learn at the job or when new experiences start coming at a slow rate. I think a lot of jobs have different learning curves, entry level seems to be about 3 months. When I interview I never have problems with "hoping". I sense IT is not like other industries here.

Ps: whenever I left a job, I was replaced, and now that person has gained skills and experience. Don't be afraid to go if you feel like going!!

HushLives

In my mind, job loyalty exists in only two forms: 1.In your own mind and 2. How much the big wigs like you. If your bosses like you then they would make moves to keep you at the company if you expressed a desire to leave/move up/make more $. For me job loyalty is something that I am having to break the habit of being in, I stayed with a company for 6+ years with no promotions, no pay raises, no nothing, because I liked my boss but at the end of the day it wasn't paying the bills. Job loyalty from a company's perspective is non-existent, especially if you live in a right to work state, where they can fire you for any old reason they want as long as they can prove that it justified firing you. Currently I work in the contracting industry, so "job hopping" is something that is new to me as well. Given my pre-existing loyalty factor to begin with, it blew my mind. But there are people I work with who have been on contract and been poached by the prime contracting company, the government, a rival company, etc. I work with people who have had 3 different positions at 3 different companies in the span of a year. The company I work for, they understand that this happens, they even encourage it, because it boosts their profile. Particularly with the entry level positions because it shows that you can cut your teeth at this company, gather some skills and move on up to bigger and better things.

Xyro

HushLives wrote: »

In my mind, job loyalty exists in only two forms: 1.In your own mind and 2. How much the big wigs like you. If your bosses like you then they would make moves to keep you at the company if you expressed a desire to leave/move up/make more $. For me job loyalty is something that I am having to break the habit of being in, I stayed with a company for 6+ years with no promotions, no pay raises, no nothing, because I liked my boss but at the end of the day it wasn't paying the bills. Job loyalty from a company's perspective is non-existent, especially if you live in a right to work state, where they can fire you for any old reason they want as long as they can prove that it justified firing you.

Yes, I remember stating to myself before I began this whole journey that I would definitely be a very loyal worker because my being is very loyal in personality; however, as far as I see now loyalty has no place in the job world.

paul78

Xyro wrote: »

...as far as I see now loyalty has no place in the job world.

There is nothing wrong with having a sense of loyalty in your career. Loyalty is earned and it exists between people, not between yourself and a corporation.

If you trust and respect a particular manager because because he/she has mentored your career, it is only proper to also have a sense of loyalty towards that person.

I have always showed loyalty to those that I respect throughout my career. And, those individuals have reciprocated in kind.

Nothing wrong with loyalty. If anything, we need more of it.

Xyro

You're likely right, Paul & perhaps when I leave this geographical location I will be able to once again share your viewpoint.