DEV Community

Cover image for Changing job - How often is too often?
Dan Newton
Dan Newton

Posted on

Changing job - How often is too often?

Let me add some context to this post.

I will soon be starting my 4th role in the 4 years that I have been working as a Software Engineer. I believe that my reasons for leaving each position are valid and, so far, have not regretted any of the decisions that I have made.

That being said, I am aware I have changed role much more often than anyone else I know. Taking that a step further, during a recent interview I was asked about why I have been in so many different roles during my short career. So it is obviously something that interviewers are picking up on.

On the other hand, after talking to various people I know in tech, they all say the same sort of things. All centering around "it's normal nowadays to change role quite frequently". But, what I ask how long they have been in their role. The answer is always 4+ years or even, that they have worked in a single role for their whole career.

That brings me to my questions.

  • How often do you think is too often to be changing job?
  • How often have you changed job and what effect do you think it has had on your career?
  • If you have interviewed potential candidates who have changed role frequently, did it effect your perception of them, whether positive or negative?
  • Finally does our perception of how we view jobs depend on our age?

Let me know your opinions in the comments!

Latest comments (24)

Collapse
 
isalevine profile image
Isa Levine • Edited

thanks for starting this converation--i'm now learning coding precisely to have a little more job-hopping flexibility, so its good to see all these perspectives on how to do it right :)

Collapse
 
mpermar profile image
Martín Pérez

4 jobs in 4 years on IT would be seen as a yellow flag for any HR person sourcing candidates for a position. Then it would be really up to the hiring manager. But definitely, as you have noticed, it is something it will be spotted.

It's natural to question this when hiring. Soon you will progress on your career and you will have to hire. Then, if you get a resume from a young person that has been 4 jobs in 4 years, you will be asking yourself the same question, is he going to leave on a year?

There are many valid reasons to leave jobs frequently. Even boredom is a valid reason. Without knowing your actual reasons, personally, if I find myself changing often, I would consider whether I should be contracting instead of going permanent.

Collapse
 
swarupkm profile image
Swarup Kumar Mahapatra

I can tell about my experience.. I have switched 3 companies in 5 years.

1st > I was in a company having 10000 employees, I was not convinced with my role provided and work was more of filling excel sheets in the name of testing. I learned programming and I tried hard to switch and I switched . (2 years)

2nd > I was in a company having 1000 employees. The environment was awesome, I learnt a lot. Pay was not super great. An employee of that company moved to a startup and he pulled me into Developer role. I couldn't miss out the opportunity (1.5 years)

3rd > This company had 100 employees. Very good culture like previous one. And I had very nice mentors. one fine day acquisition happened, and the company culture totally changed , and many people left the company (1.5 years)

Now I am in a startup created by the same people who left the 3rd company. the startup is small (10 people) and I am enjoying it.

Collapse
 
niorad profile image
Antonio Radovcic
  1. I'd say a year is a good minimum time. If you have had lots of really short gigs in short time it will definitely come up in the interview.
  2. I'm still at my first company and have been for 8 years, including the internship and the first years as designer.
  3. If they can explain it, it's a positive sign. If they start blaming others for it etc., the interview will end much sooner.
  4. In my case, I got more and more grateful for working in an area that I like and that is fun to be working at. Especially seeing non-techie-peers who are frustrated and live from weekend to weekend and hate Mondays.
Collapse
 
marek profile image
Marek Zaluski

Change jobs when:

  • You're no longer learning anything new, or no longer being challenged
  • The skills and tools are no longer aligned with where you want to take your career next
  • You don't have any immediate opportunities for a better role or more responsibility within the company

Stick to a job longer when:

  • It's an enterprise company where they actually listen to you and where you can have a career development plan
  • It's a fast-growing startup, you're an early employee, and you can grow into a bigger role

In my own career my approach has been: "when in doubt, switch jobs" and it has worked really well for me.

Collapse
 
dowenb profile image
Ben Dowen

In the UK, contractors tend to have had lots of roles, often staying as little as 3 months at time. For permies, I would like to hope they would be willing to stay for more then a year.

Collapse
 
xngwng profile image
Xing Wang • Edited

I think less than 1 year at a job consistently will look bad on your resume (or CV), especially all those less than 1 year jobs is at different companies.

For most developers, it takes average of 3 month to become productive on a new code base.

From a hiring manager perspective, they'll think two things:

  • The person is really bad, and get fired all the time.
  • The person is really hard to keep around, as soon as we spend the resource train him, he'll jump ship.
Collapse
 
xngwng profile image
Xing Wang

of course, if it is internships, it is expected every 3 to 6 month. that is ok.

Collapse
 
frothandjava profile image
Scot McSweeney-Roberts

Personally, anything more frequent than every two years would raise an eyebrow (not fatally, it's just a bit odd). Unless someone's a contractor.

Speaking of contractors, if you don't like staying in one place all that long why aren't you contracting?

Collapse
 
viniciuskneves profile image
Vinicius Kiatkoski Neves

As always: it all depends.

I have spent 4 years in my previous job and didn't get into my comfort zone at all. Until the very last day I was learning and trying new stuffs. So now you might ask why did I get a new job. I went for it as a personal challenge. New country, new life, new product, new... I wanted to try it all.

I honestly think that if you stay something less than 2 years on a job is because the company just not suits you and you have the opportunity to work somewhere else. Because if the company suits you I'm pretty sure you'll have enough challenges and develop yourself in 2 years.

Going back to your questions:

  • Yes, I've interviewed candidates. First I like to know why is he/she looking for a new job and if there is something from the previous position that they didn't like. Second, if the candidate's job changing rate is too high I would look into all available candidates before hiring he/she. As someone that is hiring I don't want to have someone for a short period of time which in most cases is not enough to have impact in the business.
  • IMHO age shouldn't matter but it is not true for most of the companies :/
Collapse
 
lankydandev profile image
Dan Newton

Sounds like you had a nice position and I hope you are enjoying your new one just as much 😄

Collapse
 
laurieontech profile image
Laurie

If you can explain your reasoning and you haven't burned bridges there is no minimum amount of time. I know someone who left a role after 2 months without issue. However, if it's a pattern then I might start to raise my eyebrows a bit.

Hiring is all about telling your story, whatever that story is. If it includes short stints in a variety of roles then that's your narrative.

Collapse
 
lankydandev profile image
Dan Newton

I think it also helps when I explain during interviews, was that I left one position so I could move to a different town.

Collapse
 
laurieontech profile image
Laurie

Absolutely. There are a number of reasons for leaving a job, many of them completely non-controversial. That's why there is no hard and fast rule.