It's up to them to make sticking around your best option. But when I'm on interview panels and someone brings up that the person in question is a job hopper, rather than see that as a negative, I see it as a challenge to find a way to get that person to stick around. And the only thing that offends me when someone quits is if the offer to do so isn't better than sticking around.
I am not popular with my fellow managers with this attitude and I expect downvotes for this. Bring 'em. It really doesn't matter to me anymore, the remainder of my career will be spent on making hard things easier rather than making easy things harder.
However, if someone has generally changed jobs every year or two and I wouldn't hire someone who I knew with certainty would only stay that long, I might think I'm special enough that I can keep them around. But I'd probably be wrong.
Perhaps you mean if they treat employees like a commodity. They can do that withoug laying people off; universities tend to treat their tenured faculty this way also. Optimizing for getting the most work out of the witth the lowest cost. If so, then yes employees should, in turn, act like the job is a commodity and try to optimize income-minus-costs on their end too.
And yet, all that fuss about these job hoppers. How about creating an environment and culture where sticking around beats job hopping instead?
As for the alternative? Check out the severance packages that executives and TLAs get. Try scaling that down to the employee level. Not going to happen.
And in our lawsuit-happy culture (with a perverse incentive for companies to always settle lawsuits even when they can win), even the most employee-friendly place probably needs such an agreement for CYA reasons.
I do agree ecompanies can do a much better job of treating employees like partners instead of "resources" to optimize. Even on HN, we have fellow engineers talking of the importance of (soul-crushing) processes that ensure no one is essential. As if it's undesirable to let anyone be special or important...
https://www.nytimes.com/2002/03/11/business/stock-options-ar...
Also you’re not really signing an agreement that they can fire you, you’re signing an acknowledgement of the at-will employment status so you can’t claim any illusions that you had an employment contract, but that status is typically derived from state law and advertised on the job posting you applied for. That paper you’re signing is about the same as an acknowledgement of the warning that you shouldn’t eat tide pods. It’s there because stupid people have necessitated it.
Speaking as a long time employee and now as an owner/employer, I’ve always thought people who bristle at at-will employment don’t really get it — it’s a two-way street, as an employee you can leave anytime, being considerate of professional courtesy for notice, etc.
I was always highly confident in my value and skills, so the idea of an employer randomly laying me off was never an issue - their loss more than mine. Your life will be far less stressful if you can develop that mental confidence and self-actualization, and if there is something preventing it, work on that. Specifically, if you feel lucky to have been employed in your field, and are barely hanging on to your job, maybe you should find a better field?
At-will employment should not even remotely be a big concern in life. Talent is hard to find - there’s more money than talent out there.
The way to get there is to refuse to sign non-compete agreements unless they come with an equivalent clause to what I got. When you sell yourself short, you sell everyone else along with you.
The difference (at least to me) is time. Hoppers are people who typically change jobs every 1.5-3 years.
Jumpers, will have a long history of 6 month stints, very few if any gigs longer than a year. At most places I've worked, depending on the quality of on-boarding it took most engineers 1-3 months to be productive, and 3-12 months to understand the system well enough to make impactful changes to the ecosystem safely.
I've lasted anywhere from 30 days to over a decade depending on the gig. And every one of those moves was the right choice. I prefer to rely on my own research of the person's career track and the number of people they can summon as references to say nice things about them. Tech culture brings out survival traits and I'm not going to hold anything against people who act in their own best interest.
The other side is that, if you're not as good as you're supposed to be, normally you won't get fired just in one year, you are actually overpaid. From the corporate side, the better engineers are covering the loss(those are overvalued but still too early to be laid-off).
So the best and most capable ones will switch jobs after 3 years, not totally because the company is too greedy. Unless there is a way and culture to make your salary can go up and down each year based on your performance, there is no good solution(because pay-cut is not common no matter what). In the end those who are overpaid will more likely to stay, those who are undervalued will likely jump board.
One way is to keep salary less important, like an average value that is reasonable for both sides, then the company can use monthly/quarterly/yearly bonus to reward the top employees, but who could like it when he has a 30-year fixed-rate mortgage that needs a sense of secure/stable income.
If you don't get a raise in the first year, it's often more about pedantry regarding the HR rules, which tend to be "optimized" by penny-pinching adjustments over the years to take advantage of employees every way they can (this is their job, squeezing money out of people any way they can). E.g. you weren't there for the last round of evaluations so you don't get a raise. Possibly no bonus too. You need to discuss all this stuff when negotiating, they'll be trying to help you work the system at that point, rather than using it against you.
Companies rely on the fact that you stay a couple of years at least. So if you want to make good deal, you need to switch jobs more often.
Although I agree with your overall point, I disagree with this line of reasoning. I think the pay offered to an engineer already takes into account that they will understand the tech stack after six months to a year. The situation is essentially the reverse of what you said: they're being overpaid initially compared to their productivity (but, quite rightly, that's the company's problem). Then their productivity catches up with their salary.
But I agree with your point in the years after that.