“Why the tech industry needs a more honest conversation about ADHD”
Written by Roxana Tascu
In tech, some of the most valuable work happens in cognitive states that are hard to explain to anyone outside the industry. It is the engineer who can hold an entire system in their head long enough to spot the hidden dependency causing a failure cascade. The product lead who can connect user behaviour, market shifts and platform capability before the data fully catches up. The developer who disappears into a problem in the afternoon and emerges hours later with a cleaner, more elegant solution than anyone thought possible.
These moments are often treated as part of the mythology of the industry, technical instinct, engineering obsession and product intuition. In reality, many of them sit much closer to the way ADHD brains naturally process complexity, novelty and challenge.
That link matters because the tech industry is unusually rich in the conditions that help ADHD minds perform at their best. Rapid iteration, changing tools, constant learning, system-level problem solving and high-stakes delivery all create the kind of environment that naturally generates activation. The ADHD brain rarely responds to importance in the abstract, it engages when the task carries enough complexity, urgency, problem tension or cognitive intrigue to create real momentum. Tech workflows create these triggers almost by default, whether that is a sprint deadline, a launch window, a live issue or an architectural bottleneck.
In my work as a business psychologist and ADHD coach, this is one of the clearest patterns I see across engineers, product specialists, founders and technical leaders. Many of the professionals I work with have built exceptional careers around exactly these strengths, and much of my work starts by helping them recognise that what they have long called “just how my brain works” is often a highly specific activation profile that tech environments have been rewarding for years.
This is one reason ADHD can so often go unrecognised in technical roles. From the outside, the person looks like a high performer thriving in exactly the right environment. They are the person others turn to when complexity spikes, when systems break and when ambiguity needs resolving fast. The output is real, and often exceptional, but the industry can easily mistake environmental fit for effortless consistency.
The friction usually appears in the parts of technical work that are less stimulating but commercially critical. Documentation, roadmap sequencing, testing discipline, long horizon systems planning, technical debt reviews and stakeholder communication rarely provide the same immediate neurological payoff as solving a live issue. These tasks matter deeply, but they do not always generate the activation conditions the brain needs in order to begin. The result is a contradiction many professionals in tech know intimately, the same person who can solve an infrastructure problem under extreme pressure can spend days avoiding a strategically important but cognitively flat task.
This is where the usual conversation around ADHD in tech becomes too simplistic. The industry often swings between celebrating the strengths or pathologising the struggles, but both framings miss the operational truth. The same wiring that fuels innovation, abstraction, systems thinking and deep immersion can also create an invisible reliance on urgency as the main route into performance. That works well in an industry full of incidents, releases and constant change, until the cognitive cost starts compounding underneath visible success.
I see this particularly often in startup and scale-up environments, where responsiveness is culturally rewarded and pressure can become the default operating system. Many professionals build reputations around being the person who rescues the sprint, reframes the architecture or solves the impossible problem at speed. What is less visible is how much of that excellence depends on pressure being present, and how difficult consistency can become when the work shifts from urgent problem solving to strategic technical thinking.
This is why the tech sector needs a more honest conversation about ADHD, not as a wellbeing trend but as a performance reality. The commercial value of many ADHD traits in technical work is obvious, such as fast synthesis, pattern recognition, comfort with uncertainty, hyperfocus and non-linear thinking. The hidden risk is what happens when teams and organisations unintentionally design cultures that depend on reactivity and crisis energy to access those strengths.
My work with professionals across tech focuses on helping them understand the difference between brilliance under pressure and sustainable cognitive performance. The question is not whether ADHD helps or hinders in tech, the more useful question is whether the environment is supporting exceptional thinking without quietly making urgency the price of access. For an industry obsessed with designing better systems, this may be one of the most commercially important human systems it still fails to build intentionally.
Roxana Tascu is a business psychologist and ADHD coach who works with professionals across the tech and creative sectors, helping them build sustainable ways of working around how their brain performs best. Discover more of Roxana’s work at www.adhd-advantage.com, or connect with her on Instagram @RoxanaTascu