I don't really see it that way. Training people is more expensive than hiring a senior dev for the simple fact that you have to use a senior dev's time to train the new person anyways.

> Training people is more expensive than hiring a senior dev for the simple fact that you have to use a senior dev's time to train the new person anyways.

For the first N months, sure, but then, you have a senior and a trained junior, who is hopefully on their way to being a mid. So it's less of an expense and more of an investment in my eyes.

But like any upfront investment, there is a time when the costs outweigh the benefits, especially in the early days.

The "investment" part of the equation is where I see that model breaking down and failing. There's a lot of poaching and job-hopping, especially motivated by total comp. You could say it's always been that way, but in terms of the senior/mid/junior spread it seems like in our industry, employers would rather hire another senior than hire a junior who needs investment.

"So it's less of an expense and more of an investment in my eyes."

Too bad companies don't see it that way.

Well, I've been part of companies that have seen it that way, so they're out there!

But I agree, too few companies have that perspective.