Ask HN: Is job hopping as bad as they say?
41–45 of 45 posts
Re: Ask HN: Is job hopping as bad as they say?
#42There are 2 different career paths, both valid, both with their pros and cons.
With short-term positions you will be "hired gun", where they hire you to contribute on a particular project and will likely view you as expendable when budgets are cut or shifted to other priorities. This is not necessarily bad though, if you keep getting good references companies will continue to hire you knowing that you will deliver. Plus getting a raise is way easier when moving from company to company vs getting 1.5% annual raise. Plus prospective employers know that you've been to number of companies and can provide outsider's prospective on a number of subjects.
Whereas when you stay employed at the same company you learn all the nooks and crannies and will likely be either promoted to management position (if you wish to do so so) or get other benefits (longer vacation, higher bonus, more freedom in determining your schedule, projects, who you work with, etc etc). At the same time, if the employer does decide to lay you off, finding another job will be difficult since you don't have much experience in job hunting, and much of your experience is with the same company (not necessarily applicable to other companies).
So at some point in your career you will have to choose a path and stick to it.
Re: Ask HN: Is job hopping as bad as they say?
#43I take the opposite view to most of the comments below, and have a strong opinion on it. I think the idea of long term loyalty to one company is naive, I'm sure there are exceptions, but, I believe staying at one place limits your personal growth, experience/variety, and most importantly earning potential. Work is transactional, most of us only do it because we get paid, if you get a better offer you should go, you o…
Re: Ask HN: Is job hopping as bad as they say?
#44Earlier quoted context omitted.
I don't think longer tenures are as positive of a signal as you're making them out to be. - You can essentially have 1 year experience repeated n times. - People with very long tenures can have a narrower view of what software development is. By switching more often you get to be exposed to different domains, teams, managers, ways of working and in a way you can mentally abstract over them instead of learning the pro…
I think if every tenure is less than two years it's a red flag for a senior position. Anyone can get by for a year but if you're around for two you'll inevitably need to deal with conflict resolution and maintaining relationships and products. If you can't stick around two years anywhere I'm prone to thinking you're someone who vomits a bunch of code and then leaves the team to pick up your mess. Or someone who can't…