Tech Workers and the Architecture of Knowledge-Work Burnout

A senior software engineer came into our office last year and said: I am still hitting all my deliverables. My manager loves me. I got promoted six months ago. I have not had a real moment of joy in eighteen months. I do not know what is wrong.

This is the particular shape of tech burnout. Not the visible collapse that makes someone call in sick. Not the inability to function. Tech burnout looks, often, like productivity. The numbers are still being hit. The slack messages are still being answered. The features are still shipping. And the person inside the productivity has gone somewhere — sometimes years ago — and is quietly disappearing under the load.

This article is for software engineers, founders, product managers, designers, and other knowledge workers carrying the particular cost of high-performance modern tech work.

Why tech burnout is its own thing

Several features distinguish tech work from other knowledge-work contexts:

Always-on culture. Slack, email, on-call rotations, distributed teams across time zones — the work has no clear end. The phone in the bedroom is part of the job.

Cognitive intensity without recovery. Software engineering specifically requires sustained deep work — holding complex systems in working memory, debugging, architectural reasoning. Recovery from this kind of cognitive load takes longer than recovery from many other kinds of work, and the modern tech schedule rarely allows it.

The merit-myth and impostor syndrome combined. Tech culture tends to frame outcomes as products of individual brilliance, which produces both pressure to perform and chronic doubt about whether one's success is deserved. Most of the senior engineers and founders we see carry significant impostor material despite objective accomplishment.

Compensation that locks in the trap. Tech compensation, particularly at senior levels, can be high enough that leaving is financially complicated. Stock vesting, RSU schedules, bonuses, and golden- handcuffs structures keep people in roles that are hurting them.

The startup mythos. Founder culture explicitly valorizes self-sacrifice, sleeplessness, and total identification with the company. The cost of buying into this is real. So is the cost of stepping back from it.

Identity-output fusion at unusual intensity. Many tech workers came of age through achievement — academic, then early-career — and have organized identity around output. The fusion is particularly tight in this population.

Specific patterns we see in tech clients

The IC engineer at year 8-12. Senior individual contributor who has been productive for a decade, has accumulated significant compensation, and has lost the relationship to the work that brought them in. Often paired with anxiety and physical symptoms. Sometimes paired with adult ADHD that was never named.

The founder of a Series A through Series C company. Carrying the weight of the team, the investors, the technical debt, the personal financial exposure. Cannot rest because rest threatens the company. Marriage strained, sleep gone, sometimes substance use creeping in.

The product manager between the team they manage and the leadership above them. Specific kind of squeeze that produces a recognizable burnout pattern.

The post-acquisition or post-IPO collapse. The exit happened. The financial outcome was achieved. And without the goal that organized the work, the person inside it has nowhere to go. Surprisingly common pattern.

The laid-off senior engineer. Tech layoffs in 2023-2024 affected thousands of senior workers who had defined themselves through their roles. The grief, identity disruption, and re-orientation work after these losses is significant.

The high-performing engineer with undiagnosed adult ADHD. Often visible by midlife. Compensation strategies that worked in early career fail under increased complexity. (See: Adult ADHD →.)

The tech worker whose marriage is being eroded by the work. One of the most common presenting concerns. The partner has been telling them for years that they are not really there.

What helps

The work with tech clients is partly the same as general burnout work and partly distinct.

Honest examination of the work-load reality. Some tech burnout responds to better boundary- setting within a sustainable role. Some requires actually changing the role. Some requires changing companies or industries. The diagnostic conversation about which is which is the foundation.

Address the architecture, not just the surface. As with all burnout work, the underlying architecture — perfectionism, identity-output fusion, hyper-responsibility — needs attention or the burnout will recur. (See Burnout Recovery: Beyond Self-Care → for the deeper architectural work.)

Sleep, body, and nervous system. Tech work is uniquely hostile to sleep architecture. Real recovery requires real sleep, which often requires substantial behavioural and structural change. We sometimes coordinate with our naturopathic medicine for the biological support.

Marriage and partnership work where indicated. Many tech clients arrive with marriages that need direct attention alongside the individual work. (See Couple/Family Therapy →.)

Specific work with anxiety, ADHD, and OCD spectrum patterns where present. These often co-occur with tech work and benefit from focused attention.

For founders specifically: confidential space outside the company system. The CEO cannot fully process struggle with the team or the investors. They need a confidential professional relationship that exists entirely outside the company. This is some of the most important work executive coaching and therapy can do for founders. (See Executive Coaching →.)

The career-recalibration question. Often the deepest piece of tech work in midlife is whether the career one has built is the career one actually wants. This is not a question to rush through. It is also not a question to avoid forever.

A word on the specific Vancouver tech context

Vancouver's tech ecosystem has its own particular features — the proximity to Seattle and the cross-border professional movement, the cluster of gaming and biotech and cleantech, the smaller scale that makes confidentiality concerns more pointed in some communities. We work with tech clients across the local ecosystem with full discretion, and we are familiar with the specific dynamics of working in the Lower Mainland tech scene.

When to come in

If you are a tech worker recognizing yourself in any of this — even (especially) if you are still high- performing — please consider therapy.

Counselling for Tech Professionals at Baraka is depth-oriented, integrative, and discrete. Evening and online options for the schedules that don't fit standard hours. Available in English and Farsi.

• Book a free 15-minute consultation → Or call (236) 455-6306 Email contact@barakaocc.com