A tangent to this is "management is now hesitant to hire people who have shown an established history of employment."
When you hire a new grad, and then spend a year getting them all up to speed with the process and CI system and code reviews and familiarization with the code base and they're just now starting to take on the responsibility for some of the code... and they leave a year and a day after you hired them.
And so then you hire another new grad... and {repeat}... and they leave a year and a day after you hired them.
At this point, management is a bit frustrated. They give it one more go... and they leave a year and a day after you hired them.
And now, when that position is opened up again, it is no longer an entry level position but rather a mid level. We forgo the extensive onboarding and gradual ramp up for a new grad and instead have a mid who should be able to understand the nature of a CI system, issue tracking, and so on and be able to start being a positive contributor in a month or two and so if they also leave a year and a day later, we've had several months of them being a positive contribution on the team.
... and now its just that much harder for a new grad to find a job.
This is an HR problem. If they’re happy with their job, it’s not possible for them to get a raise with the current company that likely comes anywhere close to what they can get jumping ship. If HR would be willing to say “Hey, we recognize that this person is doing good work and want to keep them, but also recognize they can realize a 50%+ increase elsewhere. Let’s open the checkbook.” Instead, they’ll say that the most they can give them is somewhere around 10%, maybe the manager can fight for 15%. In the end, they’re going to take the 50% increase, even if your corporate culture and everything else is great.
This is public sector. They knew the pay grade when they got hired (stating the pay range has been a requirement ever since the web page was launched) and it can't be changed without an act of the legislature.
With new grads, we can't hold 'em at all. For people who came in with 5+ years of experience, the average tenure here is 15 years. People are more likely to retire than quit. (Seriously, I've got 200 hours of "manager makes sure you use it" vacation, sabbatical accrual, an honest to goodness funded pension, and one of the better health insurance policies).
When you hire a new grad, and then spend a year getting them all up to speed with the process and CI system and code reviews and familiarization with the code base and they're just now starting to take on the responsibility for some of the code... and they leave a year and a day after you hired them.
And so then you hire another new grad... and {repeat}... and they leave a year and a day after you hired them.
At this point, management is a bit frustrated. They give it one more go... and they leave a year and a day after you hired them.
And now, when that position is opened up again, it is no longer an entry level position but rather a mid level. We forgo the extensive onboarding and gradual ramp up for a new grad and instead have a mid who should be able to understand the nature of a CI system, issue tracking, and so on and be able to start being a positive contributor in a month or two and so if they also leave a year and a day later, we've had several months of them being a positive contribution on the team.
... and now its just that much harder for a new grad to find a job.