At what point is changing jobs considered job hopping? Is it based on time at a company? Would switching jobs after working for a company for a year be considered a hop? I'm thinking it would probably depend on the time required to get to 100% effectiveness, but is there a general trend recruiters look for? And what if a developer is changing jobs due to relocating? If a developer started a new job and then moved to a new city 6 months later, would that look like a job hop?
I think it is mostly based on the time at a company. How could a recruiter possibly know the time to get 100% effective at a specific company?
I also think that it is not considered a "job hop" when you change your employer once or twice in a short period of time. If it happens more often, it is definitely job hopping. But that is my personal opinion.
Beekey Cheung is a software engineer with a large amount of enthusiasm for economics and a passion for education. He loves mentoring other programmers and is currently building an application to te...
It really depends. I think getting ramped up at an early stage startup is much easier than ramping up at a place with years of technology built. Usually takes me 6-12 months to be fully effective, though most developers should be able to produce good work within the first few weeks.
Not sure if relocating matters. Most developers have the option to work remote when moving. Even if a company doesn't want it to be general policy, it's better to have a remote developer who's proven to be extremely valuable than to lose them simply because they want/need to live elsewhere. Besides, the resume is probably not going to say whether a relocation was due to wanting to switch jobs or for other reasons. That'll most likely be covered in the interview at which point it's up to the interviewer's discretion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
At what point is changing jobs considered job hopping? Is it based on time at a company? Would switching jobs after working for a company for a year be considered a hop? I'm thinking it would probably depend on the time required to get to 100% effectiveness, but is there a general trend recruiters look for? And what if a developer is changing jobs due to relocating? If a developer started a new job and then moved to a new city 6 months later, would that look like a job hop?
I think it is mostly based on the time at a company. How could a recruiter possibly know the time to get 100% effective at a specific company?
I also think that it is not considered a "job hop" when you change your employer once or twice in a short period of time. If it happens more often, it is definitely job hopping. But that is my personal opinion.
It really depends. I think getting ramped up at an early stage startup is much easier than ramping up at a place with years of technology built. Usually takes me 6-12 months to be fully effective, though most developers should be able to produce good work within the first few weeks.
Not sure if relocating matters. Most developers have the option to work remote when moving. Even if a company doesn't want it to be general policy, it's better to have a remote developer who's proven to be extremely valuable than to lose them simply because they want/need to live elsewhere. Besides, the resume is probably not going to say whether a relocation was due to wanting to switch jobs or for other reasons. That'll most likely be covered in the interview at which point it's up to the interviewer's discretion.