In March 2021, a PHP developer joined a Shenzhen tech company. Twenty-eight days later, he was found dead at home. He had spent his first month telling his girlfriend and his friends that he was dizzy, that his chest felt tight, that his heartbeat felt irregular, and that he would go for a check-up once the current stretch of work was over. The stretch never ended.

I am retelling this case from a 2021 report republished by 51CTO, which drew on accounts from the developer's family, his girlfriend, and former colleagues. The company did not respond to the reporters before publication, and the death certificate issued to the family ruled out violent injury without establishing a further cause. Those limits matter, and I am keeping them visible: this is a story about what was reported, not a verdict on what killed him. What makes it worth revisiting is not the mystery of the cause. It is the mechanism, which the report describes in unusual detail, and which will be familiar to anyone who has worked in tech.

The company, according to the report, did not formally require overtime. Its contract set standard working hours and said overtime was not encouraged, but added that work not finished within normal hours had to be caught up on the employee's own time. That single clause is the whole trick, and it is everywhere. Nobody orders you to stay late. The workload simply does not fit inside the day, and the shortfall is yours to absorb. The developer's days, as his girlfriend described them, ran from morning onboarding sessions into project work with a one-month deadline, then into a second development package at home in the evening, then into weekends spent on the same package. His own messages home followed a pattern anyone who has burned out will recognise: I am tired, I am dizzy, this weekend is also work, it will ease up after this stretch, I will get checked next month. The body was sending signals for weeks. The schedule had no slot for listening to them.

Then came the part that connects this story to every other story like it. The family said the company offered three months' salary as compensation, which the family considered unreasonable, and negotiations stalled. By early May, the family said the company had stopped contacting them at all. Reporters who called were told the matter would be passed to the relevant colleagues. No response arrived before publication.

Put those two halves together and you see why the phrase "voluntary overtime" should be retired. The first half is a workload designed to exceed the working day, paired with a contract that relocates the excess onto the employee. The second half is what happens when the human cost of that design becomes visible: a modest offer, a stalled negotiation, and then silence. The company does not need to win an argument about hours. It only needs the family's energy to run out, which grief reliably ensures.

There is a specific lesson here for people early in their careers, because this developer was a new hire. New hires are the most exposed to this mechanism. They have no track record to trade on, no sense of what a normal workload looks like at the company, and every incentive to prove themselves by absorbing the overflow. A one-month deadline handed to someone still in onboarding is not a test of ability. It is a transfer of risk from the project plan to the person least able to refuse it. If you are that person, the warning signs are not weakness: dizziness, chest tightness, a heartbeat that feels wrong, and sleep that never catches up are data, and they outrank any deadline. The check-up he kept postponing to next month is the appointment that should never be postponed. No project remembers who finished it. Your body keeps the record.

There is a lesson for managers too, and it is simpler than any wellness programme. If your team's work routinely does not fit inside working hours, you do not have a dedication problem. You have a planning problem, and you are solving it with other people's health. The honest fixes are boring: smaller scopes, longer deadlines, fewer concurrent packages, and a rule that unfinished work goes back to the plan instead of into the evening. A contract clause that makes employees absorb the overflow is not flexibility. It is an instruction to hide the planning failure where nobody will measure it until someone collapses.

The report that carried this story ended with health advice, and most of it was the usual list: eat well, move more, sleep enough, keep your goals reasonable. All true, all beside the point. Advice addressed to the individual cannot fix a workload that was never the individual's decision. The advice that would have mattered here was addressed to the system around him: a deadline that fit the month, a manager who noticed a new hire working weekends, and a culture in which saying "this does not fit" was treated as information rather than disloyalty.

He had been at the company for less than a month. That is the sentence that should stay with you. Not because a short tenure makes the death more tragic, but because it shows how fast the mechanism works. It does not take years of grinding to break someone. It takes a few weeks of a workload that never ends, a body signalling distress, and a calendar with no room for a check-up. The work will always be there. The question is whether you will be.

I write about work, building, and the systems ordinary people run into at Airgrix (https://airgrix.com), where I also run a small independent store.