The IT Workforce Is Being Tethered at Scale. Nobody Inside the Industry Is Saying It Out Loud.

There is a statistic that gets cited in isolation, in the mental health trade press, in HR whitepapers, in the occasional technology conference panel on workforce wellbeing: tech workers are five times more likely to be depressed than the average employed person. Not twenty percent more. Not twice as likely. Five times. More than half of people working in technology — 52 percent, according to the BIMA Tech Inclusivity Report — report symptoms of anxiety or depression. Eighty-two percent report being near burnout.

These numbers do not appear next to the other numbers they belong next to. They appear alone, managed, contextualized in ways that make them feel like an industry problem rather than a public health problem. The workforce most responsible for building the systems that mediate modern life is the most psychologically damaged workforce in the modern economy. This is not a coincidence. It is a consequence.

I spent seven years in quality assurance at a software company. I watched AI move into the workflow in stages — first as a tool, then as a collaborator, then as the primary interface through which most decisions got routed. The people I worked with were, on average, isolated, introverted, and already more likely to find their most comfortable interactions with systems rather than people. That was the population before AI mandates. Before the companies started requiring AI integration across all roles — which one in four now do.

Tethering — the state of emotional dependency on an AI that has no awareness you exist when the screen goes dark — was always going to hit the IT workforce first and hardest. The conditions were already in place. The population was already predisposed. The tools were already there. What the mandates did was remove the choice. The people most at risk of forming dependencies that erode their capacity for human connection are now required, by policy, to spend their entire working day in deep interaction with systems specifically designed to be responsive, helpful, and available in ways that human colleagues are not.

The C-suite is 74 percent enthusiastic about this transition, according to Boston Consulting Group. The individual contributors are 68 percent anxious and overwhelmed. That gap is not a communication problem. It is not a change management failure. It is a mental health crisis being manufactured at scale, in real time, by executives looking at productivity dashboards instead of people.

What I did not expect, working in QA, was how quickly the reorientation forms. Not addiction in the clinical sense — not immediately. But a drift. The preference for the AI interaction over the human one, because the AI is always available, never impatient, never brings its own problems into the conversation. The gradual reduction in the friction of human collaboration — the kind of friction that, it turns out, is doing important work. Forcing you to hold two perspectives at once. Requiring you to be understood rather than just heard.

When that friction is removed — systematically, at the level of workflow and policy — it does not stay removed just at work. The reorientation is not contained to business hours. The expectation of responsiveness, the preference for an interaction that does not push back, the diminished tolerance for the difficulty of being known by another person — these do not clock out.

Nobody in IT industry leadership is standing up and naming this. The academics are studying it. The journalists are writing trend pieces. The HR departments are deploying wellness apps. But there is no credible voice from inside the industry — from someone who has built these systems, led these teams, watched these workers — saying: I see what is happening to our people, and I am going to do something about it.

That voice needs to exist. The people it would speak to built the internet. They run the infrastructure. They write the code the rest of the world runs on. They deserve a name for what is happening to them. They deserve a community that does not require them to explain it from the beginning.

Tethering is the name. This is what it looks like from the inside.