burnt_husk
You are less of a person and more of a means to an end. A tool to achieve something, and some tools are disposable. It can be of career advantage to a manager to burn out engineers. Maybe instead of spreading 24x7 on-call across 3 teams in three timezones, you put it on 1 team in 1 timezone. By doing so a manager can achieve a lot with less resources, and hopefully secure their own elevation up the corporate ladder before the cost of their strategy becomes evident.
The cost of burn out I think remains hidden, in technology there's a constant flux of staff anyway, teams being being created and dissolved, in all the noise a few people being exhausted and bailing from the company is hardly noticed. Perhaps they said something before they left, but it's best for everyone in middle management if the burnt out individual is labeled the problem, they were a bad culture fit you see, a grumbler who didn't have what it took.
I suffered burnout there. I had the misfortune of working as an "SRE" at Atlassian. The reality was you spent your days, nights, and weekends dealing with major incidents.
I do not know if it was a conscious strategy, but it would seem the approach taken to reduce organizational wide pager fatigue and burnout from out of hours work was to concentrate it on a few.
(My guess is that it was conscious, as that best explains why my cries for help whilst falling on seemingly sympathetic ears, yielded no changes.)